Nikhil Bajaj — one person, many worlds
I build systems. Some run on code. Some run on stories.
Engineering Leader. Novelist. Student of mythology, technology, and human behavior.
At a glance
I build engineering organizations that scale without losing reliability, clarity, or speed.
Twenty years building and leading the engineering organizations behind enterprise-scale software.
- 20+ years in engineering leadership
- Led 60+ engineers across six teams
- $50M+ ARR platforms
- AI-first engineering operations
- Enterprise SaaS · global delivery (US · UK · APAC)
- Gurgaon, India
Trusted with systems at
Builder, storyteller, systems thinker
- Builder engineering organizations that scale without breaking.
- Storyteller four novels, three universes, one obsession.
- Systems thinker the same patterns under all of it.
One person, a few different worlds.
Selected wins
Proof, before the prose.
- 15 → 60+ Scaled the engineering org Organizational capacity that kept pace with the business, not behind it.
- ~60 → 95%+ On-time delivery, lifted Execution leadership could finally plan and commit against.
- 40% Fewer production incidents Less customer impact, lower operational risk on revenue-critical systems.
- 99.9% Uptime on $50M+ ARR platforms Protected revenue and the enterprise trust the contracts depend on.
How I lead
A few things I’ve stopped arguing about.
- I make reliability boring on purpose.
- Clarity beats control.
- I’d rather grow a team than supervise one.
- Systems outlast heroics.
Explore further
- The Builder The longer version of how I think about building organizations — the operating system, the calls, the scars.
- How I Lead A short stack of convictions that survived contact with reality.
- The Storyteller The questions behind the fiction, and the mind that keeps building worlds.
- The Mind The patterns connecting all of it — what keeps reappearing under the work and the wondering.
- The Journal Notes from the desk, where the engineering and the fiction keep arguing.
Currently
- No check counts until we’ve watched it fail.
- A myth is a runbook that survived long enough to sound like magic.
- A feature is not an outage. A deadline can raise its priority. It does not make it a P0.
- The agent that builds the thing doesn’t get to sign it off.
- Reliability is mostly trust, expressed in numbers.
- Lately: what a green dashboard is actually telling me, and what it can’t.
One more question
What are you building?
If you’re weighing org design, reliability, or how AI reshapes a team without breaking it — that’s the conversation I’m here for.