Leadership

Technical leadership is about multiplying the effectiveness of the people and systems around you.

Technical Mentorship

Regular 1:1s focused on career growth, not just task management. I help engineers develop system design intuition, security awareness, and the judgment to make good trade-offs under uncertainty. I believe the best mentorship happens through pairing on real problems, not abstract exercises.

Code Review Culture

I advocate for reviews that teach, not just gatekeep. Every review comment should explain the 'why' — helping the author build mental models, not just fix the immediate issue. I set the standard by writing thorough reviews myself and celebrating when others do the same.

Cross-Team Collaboration

Complex systems problems rarely fit within one team's boundary. I build alignment across teams by writing clear technical proposals, facilitating design reviews, and ensuring shared infrastructure decisions are understood by all stakeholders.

Incident Leadership

Calm under pressure, structured in approach. During incidents, I focus on restoring service first, then drive blameless postmortems that produce actionable improvements. I document patterns to help the team respond faster next time.

Staff-Level Signals

  • Scope beyond team: Driving initiatives that impact multiple teams and the broader engineering organization.
  • Technical strategy: Making architectural decisions that consider long-term maintainability, not just immediate delivery.
  • Force multiplier: Building tools, patterns, and documentation that make the entire team more effective.
  • Ambiguity navigation: Taking ill-defined problems, breaking them down, and driving them to clear outcomes.