I’m Abhinav, an independent engineer with seven years building web products. I work directly with founders and product teams who need to launch, replace a manual workflow, or make an existing product easier to use and maintain. See the engagement options and prices.
You can bring me the problem without having to work out which layer is responsible. I work across the interface, API, database, and deployment, using React, Next.js, TypeScript, and Postgres. That lets me follow a slow screen or a broken workflow through to its cause and take responsibility for the fix.
We agree on what success looks like before work starts. You see working demos along the way, and your team gets the documentation, tests, and walkthrough needed to keep the product moving after I leave.
What you can count on
Know what you are paying for
You get the outcome, scope, and a fixed project or monthly price in writing before work starts.
Try the progress yourself
Regular demos let you check the work against the problem and give feedback while it is being built.
Keep control of your product
You own the code and get the tests, docs, and handover your team needs to run and extend it.
Where I’ve been
Independent engineer
Self-employed
Fixed-scope engagements with fintech, logistics, and publishing teams, usually as the sole engineer taking a product from rough spec to production.
Contract lead engineer
Various product teams
Embedded with small teams as the senior engineer on one initiative — typically a rebuild or a performance rescue on something already in production.
Freelance full-stack developer
Self-employed
Built and maintained web applications for early-stage startups, often as the first engineer a founder hired after building an MVP themselves.
Product engineer
Early-stage SaaS
First engineering hire on a small team. Learned what happens when nobody writes the migration down.
What working together looks like
Know what needs to change
We spend thirty minutes on the result you need and what is blocking it. You leave knowing whether I can help and what the next step is.
Agree on success and cost
Before work starts, you get the outcome, the approach, the price, and the limits in writing. You know what you are paying for and how we will judge the result.
See progress as it happens
Try the work in demos, read the code, and follow a written update every day. You can check that we are solving the right problem while there is still time to adjust.
Keep moving after handover
Your team gets the code, documentation, tests, and a walkthrough so they can run and extend the product themselves.
Currently taking new work — next start october.
Book a call