Hi there...
I'm a full-stack engineer with 2+ years across big tech such as Amazon and enterprise software like Dayforce - cloud infrastructure, real-time systems, React frontends, and increasingly prompt engineering for LLM-backed features. System design is the part I enjoy most: how the pieces connect, and how they stay coherent as the system grows. The art and the engineering aren't separate to me - both come down to making something coherent, where every part earns its place.
What I care about
What I weigh going into a project or a role - each with one example from my own projects
Tools I'd actually use overthings that only demo well
e.g.App.lya job-hunt bot I still use every week
Something people come to depend on overshipped and forgotten
e.g.ReliaNeta fault-tolerant network for a disaster or war zone
How a system feels to use overwhether it merely runs
e.g.This Sitedesigned in Figma before a line of code
Adapting through configuration overa rewrite for every new case
e.g.Facial Recognition Systemfour services that each scale on their own
How I work, and where I’m strong
How I go about a project - the principles behind it, one at a time
The contract comes before the code
The hard part is done before the typing starts
Failure is the expectation, not the exception
If you can't watch it run, it isn't done
The stack is a tool, not an identity
Good code reads like its own documentation
The prompt is the spec
Featured
One build worth opening, the people who've vouched for the rest, and the toolkit behind it.
When I'm not shipping
The same curiosity, pointed at something other than a screen.
I like owning something from the first sketch to the version running in production - if that's the kind of work you have, tell me what you're building.
Built with Next.js, TypeScript & Tailwind CSS.
© 2026 Gaurav Divecha. All rights reserved.