Stories Flashcards — Patterns from 14 Staff Engineers
flashcards selt stories career
Why did Larson build staffeng.com and include the 14 stories in the book?
?
To fill a gap: the engineering management track had been extensively documented, but there was almost no first-person literature about operating as a Staff-plus IC. The stories provide concrete evidence that the book’s frameworks (archetypes, promotion mechanics, operating principles) are not theoretical — they are distilled from real careers.
What is the most striking structural pattern across the 14 stories regarding paths to the Staff title?
?
No single path exists. Engineers reached Staff through: long internal tenure followed by promotion (Ras Kasa Williams), deliberate company-switching with title upgrades (Keavy McMinn), retroactive recognition when a company created the title (Williams again), and direct hire into senior IC roles (McMinn). Strategy depends on the company and context, not a universal formula.
What does Michelle Bu’s story at Stripe illustrate about the post-promotion experience?
?
The title transition is an identity shift, not just a role expansion. The work that earned the title — deep individual execution, reliable delivery — stops being sufficient. Scope expands, ambiguity increases, and the familiar validation loops (sprint completions, feature launches) become less frequent. Engineers who expect the title to feel like a reward are often surprised by the disorientation.
What does Ras Kasa Williams’ story at Mailchimp illustrate about tenure and institutional knowledge?
?
Long tenure is a compounding advantage. Williams was effectively doing Staff-level work before the title existed at Mailchimp. The institutional knowledge, trust networks, and systems-level mental models built over years at one company are genuinely hard to replicate through external hiring or rapid promotion. Tenure gives a form of organizational context that newcomers cannot shortcut.
What is distinctive about Keavy McMinn’s path to Senior Principal Engineer at Fastly?
?
She built her career by moving companies deliberately — each move brought both a title upgrade and a new technical domain. She was repeatedly hired directly into senior IC roles, which requires demonstrating not just technical capability but organizational judgment in the interview: interviewers want to know whether you can operate without the institutional context a long-tenured employee would have.
What does Katie Sylor-Miller’s story at Etsy demonstrate about “glue work” and Staff promotions?
?
“Glue work” — coordination, documentation, standard-setting, knowledge transfer — is often invisible in promotion conversations because it produces no obvious technical artifact. Sylor-Miller’s promotion packet was the forcing function that made years of web performance work legible as Staff-level impact. The implication: impact that cannot be articulated is impact that the promotion process cannot evaluate.
What does Ritu Vincent’s story at Dropbox illustrate about post-promotion career design?
?
After reaching Staff, Vincent was deliberately intentional about what kind of Staff work she wanted — deep technical execution in a focused domain rather than broad organizational coordination. Many Staff engineers drift toward whatever the organization needs without asking what they want from the role. Her story is an argument for explicitly negotiating the shape of the role with your manager.
What is the Right Hand archetype and what does Rick Boone’s story at Uber reveal about its personal cost?
?
The Right Hand is a Staff engineer who extends an executive’s attention and authority — filling organizational gaps, accelerating decisions, coordinating across teams on behalf of a VP or CTO. The personal cost: constant context-switching, rarely finishing anything you start, and deriving satisfaction from organizational outcomes rather than technical deliverables. Engineers who find meaning in deep technical execution often find this role draining.
What does Nelson Elhage’s story contribute that is unique among the 14 narratives?
?
His story is told from the perspective of having voluntarily left a Staff role, giving him distance to reflect on what the role actually required. His key insight: security is an organizational architecture problem, not primarily a technical one. Security debt accumulates silently and the organizational incentive to address it is weaker than the incentive to ship features — making it a classic case of unglamorous, high-leverage Staff work.
What challenge does Diana Pojar’s story at Slack highlight about data engineering as a Staff domain?
?
Data engineering work — modeling, platform standards, pipeline reliability — produces diffuse impact rather than feature-level deliverables. This creates two challenges: (1) it is harder to document and advocate for in promotion conversations, and (2) asserting Staff-level influence requires translating data infrastructure decisions into the product-level language that engineering leadership uses to evaluate impact.
What does Dan Na’s story at Squarespace challenge in the standard Staff engineering framework?
?
He challenges the assumption that managing people and Staff IC work are in conflict. At Squarespace, he combined both effectively: the small people-management scope (one team) gave him direct organizational context that made his technical leadership more effective. The Tech Lead archetype often exists in this hybrid form at mid-sized companies where the engineering management and IC tracks have not fully separated.
What does Joy Ebertz’s story at Split illustrate about Staff engineering at smaller, less-structured companies?
?
She had to create the Staff role’s definition from scratch — no established Staff engineers to emulate, no charter, no standard expectations. The freedom was real, but so was the absence of feedback loops. Her story shows both the opportunity (more latitude to shape engineering culture) and the challenge (building your own evaluation framework for “doing the job well”). The leverage asymmetry favors Staff engineers at small companies when it comes to cultural influence.
What is Damian Schenkelman’s strategy at Auth0, and what mechanism made it effective?
?
Schenkelman built his Principal career through technical writing and external visibility — blog posts and conference talks that built a reputation outside Auth0, which fed back as organizational credibility inside Auth0. The mechanism: engineers who read his posts joined Auth0 already familiar with his thinking; leadership saw external validation of his technical judgment. His path involved no single Staff project — it was an accumulation of writing, proposals, and technical leadership.
What does Dmitry Petrashko’s story at Stripe illustrate about deep technical expertise as a Staff-level strategy?
?
His rare expertise in compilers, type systems, and formal reasoning became an organizational asset directly applicable to infrastructure problems. His story is a case for staying deeply technical at senior levels rather than broadening into organizational generalism — the value of his role depended entirely on the depth remaining real. It also required translating between deep technical knowledge and the organizational language of infrastructure investment.
What is distinctive about Staff engineering at Samsara, as illustrated by Stephen Wan’s story?
?
Samsara is a hardware-software IoT company, making Wan’s story the most distinct from pure software contexts. Staff engineering there requires deep domain knowledge about physical systems (firmware, hardware constraints, real-time embedded data) that creates a natural expertise moat. The lesson: the Staff engineer’s domain is defined by where the company creates value, which in hardware-adjacent companies is often at the boundary between software and physical systems.
What does the equity and access theme across multiple stories reveal about the Staff promotion system?
?
The promotion system — which relies heavily on informal advocacy and visibility — amplifies existing organizational advantages. Engineers from underrepresented groups often need to be more deliberate about documenting impact, more proactive about sponsor cultivation, and more explicit about self-advocacy than peers with equivalent output. The same quality of work does not reliably produce the same organizational recognition across different demographic groups.
What is the consistent mechanism by which Staff engineers in the stories exercise influence without formal authority?
?
They develop deep expertise and broad organizational context until people voluntarily seek their input — then use that position to shape outcomes through written artifacts, persistent communication, and cross-team coordination. The pattern across all 14 stories: influence is earned through credibility and sustained engagement with important problems, not delegated through org charts.
How does the Staff role differ across Stripe, Mailchimp, and Uber based on the stories?
?
- Stripe: Dense, structured engineering culture; high technical rigor; Staff work involves written communication, architectural influence, and organizational navigation at scale.
- Mailchimp: Less formalized; the Staff title brought recognition more than it changed the work; the role looked more like being the most experienced, trusted engineer on a team.
- Uber (Infrastructure VP level): The Right Hand role is defined by executive priorities, not a fixed technical domain; operates at organizational speed, not technical-project speed.
The same title contains very different work depending on company culture, size, and maturity.
What is the “sponsor as door-opener” pattern and which story illustrates it most clearly?
?
The pattern: a sponsor does not just advocate for a candidate during a promotion review — they actively create opportunities for the candidate to demonstrate Staff-level impact before the promotion happens. Ritu Vincent’s story at Dropbox is the clearest example: her sponsor gave her access to high-visibility projects specifically to build the evidence base the promotion required. The candidate’s job is to execute; the sponsor’s job is to open the right doors first.
What does the collective evidence of the stories say about the relationship between technical merit and Staff promotion?
?
Technical merit is necessary but not sufficient. Across the 14 stories, engineers describe cases where excellent technical work was not enough without a sponsor who advocated with their own credibility, visibility that brought the work to the attention of decision-makers, and a written articulation of impact that the promotion process could evaluate. Merit creates the ceiling of what is possible; the other factors determine whether that ceiling is reached.
What pattern does Larson’s stories section reveal about “Staff projects” as the path to Staff?
?
The single-defining-Staff-project model is not universal. Some engineers (like Schenkelman at Auth0) reached Principal through sustained accumulation — years of writing, proposals, and technical leadership — without a single project that served as proof. Others had a Staff project that was decisive. The stories suggest that the “accumulation path” is more common than the framework chapters imply, and that companies with more mature engineering cultures tend to favor the accumulation model.
What does the stories section collectively suggest about the value of writing technical content externally (blogs, talks)?
?
External writing compounds internal influence through multiple mechanisms: engineers hired later already have context on your thinking; outside references validate your judgment to internal leadership; your ideas circulate beyond what internal documents can reach. Schenkelman’s story is the most explicit, but the pattern of written artifacts driving organizational influence appears across multiple stories. External visibility is not vanity — it is a legitimate Staff-level leverage multiplier.
Summarize what the 14 stories section adds to the book’s frameworks that the earlier chapters cannot provide.
?
The stories provide empirical grounding for the frameworks. They show that: (1) the archetypes are real and recognizable in practice, (2) the promotion mechanics play out differently in different organizational contexts, (3) there are paths not fully captured by the framework (accumulation vs. Staff project, hybrid IC/manager roles, retroactive recognition), and (4) the human variables — identity, equity, personal motivation, company culture — matter as much as the structural mechanics. The stories are the evidence base; the frameworks are the distillation.
Total Cards: 23
Review Time: ~16 minutes
Priority: MEDIUM
Last Updated: 2026-05-30