I don't just write software. I design systems that survive contact with reality.
I build digital products and platforms from the first idea to the operating system behind them - balancing architecture, delivery, and production realities.
← RETURN TO SYSTEM01 / ARCHITECTURE
Designing systems from the domain model to infrastructure.
02 / PRODUCT
Understanding the business goal, not only the ticket.
03 / DELIVERY
Taking products from the first commit to production.
04 / OWNERSHIP
Technical decisions, monitoring, maintenance and growth.
A product and platform career built through delivery, systems thinking, and iteration.
2016 · FOUNDATIONS
Started translating product ideas into usable interfaces and stable front-end architecture, with a strong bias toward maintainable delivery.
2019 · SYSTEMS
Shifted toward product-scale thinking: service boundaries, cross-team integration, and shared patterns that made delivery more predictable.
2022 · PRODUCT ENGINEERING
Led work across product discovery, engineering planning, and implementation so technical decisions stayed tied to business outcomes.
2025 · OPERATIONS
Focused on resilience, observability, and iterative improvement so systems keep delivering value beyond the initial release.
How I approach engineering decisions.
- 01
MAKE COMPLEXITY EXPLICIT
- 02
OPTIMIZE FOR CHANGE
- 03
OBSERVE BEFORE OPTIMIZING
- 04
BORROW COMPLEXITY, DON'T INVENT IT
- 05
SHIP SMALL, LEARN FAST
- 06
A SYSTEM IS MORE THAN ITS CODE