I’m a Software Architect and Engineering Leader with over a decade of experience building and scaling high-performing teams, driving technical strategy, and connecting engineering excellence with meaningful business outcomes. My path has spanned the full spectrum of engineering roles, including founding engineer, staff engineer, and engineering manager. Giving me both deep technical credibility and an appreciation for how organizations evolve as they grow.
I lead through conscious leadership principles and systems thinking. This involves creating clarity, empowering ownership, and cultivating environments where engineers can do their best work. I’ve built teams in fast-scaling startups, led company-wide technical initiatives, and architected solutions that became critical to business growth. What I enjoy most is translating ambiguous business goals into clear technical strategies and coaching my teammates to flourish not only in their current role, but beyond.
I thrive where technical excellence meets business impact: building scalable products, integrating AI-driven systems, or shaping engineering practices that balance speed with stability. My approach is product-minded, I care deeply that we’re not just building software well, but building the right software to move the business forward.
My leadership philosophy is rooted in presence, curiosity, and kindness. I lead as both an enabler and a demanding steward of excellence, empowering people to make decisions with confidence while holding a high bar for quality and craft. My goal is to build teams that thrive without constant oversight, where my eventual redundancy is a sign of success. I’d rather nudge than push, and model the behavior I expect rather than mandate it. The best teams don’t need constant steering, they understand the destination and have the trust and tools to get there.
I approach challenges through systems thinking: identifying the loops and leverage points that shape behavior. Often, organizational or technical friction isn’t about individuals, but about the systems around them. My role is to help people see those systems clearly, and to make small, high-impact adjustments that produce long-term change.
Conscious leadership principles guide my interactions: taking responsibility instead of assigning blame, being open to feedback, and showing up with curiosity over certainty. Over time, that mindset builds teams where accountability feels empowering and where learning and performance naturally reinforce one another.
I believe in intentional communication and thoughtful writing over noise. The 37signals guide to internal communication captures this well.
“Urgency is overrated. ASAP is poison.” I assume nothing is urgent unless it’s explicitly stated. I prefer asynchronous written communication and focused, purposeful meetings with clear outcomes. I check Slack and email periodically, not continuously, and I don’t expect or require instant responses. Calm, focused teams do their best work.