Technical Leadership

Technical leadership at the staff/principal engineer level is distinct from management: it operates through technical influence, not authority. The primary levers are: setting and modeling engineering excellence standards (code quality, system design, testing discipline), mentoring junior and senior engineers through pairing and design reviews, establishing code review norms that are constructive rather than gatekeeping, and making it safe to raise concerns early (psychological safety). Will Larson's Staff Engineer and Tanya Reilly's "Being Glue" essays define the non-managerial leadership archetypes: Tech Lead, Architect, Solver, and Right Hand.

Key Points

• Technical vision: articulate a 12–24 month technical direction that connects engineering decisions to business strategy; written, shared, and revised quarterly based on new information
• Mentoring vs coaching: mentoring = sharing your experience and solutions (directive); coaching = asking questions to help the engineer discover their own solutions (non-directive); use both, situationally based on the engineer's experience and urgency
• Code review as teaching: effective reviews explain the "why" behind feedback, reference documentation or patterns, and separate blocking issues (correctness, security) from suggestions (style, alternatives); use "nit:" prefix for non-blocking comments
• Psychological safety measurement: Amy Edmondson's 7-question survey; teams with high psychological safety have higher deployment frequency, report more near-misses, and recover faster from incidents (Google Project Aristotle)
• Engineering excellence culture: celebrate well-written postmortems, reward engineers who find and fix systemic problems not just feature delivery, make tech debt visible and funded — culture follows incentives
• Influence without authority techniques: pre-socialize ideas with key stakeholders before meetings, use data to support positions (not just opinion), build a track record of correct technical calls, and acknowledge when others's approaches work better than your initial proposal
• Technical roadmap ownership: a staff engineer maintains a living technical roadmap (strategy doc) that prioritizes tech debt, platform investments, and capability gaps aligned to business OKRs; this is the primary deliverable of the role
• Staff+ scope: operates at the team-of-teams level; designs systems spanning multiple services, identifies cross-team technical dependencies, and removes organizational impediments to engineering velocity — not a senior IC who writes more code