How I Lead Engineering Teams
My approach to building teams that deliver great software while growing as engineers and people
Servant Leadership in Practice
I believe in creating psychologically safe environments where teams feel empowered to take calculated risks, grow meaningfully, and deliver exceptional results through collaboration and ownership.
Process Innovation
When teams get stuck, I focus on removing roadblocks and optimizing workflows—like switching from Scrum to Kanban to unlock 50% velocity gains.
People-First Leadership
I prioritize psychological safety, mentorship, and growth opportunities. Engineers don't just deliver—they thrive and become force multipliers.
Agent Workflows, Real Results
I drive team-wide adoption of agentic coding tools like Claude Code and Cursor the same way I lead any process change—with clear standards, not mandates. The result is faster dev cycles without cutting corners.
My Technical Leadership Principles
How I make technology decisions that support both business goals and team happiness
Business Value Over Complexity
I choose proven technologies that solve real problems rather than chasing the latest trends. Reliability and team productivity matter more than being cutting-edge.
Technical Debt as Investment
Technical debt isn't inherently bad—it's a tool. I help teams make conscious trade-offs between speed and maintainability based on business priorities.
Quality Through Ownership
The best quality comes from engineers who own their work. I establish clear standards then trust my team to execute with autonomy and pride.
Measurable Technical Impact
Results from combining leadership and technical excellence