I study how systems fail, then build against it.

My background is in backend engineering across payment, authentication, and distributed systems. Over time, that pushed me toward a deeper question: not just how systems work, but how they break under real conditions.

That changed the way I build. I think in terms of operational pressure, bottlenecks, hidden coupling, recovery paths, and visibility.

Today, my work sits at the intersection of software delivery, resilience, and technical judgment — building systems that are practical, stable, and ready for scale.

I am especially drawn to systems with real consequences: payment flows, authentication layers, queue-heavy workflows, and the kind of infrastructure where ambiguity becomes expensive quickly.

Principles

  • Design for failure, not just function
  • Prefer observability over guesswork
  • Treat scale as a systems problem
  • Build with clarity, not noise

Focus Areas

  • Backend systems
  • Payments and authentication
  • Distributed workflows
  • Reliability and failure analysis