summaryrefslogtreecommitdiff
path: root/notes/staff-engineer.gmi
diff options
context:
space:
mode:
authorPaul Buetow <paul@buetow.org>2025-02-21 10:55:25 +0200
committerPaul Buetow <paul@buetow.org>2025-02-21 10:55:25 +0200
commit5a76af565ea910512b0418c56437467068821fd6 (patch)
treed8ee7610db5f698703d5891eb9b6aabd1f699f14 /notes/staff-engineer.gmi
parenta30460cc038708e3a01cbe8cf4d90c6572e26784 (diff)
parent75655782fe8ad0b8b9b5fd26a6837e8a745b7268 (diff)
Merge branch 'content-gemtext' of codeberg.org:snonux/foo.zone into content-gemtext
Diffstat (limited to 'notes/staff-engineer.gmi')
-rw-r--r--notes/staff-engineer.gmi99
1 files changed, 97 insertions, 2 deletions
diff --git a/notes/staff-engineer.gmi b/notes/staff-engineer.gmi
index 6c184ee0..3d497f5d 100644
--- a/notes/staff-engineer.gmi
+++ b/notes/staff-engineer.gmi
@@ -1,11 +1,94 @@
# "Staff Engineer" book notes
-> Last updated 10.8.2023
+> Published at 2024-10-24T20:57:44+03:00
+
+These are my personal takeaways after reading "Staff Engineer" by Will Larson. Note that the book contains much more knowledge wisdom and that these notes only contain points I personally found worth writing down. This is mainly for my own use, but you might find it helpful too.
+
+```
+ ,.......... ..........,
+ ,..,' '.' ',..,
+ ,' ,' : ', ',
+ ,' ,' : ', ',
+ ,' ,' : ', ',
+ ,' ,'............., : ,.............', ',
+,' '............ '.' ............' ',
+ '''''''''''''''''';''';''''''''''''''''''
+ '''
+```
+
+## Table of Contents
+
+* ⇢ "Staff Engineer" book notes
+* ⇢ ⇢ The Four Archetypes of a Staff Engineer
+* ⇢ ⇢ Influence and Impact over Authority
+* ⇢ ⇢ Breadth and Depth of Knowledge
+* ⇢ ⇢ Mentorship and Sponsorship
+* ⇢ ⇢ Managing Up and Across
+* ⇢ ⇢ Strategic Thinking
+* ⇢ ⇢ Emotional Intelligence
+* ⇢ ⇢ Navigating Ambiguity
+* ⇢ ⇢ Visible and Invisible Work
+* ⇢ ⇢ Scaling Yourself
+* ⇢ ⇢ Career Progression and Title Inflation
+* ⇢ ⇢ Not a faster Senior Engineer
+* ⇢ ⇢ The Balance
+* ⇢ ⇢ More things
+
+## The Four Archetypes of a Staff Engineer
+
+Larson breaks down the role of a Staff Engineer into four main archetypes, which can help frame how you approach the role:
+
+* Tech Lead: Focuses on the technical direction of a team, ensuring high-quality execution, architecture, and aligning the team around shared goals.
+* Solver: Gets pulled into complex, high-impact problems that often involve many teams or systems, operating as a fixer or troubleshooter.
+* Architect: Works on the long-term technical vision for an organization, setting standards and designing systems that will scale and last over time.
+* Right Hand: Functions as a trusted technical advisor to leadership, providing input on strategy, long-term decisions, and navigating organizational politics.
+
+## Influence and Impact over Authority
+
+As a Staff Engineer, influence is often more important than formal authority. You’ll rarely have direct control over teams or projects but will need to drive outcomes by influencing peers, other teams, and leadership. It’s about understanding how to persuade, align, and mentor others to achieve technical outcomes.
+
+## Breadth and Depth of Knowledge
+
+Staff Engineers often need to maintain a breadth of knowledge across various areas while maintaining depth in a few. This can mean keeping a high-level understanding of several domains (e.g., infrastructure, security, product development) but being able to dive deep when needed in certain core areas.
+
+## Mentorship and Sponsorship
+
+An important part of a Staff Engineer’s role is mentoring others, not just in technical matters but in career development as well. Sponsorship goes a step beyond mentorship, where you actively advocate for others, create opportunities for them, and push them toward growth.
+
+## Managing Up and Across
+
+Success as a Staff Engineer often depends on managing up (influencing leadership and setting expectations) and managing across (working effectively with peers and other teams). This is often tied to communication skills, the ability to advocate for technical needs, and fostering alignment across departments or organizations.
+
+## Strategic Thinking
+
+While Senior Engineers may focus on execution, Staff Engineers are expected to think strategically, making decisions that will affect the company or product months or years down the line. This means balancing short-term execution needs with long-term architectural decisions, which may require challenging short-term pressures.
+
+## Emotional Intelligence
+
+The higher you go in engineering roles, the more soft skills, particularly emotional intelligence (EQ), come into play. Building relationships, resolving conflicts, and understanding the broader emotional dynamics of the team and organization become key parts of your role.
+
+## Navigating Ambiguity
+
+Staff Engineers are often placed in situations with high ambiguity—whether in defining the problem space, coming up with a solution, or aligning stakeholders. The ability to operate effectively in these unclear areas is critical to success.
+
+## Visible and Invisible Work
+
+Much of the work done by Staff Engineers is invisible. Solving complex problems, creating alignment, or influencing decisions doesn’t always result in tangible code, but it can have a massive impact. Larson emphasizes that part of the role is being comfortable with this type of invisible contribution.
+
+## Scaling Yourself
+
+At the Staff Engineer level, you must scale your impact beyond direct contribution. This can involve improving documentation, developing repeatable processes, mentoring others, or automating parts of the workflow. The idea is to enable teams and individuals to be more effective, even when you’re not directly involved.
+
+## Career Progression and Title Inflation
+
+Larson touches on how different companies have varying definitions of "Staff Engineer," and titles don’t always correlate directly with responsibility or skill. He emphasizes the importance of focusing more on the work you're doing and the impact you're having, rather than the title itself.
+
+These additional points reflect more of the strategic, interpersonal, and leadership aspects that go beyond the technical expertise expected at this level. The role of a Staff Engineer is often about balancing high-level strategy with technical execution, while influencing teams and projects in a sustainable, long-term way.
## Not a faster Senior Engineer
* A Staff engineer is more than just a faster Senior.
-* A staff engineer is not a senior engineer but a bit better. (But I want to be a senior engineer but a bit better).
+* A staff engineer is not a senior engineer but a bit better.
It's important to know what work or which role most energizes you. A Staff engineer is not a more senior engineer. A Staff engineer also fits into another archetype.
@@ -36,4 +119,16 @@ Sebactical: Take at least six months. Otherwise, it won't be as restored.
E-Mail your comments to `paul@nospam.buetow.org` :-)
+Other book notes of mine are:
+
+=> ./staff-engineer.gmi 2024-10-24 "Staff Engineer" book notes (You are currently reading this)
+=> ./the-stoic-challenge.gmi 2024-07-07 "The Stoic Challenge" book notes
+=> ./slow-productivity.gmi 2024-05-01 "Slow Productivity" book notes
+=> ./mind-management.gmi 2023-11-11 "Mind Management" book notes
+=> ./career-guide-and-soft-skills.gmi 2023-07-17 "Software Developmers Career Guide and Soft Skills" book notes
+=> ./the-obstacle-is-the-way.gmi 2023-05-06 "The Obstacle is the Way" book notes
+=> ./never-split-the-difference.gmi 2023-04-01 "Never split the difference" book notes
+=> ./the-pragmatic-programmer.gmi 2023-03-16 "The Pragmatic Programmer" book notes
+
=> ../ Back to the main site
+