Aman Kumar Singh — Team Lead & Senior Software Engineer. React, Next.js, Node.js, NestJS, PostgreSQL, Redis, and AWS.
Also searched as Bombay.
Mumbai is India’s financial capital, and its software demand follows directly: trading platforms, banking integrations, insurance systems, and media at national scale. My insurance and financial-platform experience — including a system handling ₹10Cr+ annually — maps onto Mumbai work more directly than onto anywhere else in the country.
I am Aman Kumar Singh — a Team Lead and Senior Full Stack Engineer based in Noida with 6+ years of experience, 15+ production applications shipped, and teams of 5–10 engineers led. Where India’s financial-systems engineering actually happens.
Mumbai engagements run remote-first from my base in Noida, with a scheduled on-site visit for kickoff or a major release when it is worth the flight. Everything is on IST, so there is no timezone gap — same working day, same standup.
What I build for Mumbai clients
—Payment flows, ledgers, and reconciliation that has to balance to the rupee.
—Account and transaction systems with idempotent writes and a full audit trail.
—Policy platforms, premium calculation, and renewal workflows.
Yes. Mumbai engagements run remote-first from my base in Noida, with a scheduled on-site visit for kickoff or a major release when it is worth the flight. Everything is on IST, so there is no timezone gap — same working day, same standup.
What kind of software do Mumbai businesses usually need?+
My insurance and financial-platform experience — including a system handling ₹10Cr+ annually — maps onto Mumbai work more directly than onto anywhere else in the country. Concretely, that tends to mean payment flows, ledgers, and reconciliation that has to balance to the rupee, account and transaction systems with idempotent writes and a full audit trail, and policy platforms, premium calculation, and renewal workflows. The stack is React and Next.js on the front end, Node.js and NestJS services behind it, PostgreSQL and Redis for data, and AWS for deployment.
Can you join an existing Mumbai team rather than build from scratch?+
Yes, and with an established Mumbai team that is often the better arrangement. I have led teams of 5–10 engineers and spent a lot of time in code review and mentoring, so joining an existing codebase to raise the standard — testing, CI, module boundaries, review culture — is familiar work rather than a compromise.
Who owns the code once a Mumbai project is delivered?+
You do, outright. For Mumbai work in particular — where I am usually not in the building — I plan the handover from the first sprint: readable module boundaries, a written architecture note, and setup documentation your team can follow without me. Ongoing support afterwards is a separate arrangement, never a dependency I engineer in deliberately.
How long does a first version take for a Mumbai project?+
A focused first version is typically 6–12 weeks depending on scope. Given that my insurance and financial-platform experience — including a system handling ₹10Cr+ annually — maps onto Mumbai work more directly than onto anywhere else in the country. I would rather ship a narrow phase one that works than a broad one that slips, so the first conversation with a Mumbai client is usually about cutting scope to the part that proves the idea.
Read the engineering writing
The reasoning behind how I build — 200+ articles on architecture, backend, and performance.