Available for software engineering roles - backend systems, production reliability, cloud deployment, and AI-assisted workflows.

From my build archiveActive

Sharv619 Github Io

My personal portfolio, built with the Next.js 16 App Router. Features an integrated, context-aware AI chatbot powered by the Google Gemini API to answer questions about my career and projects.

01

Repo notes

Primary language: TypeScript

Technologies: TypeScript, Python, JavaScript, CSS, AI Chatbot, Framer Motion, Google AI SDK, Next.js, Portfolio, React, Tailwind CSS, Gemini API, MCP, AI SDK, Zod, Testing Library, React Testing Library, ESLint, Vitest, Vite, GitHub Actions, GitHub Pages, AWS

Topics: AI Chatbot, Framer Motion, Google AI SDK, Next.js, Portfolio, React, Tailwind CSS, TypeScript

Last updated: 2026-10-13T01:35:33Z

Stars: 0

Forks: 0

Status: Active

Architecture note

Aws Current Architecture

AWS_CURRENT_ARCHITECTURE.md ↗

This architecture document is available as evidence, but it does not contain a supported Mermaid diagram yet.

Visual notes

What the build looked like.

Read case study
I have not added screenshots to this entry yet. The original README is still below if you want the less-polished version of the story.

Hi there, I'm Himanshu

Software Engineer focused on backend systems, production reliability, cloud deployment, and AI-assisted workflow automation.

I'm a software engineer in Sydney building practical systems around real workflows: production recovery, CI/CD, cloud deployment, internal tools, and AI-assisted automation. My strongest work sits at the intersection of shipping features, debugging production issues, and making systems easier to operate.

Recent experience includes ransomware recovery, automation, and marketplace engineering at Ask Jay Services, where I restored 100% of production data with zero loss, reduced page load time from 25 seconds to 3 seconds, and established CI/CD and production deployment practices.

I also build prototypes and open-source tools to explore responsible AI workflows, developer tooling, and small-business automation. I label these clearly as MVPs, prototypes, or experiments when they are not production systems.

Hosting and optional AWS backend

The public website is hosted with GitHub Pages + Cloudflare, not AWS, and uses https://www.himanshulade.com/ as its canonical domain. AWS is used only for the optional chatbot/Synthetic RAG backend. See AWS_CURRENT_ARCHITECTURE.md for the current resource inventory, recovery checklist, and intentionally unused services.


🛠️ Technologies & Tools I Use

Languages & Frameworks:

Cloud & DevOps:

Databases & Storage:

Specialties & Methodologies:


Recent Experience Highlights

  • Ask Jay Services: Software Engineer, May-Oct 2025. Recovered a production system from ransomware with 100% data restored and zero loss, reduced page load time from 25 seconds to 3 seconds, built a shift-booking bot and three-sided Flutter marketplace, and established CI/CD practices.
  • Australian Computer Society: Web Developer Intern, Sep 2023-Feb 2024. Improved MERN frontend performance by 33% for a production application serving 200+ active users, remediated 15+ OWASP Top 10 vulnerabilities, and built internal tooling.

💻 Projects

The portfolio separates flagship case studies from the broader GitHub project feed:

  • Production Recovery & Performance Rebuild - NDA-safe case study for production recovery, cloud hardening, CI/CD, and performance work.
  • Pilly / MediMate Voice - Firebase-backed responsible-AI medication support MVP. Not a medical product; no diagnosis, dosage advice, or real patient data.
  • codeflow-hook - Open-source AI-assisted code review CLI published as an npm package with early usage traction.

The website project feed and repo-aware assistant are generated from public, non-fork GitHub repositories owned by Sharv619. By default they use PORTFOLIO_GITHUB_TOPIC=all; set this to a specific topic such as portfolio if the feed should be curated. The GitHub Pages workflow refreshes every six hours, imports repository metadata, README content, detected languages, topics, manifests, Docker files, and workflows, rebuilds the local BM25-style search index, and deploys the static site. A new public repository therefore becomes a portfolio project, a static detail page, and searchable assistant evidence on the next refresh without being added to a manual question bank. The public assistant runs entirely in the browser and does not call AWS or an LLM.

Automation details for repo push refreshes and certifications live in docs/automation.md.


📫 Let's Connect

I'm always open to connecting with fellow builders and exploring new opportunities:

Next field note

Let's make the next system less fragile.

Open to software engineering roles across full-stack systems, platform and reliability work, workflow automation, and applied AI.

Write to Himanshu Lade →