Building what needs to be built.
There's something about startup energy I've never been able to resist — the speed, the ambiguity, the thrill of building the plane while flying it. Since 2012, that pull has had me showing up early, laying the tech foundation and wiring up the architecture — then sticking around to turn the fresh engineers on the team into thoughtful ones, not just fast ones.
Not particularly passionate about startups. I just accidentally survived 13+ years building things on the internet that didn't permanently crash. Which, in startup terms, is called "strong stability."
I don't "thrive in chaos." I've just attended enough urgent alignment calls to know exactly where the product will break — before it breaks in production.
Early-stage environment? Of course. Unclear requirements, a Google Doc named Final_v3_ThisOneFinal2, and that legendary line: "Can we launch by tomorrow? It's just a small change."
Frameworks come and go like IPL teams changing captains. That's why I stick to fundamentals — hype doesn't scale, architecture does.
I don't "drive innovation." I ship products. I don't "build culture." I make sure nobody blames DevOps when production goes red.
If you're building the next big thing and need someone who can turn chai-time ideas into actual features, convert chaos into execution, and stay calm when the AWS bill suddenly looks emotional — let's talk.
- WorkFlow — a self-hosted project & knowledge management platform for small engineering teams: sprints, tasks, a knowledge base, decision records, release notes, team chat, and status digests, in one workspace.
- WireFlow — "Build the screen before you build the product." A shared canvas where the whole team shapes a prototype together — drag-drop wireframing, copy review & i18n, pinned comments — then ships it as a clean, measured developer spec. No design license required.
#StartupSurvivor · #JugaadWithArchitecture · #ShippedInProduction