Mostly software, startups, leadership, and the occasional rabbit hole. More long-form on the way.

Engineering Philosophy

• On Leadership Style I'm a builder at heart. I am unwilling to lead from a distance. I need a deep understanding of the technology that drives our business, at a level comparable to the engineers building it. That understanding helps me provide context, make better decisions, and earn credibility with the teams I lead. I set high standards and clear expectations, then tailor my leadership approach to the individual. Some engineers thrive with broad autonomy, while others benefit from more guidance - my job is to understand the difference and help each person perform at their highest level.
• On Hiring and Growing Engineering Talent I index on curiosity, agency, and autonomy when evaluating talent. Curiosity drives continuous learning and a desire to understand difficult problems, agency reflects ownership and initiative, and autonomy signals the judgment required to make sound decisions without constant direction.
• On Scaling Engineering Organizations I believe the best engineering teams are built around broad ownership. Engineers should feel accountable for outcomes, not just the individual components they own. Specialists provide leverage as complexity grows, but scaling should not come at the cost of ownership, accountability, or an understanding of the broader system.
• On AI-Assisted Development Engineers are increasingly becoming judges rather than authors. As AI accelerates implementation, the value of an engineer shifts toward problem framing, architectural judgment, validation, and decision-making. I encourage teams to stay on the leading edge of AI-assisted development while maintaining human ownership of system design, security, quality, and business outcomes.