I work with software systems and cloud infrastructure. My background spans backend engineering, cloud architecture, and engineering leadership.
Over the past few years, I’ve spent most of my time thinking about how systems grow, where they break, and why seemingly small technical decisions tend to become expensive later.
I started in engineering with a strong technical foundation, then gradually moved into roles where I reviewed systems, led teams, and helped make architectural decisions.
Working across different teams and environments taught me that most technical problems are not caused by lack of technology, but by misaligned assumptions, unclear ownership, and premature complexity.
My background sits at the intersection of backend engineering, cloud infrastructure, and system design. I’ve worked across both technical delivery and technical leadership roles.
For a more detailed professional history, my full resume is available upon request.
Outside of professional work, I spend time on things that help me stay balanced and curious: