Lead Engineer — online marketplace platform
Current Oct 2026 — nowLeading the engineering behind a consumer marketplace — the architecture, the backend systems and getting the work out the door.
Abhishek Singh
I'm a software engineer with 11+ years building the behind-the-scenes machinery of web products — the part that has to stay fast and stay up when thousands of people use it at once. Lately I also build AI-powered products, including one of my own.
Every app you use has a visible half and an invisible one. I work on the invisible half — and I like the problems nobody else wants to open.
Most of my career has been spent on the backend: the servers, databases and pipelines that sit behind an app and do the real work. Making them fast, making them reliable, and making sure they don't fall over on the busiest day of the year.
I've built for industries where mistakes are expensive — banking and compliance systems, security platforms, logistics. That kind of work teaches you to plan for what happens when things break, not just for when they work.
What I enjoy most is ownership. Hand me a blank page and a vague problem, and I'll come back with something running in production. Right now that is an online marketplace platform — and, after hours, finding out where AI genuinely helps and where it's just a demo.
Making software respond instantly instead of "in a moment" is worth more than most new features.
Designing for the day something fails — because eventually, something always does.
Not demos. Real products with real users, real costs and real edge cases.
Free tools published for other developers. If it isn't shipped, it isn't finished.
Every box is somewhere a request can get slow, or get lost. Most of my work is making sure it does neither. The milliseconds are illustrative — the gap between the two runs is not.
Deep in the .NET and cloud world, comfortable most places else. The chart is years of use, not a self-rating out of ten — click any row or chip and the timeline below filters to the roles behind it.
Where most of the eleven years went.
Making the slow parts fast, and the heavy parts async.
Shipping it, running it, watching it.
Recent, and in production rather than in demos.
Enough to build and wire a real interface.
The habits that survive contact with a deadline.
Marketplaces, logistics, legal services, banking, security, field operations and publishing — the industries change, the craft doesn't.
Leading the engineering behind a consumer marketplace — the architecture, the backend systems and getting the work out the door.
Led a brand-new platform built from the ground up on Microsoft Azure — designing how the whole system fitted together and taking it to launch.
The only engineer on a platform law firms use to run cases, documents and payments. Rebuilt the engine underneath it so the app responded around 45% faster, and moved the slow jobs into the background so nothing kept people waiting.
Built the systems behind customer verification and compliance checks for a financial platform, and owned the pipelines that process trades end to end. Cut production incidents by more than 20%, reviewed code and mentored other engineers.
Led the engineering behind a product that spots security weaknesses in real time, managed a small team, and halved the time it took to get new releases out the door.
Handled data at scale: importing millions of records at a time and making the system's queries roughly twice as fast.
Built publishing and analytics tools, led a team of 10–12 engineers, and owned how the apps were put together from the interface down to the data.
A product of my own, with real customers paying for it.
Tools I built for myself first, then published free for anyone who hits the same friction.
An AI coding assistant that lives inside Visual Studio.
Type-safe routing for Angular, generated from the routes you already have.
app.routes.ts — no second source of truth to keep in step.A ready-made component for showing data as a circular chart.
A calendar and date picker, in five languages.
The "prove you're not a robot" check, made simple to add.
The @angx packages live under the
angx-libs
organisation, ng-typed-routes under my own account, and all of them on
npm.
Interesting engineering problems, AI products, or just a good conversation about either. Send me a message and it lands in my inbox.
or find me here