Developing Your Leadership Skills toward Principal Engineering
Ben Linders · rss · 2026-04-15 source ↗ Reader 🖥️
Becoming a principal engineer requires deliberately cultivating leadership skills beyond technical expertise — especially by bringing skills from outside work, engaging in tech communities, and public speaking — and these activities create compounding positive feedback loops that accelerate career growth.
practical · expository — A journalistic summary of Sophie Weston's QCon London talk. Practical: argues that aspiring principal engineers should take specific actions (community involvement, public speaking, bringing non-work skills to work) to advance their careers. Expository form — presents Weston's advice with quotes rather than building an independent argument.
Structure
| Part | Role |
|---|---|
| Reframing principal engineering as leadership, not just technical skill | Context-setting — redefines the goal to expand the reader's understanding of what 'principal engineer' means |
| Skills from life outside work (parenting, sports, volunteering, gaming) | First pillar of evidence — demonstrates that leadership skills are acquired in non-obvious places |
| Flexible career paths and 'squiggly careers' | Organizational enabler — argues that companies should support non-linear progression |
| Community involvement: meetups, conferences, volunteering, organizing | Second pillar of action — concrete activities that build network, visibility, and skills |
| Public speaking as a learnable skill and career accelerator | Third pillar of action — the most challenging activity, presented as accessible to anyone |
| Positive feedback loops and systems thinking framing | Synthesizing conclusion — the activities compound rather than merely accumulate |
| Intrinsic motivation coda: do it because it excites you | Values framing — reframes career benefits as side effects, not goals |
Key terms
- broken comb Career Development
A skill profile with deep expertise in several areas (the long teeth) and gaps between them — contrasted with T-shaped (one deep area) or generalist profiles. Having more 'teeth' from diverse life experiences makes you more effective as a principal engineer - squiggly careers Career Development
Non-linear career paths that include role shifts, moving in and out of management, lateral moves — presented as a positive pattern rather than a lack of focus - positive feedback loops
The compounding dynamic where each leadership activity (learning, meetups, speaking, organizing) feeds into the next, creating accelerating returns rather than linear accumulation - whole self Career Development
Bringing the full range of your skills, experiences, and identity — including those developed outside work — to your professional role, tied to psychological safety
Propositions
- explicitcorroboratedBecoming a principal engineer requires influence, communication, and strategy — not just technical skillconf: highextends ←Alex Ewerlöf's Post · p2 — Ewerlöf's claim focuses on technical depth as Staff's distinguishing value versus EM; the other document adds that influence, communication, and strategy are also required for the adjacent principal-engineer level — a complementary, not contradictory, fuller skill picture one level up.supports ←Stop Just Writing Code. Start Leading Agents: The Staff Engineer’s AI Edge · p1 — Both argue staff/principal-level engineering is defined by influence, communication, and direction-setting, not technical skill alone — Mokhtar extends this claim specifically to leading AI agents.
- explicitdevelopedSkills developed outside of work (parenting, sports, volunteering, gaming) are transferable and valuable for principal-level leadershipconf: highextends ←Introducing The Founder Mindset: Tim Ferriss on Experiments, Risk, and Freedom · p10 — Ferriss sharpens the general claim that outside-work skills are transferable and valuable into a specific competitive mechanism: deliberately combining two domains where you're each only in the top 25%, rather than any outside skill counting equally.
- explicitThe activities of learning, community involvement, speaking, and organizing multiply rather than merely accumulate — they create positive feedback loopsconf: high
- explicitPublic speaking is a learnable skill, not a natural talent, and anyone can develop itconf: high
- explicitCareer benefits from community engagement should be treated as side effects, not primary goals — intrinsic motivation is the right driverconf: high
- implicitOrganizations that support flexible, non-linear career paths retain better talent and produce more effective principal engineersconf: medium
- implicitThe path to principal engineering is individual and non-prescriptive — there is no single correct sequence of stepsconf: medium
- explicitNetworking is instrumentally necessary for career advancement at the principal level, not merely nice to haveconf: high
Arguments
Aspiring principal engineers should deliberately cultivate leadership skills from outside-work activities strength: medium
Explicit premises:
- Principal engineering requires influence, communication, and strategy beyond technical skill
- Parenting teaches negotiation, time management, stakeholder management, adaptability, and influence
- These are all leadership skills applicable to engineering leadership
Implicit premises:
- Leadership skills are transferable across domains — the context in which they are learned does not limit where they can be applied
- Self-awareness about one's own non-work skills is sufficient to transfer them — the article assumes recognition leads to application without discussing how to bridge domains
- The skills listed (negotiation, time management, etc.) are actually the bottleneck skills for principal engineers — not, say, systems thinking, political navigation, or business acumen
Inferences:
- If outside-work skills are this valuable, organizations should recognize and value them in promotion decisions — but most promotion frameworks don't
- The argument implies that people without rich outside-work experiences (e.g., those consumed by caregiving without support, or facing financial constraints) may be at a disadvantage in developing these 'bonus' skills
Community involvement and public speaking create compounding positive feedback loops that accelerate growth toward principal engineering strength: medium
Explicit premises:
- Learning leads to meetups, meetups lead to speaking, speaking leads to organizing
- Each activity builds network, visibility, skills, and confidence
- These reinforce each other in a systems-thinking positive feedback loop
Implicit premises:
- The feedback loop actually starts — the initial activation energy to attend a first meetup or give a first talk is treated as a small step, but for many engineers it is a significant barrier
- The loop is predominantly positive — negative feedback (bad talk experiences, toxic communities, opportunity cost of time spent on community vs. deep technical work) is not considered
- Community involvement is accessible to all engineers equally — no consideration of geographic, financial, family, or neurodiversity constraints
Inferences:
- If the feedback loops are real, engineers who start community involvement earlier gain compounding advantages — creating a Matthew effect where early starters pull further ahead
- The argument provides no way to evaluate when community involvement has diminishing returns relative to deep technical work
Narratives
- Weston describes how parenting taught her negotiation, time management, multitasking, stakeholder management, adaptability, and influence — all leadership skills she applies as an engineer
→ Makes the abstract claim about non-work skills concrete and personal; implicitly argues that the most unexpected sources of skill development may be the most valuable - Weston recounts her own transformation from a terrified first-time speaker to a confident QCon presenter: 'If you'd seen me the first time I got up to speak in public, you would never have predicted... that one day I would be here speaking at QCon'
→ Serves as proof-by-example that public speaking is a learnable skill; also builds Weston's credibility by showing vulnerability and growth rather than presenting herself as a natural - The positive feedback loop narrative: learning → meetups → speaking → organizing → 'you're at the very centre of the communities that once inspired you: Contributing, leading, and shaping them'
→ Transforms a list of discrete career tips into a systems-level narrative of compounding growth; implicitly argues that the whole is greater than the sum of its parts
Questions addressed
- ✅ What skills beyond technical expertise does a principal engineer need?
Influence, communication, strategy, and a broad 'broken comb' skill profile including skills developed outside work - ✅ How can engineers develop leadership skills outside of their day job?
Through community involvement (meetups, conferences, volunteering, organizing) and public speaking, plus recognizing transferable skills from personal life - ⭕ How do these non-technical activities actually lead to career advancement?
- ⭕ How should organizations change their promotion frameworks to value these broader skills?
- ⭕ What is the right balance between investing in community/speaking and investing in deep technical work?
Gaps
- incompleteThe article never addresses the tension between breadth (community, speaking, diverse skills) and depth (deep technical mastery). Principal engineers are typically expected to have both, but the article focuses entirely on the breadth side. An engineer following this advice exclusively might develop excellent leadership skills while falling behind technically — which would undermine their credibility in the role.
Read next: Will Larson's 'Staff Engineer' or Tanya Reilly's 'The Staff Engineer's Path' for the technical depth dimension; also the original talk video for potential coverage of this balance - incompleteThe feedback loop claim is asserted via metaphor ('systems thinking terminology') but not demonstrated. There is no evidence that these activities actually compound rather than merely accumulate. The mechanism by which speaking leads to organizing leads to centrality is never specified — it could equally be a survivorship bias narrative.
Read next: Research on career capital theory (Cal Newport's 'So Good They Can't Ignore You') for a more rigorous framework on how skills compound - uninformedNo acknowledgment of structural barriers to community involvement and public speaking: geographic isolation, caregiving responsibilities, financial constraints, neurodivergence, visa/immigration constraints that limit professional visibility. The advice assumes a degree of privilege and freedom that many engineers don't have.
Read next: Literature on equity in tech careers; Lara Hogan's work on sponsorship as an alternative path for underrepresented engineers - incompleteThe article is a journalistic summary of Weston's talk, not an independent analysis. The real intellectual content is in the original QCon presentation, which likely contains more nuance, caveats, and audience interaction than this compressed version captures.
Read next: Watch the original talk: 'The Principal Engineer's Path' by Sophie Weston, QCon London
Related documents
- 5 Things World-Class Engineers Do That You Don't
- The engineering manager role is splitting in two
- How to Turn Individual Talent into Organizational Excellence
- Update on Software Engineering Career Ladder
- You Don't Get to Create Anything (Still Burning: Beck + Randy Shoup on Jevons paradox and distributed systems under AI)