Fifteen years of systems, one person shipping them
I am a staff-level software engineer. For most of fifteen years that meant distributed systems and cloud-native backends inside large organisations — the kind of work where a design review has eleven people in it and the interesting problem is usually two layers below the one you were asked about.
Currently I work at a large enterprise software company on its content management platform: serverless backend services, a PWA-based player shipping across ChromeOS, Windows, Android, BrightSign and LG webOS, and large-scale enterprise replatforming migrations. Before that, backend systems at two e-commerce companies, and seven years at a consumer electronics manufacturer.
What changed
AI-assisted development changed the shape of what one engineer can finish. Not what one engineer can start — that was never the constraint. The constraint was always the long tail: the admin screen, the consent banner, the sitemap, the third data source, the deploy pipeline, the documentation. The work that is not hard but is irreducibly large.
So I tested it properly rather than arguing about it. Three production platforms, built end to end, alone. Architecture, data pipelines and infrastructure are mine; a lot of the typing is not. Two are still running. The third runs a real business day to day — I built it and still maintain it, while someone else operates it.
The honest summary of what I learned: the leverage is real and it is not free. It moves the bottleneck from writing code to reviewing it, and a team that does not move its guardrails at the same time ships faster and worse. Most of what I now know about this is about where to put the constraints — in a database role rather than a prompt, in a test rather than an instruction.
What I take on
Work where the interesting part is the system rather than the interface. AI pipelines that have to be correct rather than impressive. Products that need to exist before a team can be hired to maintain them. Teams that are already shipping and want AI-assisted development to make that faster without making it worse.
I am straightforwardly bad at some things. I am not a designer, although I have opinions and can execute a system. I do not want to own a growth function. And if a problem is better solved by a specialist agency than by one engineer, I would rather tell you that in the first conversation than discover it in month three.
Where to find me
The code is on GitHub, the career history is on LinkedIn, and the fastest route to a reply is email. I am based in Noida, India, and work with teams in most time zones.