About
One engineer.
No handoffs.
I am a product engineer in Mumbai. I spent two and a half years building and then running the software an events company operates on, starting as an intern and finishing as the person who owned the servers, the pipeline and the team. The interesting part was never the feature list. It was the constraint nobody mentioned until week three.
- 01
The person you brief is the person who writes it
There is no team behind me that the work gets passed down to. Whatever you explain on the first call is heard by the one who then builds it.
- 02
Nobody learns on your project
Agencies get burned when a name on the pitch turns into a junior on the repo. That substitution cannot happen here, because there is nobody to substitute.
- 03
The ceiling is real, and I say so early
One engineer has a limit. If a build needs more hands than I have, you hear it before you sign rather than in week six, and I will not quietly subcontract it.
What I am good at
Holding a whole system in my head. The diagrams on the work pages are not decoration. They are how I think, and they are why the modules in a build I ship do not quietly grow dependencies on each other.
Also: the unglamorous half. Deploys, migrations, the slow query nobody noticed, the export the client actually wanted. That work is why4 systems are still running.
What I will talk you out of
Software you do not need. A fair number of enquiries turn out to be a process problem wearing a software costume, and the honest answer is a rule and a shared sheet.
Rewrites for their own sake, features nobody asked for, and anything where I would end up the only person who understands it with no plan for that. I say so on the first call, not in week six.
Tools
What I reach for.
Front end
- TypeScript
- React 19
- Next.js
- Astro
- Tailwind
- Framer Motion
- GSAP
Back end
- Python
- Django
- Flask
- Node.js
- Prisma
- MySQL
- PostgreSQL
AI & payments
- AWS Bedrock
- OpenAI
- SSE streaming
- Playwright
- Razorpay
- Stripe
Ship & run
- Linux VPS
- Nginx
- Gunicorn
- PM2
- Vercel
- NextAuth
None of this is a religion. If your team is on Django and Vue, I will write Django and Vue. Handing a codebase to someone who has to learn it first is a bad outcome dressed as a preference.
Bling Square Events · Feb 2024 – Aug 2026
One company.
Four titles. Thirty-one months.
- Jul – Aug 2026Full stack developer, contractBack on contract to keep the production applications running and shipping.
- Sep 2025 – Jun 2026Full stack developer & team leadSprint planning, code review, and a team of two to three junior interns. Owned three production modules outright, plus the infrastructure and the CI/CD pipeline underneath them.
- Aug 2024 – Aug 2025Full stack developerFull ownership of production modules in Django and React, against real business workflows rather than tickets.
- Feb – Aug 2024Web developerWhere it started. Python, Django, and the first parts of what became Sarvagun.
Where else to look.
Mumbai, IST · UTC+5:30. Replies within a working day.