Full-stack engineer.Builder of systemsthat scale.
Full-Stack
Engineer
Bengaluru,
India
The journey, in chapters.
Where it started.
Origin /Picked up Computer Science in class 12. Hindi medium school, no home computer, no roadmap. Saw a discipline I could go all-in on and made the call.
- 10th: PCM. 12th: added Computer Science to the mix.
- Decided engineering was the path before I knew how to type.
- English was a barrier. Treated it as a problem to solve.
The decision.
Pivot /Prepared for NDA, then made a deliberate switch. Looked at the path realistically and chose Computer Science. No regrets, no second-guessing. Commitment, full and final.
- Prepared for NDA selection.
- Self-assessed and pivoted to engineering.
- Committed completely. Removed the back-up plan.
The foundation.
Foundation /First formal CS education. First time writing real code. Lab time wasn't an obligation, it was the point. Built fundamentals in C, Java, web technologies, and started reading code more than tutorials.
- Bachelor of Computer Applications.
- First production-style projects.
- English caught up with the engineering.
Distinction.
Mastery /Master of Computer Applications, graduated with Distinction. Deeper systems thinking, OS internals, networking, advanced algorithms. The degree mattered less than the discipline it forced.
- MCA with Distinction.
- Systems-level thinking became default.
- Started building things outside coursework.
Sharpened the toolkit.
Upskill /Six months of focused work on Java, OOP, design patterns, and backend fundamentals. Self-funded, self-directed. The point: walk into the industry already production-capable.
- Deep Java and OOP mastery.
- Backend architecture patterns.
- Established the habit of continuous upskilling.
Production-grade engineering.
First job /Joined as a trainee, promoted twice. Built React applications tracking aerospace manufacturing parts across multiple sites. Learned what production code actually means: reliability, edge cases, code review, and shipping under deadline.
- Two promotions in 2.5 years.
- Built scalable React systems with Hooks and modern patterns.
- Designed role-based access and task assignment workflows.
- Owned modules tracking aerospace parts across sites.
The Breville chapter begins.
Turning point /Stepped onto a global e-commerce platform. Led the React to Next.js migration, introduced SSR, and rebuilt the rendering layer. The architecture I set up became the standard the platform runs on today.
- Led migration from client-side React to Next.js.
- Introduced SSR with measurable SEO and Core Web Vitals gains.
- Set the architecture for what became a 4+ year platform evolution.
Scale, ownership, full-stack.
Ownership /Four years. Went from feature work to owning R&D and delivery of critical systems. Built authentication from scratch, integrated Algolia for global search, shipped Salesforce-backed support chat, drove WCAG 2.1 compliance, and built backend services and data pipelines powering the storefront.
- Scaled platform across 30+ countries with region-aware rollouts.
- Built end-to-end Auth0 authentication: design, integration, rollout.
- Implemented Algolia search across the platform.
- Shipped Salesforce-integrated customer support chat.
- Drove WCAG 2.1 compliance across product.
- Built backend services and data pipelines for search indexing.
- Owned high-traffic product pages and checkout flows.
In-house, leading the platform.
Now /After 4+ years building Breville as an external engineer, brought in-house. Now leading frontend architecture across global product, maintaining the shared React component library, owning SEO infrastructure, and building AI-powered internal tooling on Claude Code, LangGraph, and AWS Lambda.
- Lead frontend across global product, multiple squads.
- Own the shared React component library used platform-wide.
- Architected SEO infrastructure: SSR strategy, structured data, performance.
- Migrated product comparison system to server-driven architecture.
- Designed AI-based incident triage system on LangGraph + AWS Lambda.
- Building developer productivity tools with Claude Code.
"Build it. Ship it. Own it.
Then build the next thing better."
Working principle, learned the hard way
The craft, in detail.
The interface.
- React
- Next.js
- TypeScript
- CSS Modules
The services.
- Node.js
- Java
- REST & GraphQL
- Data pipelines
The infrastructure.
- AWS Lambda
- EventBridge
- AWS S3
- Vercel
The connections.
- Auth0
- Algolia
- Salesforce
- AEM & Contentful
The AI layers.
- Claude Code
- LangGraph
- MCP servers
- GPT models
The discipline.
- WCAG 2.1
- Core Web Vitals
- Jest & RTL
- ESLint, Husky
Hi, I'm Vinit.
I'm a Senior Full-Stack Engineer based in Bengaluru. For the last seven years I've been shipping production systems at scale, from aerospace manufacturing platforms to global e-commerce serving millions of users across thirty countries.
I work across the entire stack. React and Next.js on the frontend, Node and Java on the backend, AWS Lambda and EventBridge for infrastructure, and now Claude Code, LangGraph, and MCP servers for AI-powered tooling. I care about ownership, evidence-based decisions, and shipping things that actually work.
Outside engineering, I'm continuously upskilling. The day I stop learning is the day I stop being useful.
Outside of engineering, the gym keeps me grounded and cricket keeps me honest. If the software career had not worked out, there is a decent chance I would be mid-pitch somewhere arguing about a no-ball. Priorities still matter though. Everything gets a slot or it simply does not happen.
Four principles, learned by doing.
Ownership over output.
Building a feature is the starting line. Owning a system means thinking about edge cases, observability, incident response, and what breaks at 3 AM. That mindset is what got me from contributor to platform lead.
Evidence over opinion.
Every decision gets grounded in data. Bundle size, Core Web Vitals, error rates, SEO impact. If I can't measure it, I can't claim it improved. No vague filler.
Reuse before rebuild.
Check the component library. Check the utilities. Check what the team already shipped. Duplication compounds technical debt; reuse compounds velocity.
Self-investment, always.
Six months of self-funded coaching after MCA. Continuous upskilling on the job. Now building agentic AI tooling. The day I stop learning is the day I stop being useful.
Achievements & certifications.
Achievements.
04 AwardsCertifications.
06 CredentialsBuilding what's next.
Interested in problems where scale, performance, and developer experience intersect. Going deep on agentic AI systems, incident automation, and frontend platforms that hundreds of engineers depend on.
If you're building something interesting in that space, let's talk.
The anchor.
Every essay has one quiet truth running through it. This one's mine.
My mother. Every decision, every late night, every pivot. She backed it before there was any proof it would work. Crediting that, plainly.