01
Systems Thinking First
Architecture starts with boundaries, dependencies, failure modes and operational cost.
Senior backend engineer working on low-latency trading infrastructure, matching engines, distributed systems and production-grade cloud platforms.
“I care less about how sophisticated a system looks and more about how well it behaves under pressure.”
Architecture starts with boundaries, dependencies, failure modes and operational cost.
Design explicit failure modes, bounded blast radius, observability and recovery.
Tail latency is a requirement, not simply an optimization exercise.
Technologies studied to production depth — internals, failure modes and tradeoffs.