What I work on / The systems layer
Behind every good product is a system you can trust.
I focus on the foundations that make data available, dependable, and usable. This is a map of the engineering problems that interest me, not a claim about any particular employer or production environment.
Ingestion & data pipelines
Event and batch processing, data contracts, change management, orchestration, schema evolution, and designing for replay.
Platform & developer experience
Building abstractions that let other engineers ship independently without making every team become an infrastructure team.
Reliability & recovery
Thinking about incident response, observability, error budgets, graceful degradation, and the difference between a green dashboard and a healthy system.
Pragmatic distributed systems
Making conscious tradeoffs around latency, consistency, throughput, simplicity, and where complexity should live.
Engineering principles
How I approach
the hard parts.
Make failure understandable.
Systems fail. Good ones give operators clear signals, safe recovery paths, and fewer mysteries at 2 a.m.
Optimize for the next engineer.
Discoverability, documentation, and sane defaults are part of the interface, not optional polish.
Prefer explicit contracts.
A good boundary states what it promises, what it cannot guarantee, and how change is managed.
Measure what users feel.
Throughput matters, but so do freshness, trust, time to first success, and time to recover.
Career
From engineering to data platforms.
Now: Software Engineer, Data Infrastructure on Persona's Data Platform team.
Our team's remit spans streaming and batch ingestion, change data capture, an Apache Iceberg data lake, warehouse integrations, and query and low-latency serving systems. This is context about the team's platform, not a claim of end-to-end individual ownership.
Previously: Data engineering and architecture at Twitch, Gem, and Slack; desktop software programs at Slack and Apple; software stability engineering at Qualcomm.
See the complete career timeline ↗Experience
The concise version.
For a public, privacy-conscious overview of my technical background, see my résumé.