I started writing code because I wanted to build things—not just any things, but solutions that actually made people's lives easier. That curiosity has shaped everything I've done since.
Over the years, I've grown from a hands-on developer into someone who leads teams and designs systems at scale. But I've never stopped being the person who loves diving into the details, understanding how things work, and figuring out how to make them better.
What drives me is the challenge of turning ambiguity into clarity. When someone says “we need to build this, but we're not sure how,” that's when I get excited. I enjoy the process of asking the right questions, exploring the trade-offs, and finding the path that balances speed with sustainability.
I've built full-stack applications from scratch, led engineering teams through complex product launches, and designed architectures that scale without becoming nightmares to maintain. But more than any specific technology, what I bring is a way of thinking—pragmatic, thorough, and always focused on what will actually work in the real world.
When I work with teams, I try to be the kind of leader I always wanted—someone who listens, who explains their reasoning, who trusts people to do great work while being there when they need support. Building software is a team sport, and the best results come when everyone feels ownership over what we're creating together.
If you're looking for someone who can bridge the gap between vision and execution—someone who's as comfortable in a strategy meeting as they are debugging a production issue—I'd love to chat.
