Principal Engineer turned Engineering Manager with 12+ years building distributed systems at scale. Focused on developer platforms, infrastructure reliability, and high-performance teams.
Background and philosophy
I started my career writing low-latency trading systems in C++, then moved into distributed data infrastructure as the scale problems became more interesting. Over the past four years I have led engineering teams of 10–30 people across two continents, owning the full lifecycle from architecture through incident response.
I believe the highest-leverage work an engineering leader can do is reduce friction: clear interfaces, ruthless observability, and fast feedback loops. I write code every week and prefer being in the critical path of at least one hard technical problem per quarter.
Outside work I contribute to open-source database tooling, occasionally speak at systems conferences, and am unreasonably interested in compilers.
Technical depth and leadership surface area
Selected roles and achievements
Owned the developer platform and cloud infrastructure org. Built the internal developer portal from scratch, reducing mean time to first deployment for new services from 14 days to 4 hours.
Technical lead for the real-time data mesh product. Architected a distributed query engine on top of ClickHouse and Apache Arrow that handled 2M events/sec at p99 < 50 ms.
Core infrastructure team. Owned the Kafka-based event backbone and built the schema registry service that managed 4,000+ schemas across 90 microservices.
Low-latency order routing in C++ on Linux. Reduced round-trip latency of the execution engine from 280 µs to 38 µs through careful memory layout and kernel bypass networking.
Placeholder details — replace before publishing