Skip to content

About

I Build Backend Systems That Don't Break at 3am

Senior Technical Lead with 7+ years of experience building backend systems for fintech and e-commerce — the kind where downtime costs real money.

Based in New Delhi. Open to remote opportunities worldwide.

Gautam Thapa, backend engineer and technical leader

The Short Version

From Shipping Features to Owning Outcomes

I started my career focused on writing code and shipping features. Over time, my work shifted toward owning outcomes — leading teams, making architectural decisions, and taking responsibility when production breaks at 2am.

My work has spanned very different kinds of systems. I've built enterprise ERP platforms used by large institutions, worked on patent-pending AI technology for US e-commerce brands, and architected financial systems processing 50,000+ transactions daily.

The common thread has always been the same: systems where failure isn't an option.

Along the way, I learned that the hard part isn't writing code — it's deciding what not to build, knowing when to take on tech debt intentionally, and making decisions teams won't regret six months later.

That's the work I care about now.

My Approach

How I Think

I don't believe in:

  • Over-engineering for hypothetical scale
  • Choosing technology because it's trending
  • Perfectionism that delays shipping
  • Cleverness over clarity

I do believe in:

  • Boring technology that just works
  • Systems that fail gracefully
  • Documentation that explains why, not just what
  • Trade-offs made intentionally, not accidentally

The best systems I've built aren't clever. They're predictable, debuggable, and don't wake anyone up.

Proof

Track Record

Employee of the Year (2020)

Recognized for technical leadership at I-MADE

4× Faster Releases

Improved deployment frequency from monthly to weekly through CI/CD

99.9% Uptime

On systems processing 50K+ daily transactions

Enterprise Trust

Built platforms used by IIT Kanpur and IIT Delhi

When I'm Not Coding

Reading about how teams solve scaling problems, writing to clarify what I've learned, and occasionally mass-configuring a Prometheus alert that will never fire.

Connect

Let's Connect

Open to senior backend and technical leadership roles where reliability is non-negotiable.