library / lib7dfc5940bad6b01a
Staff Engineer: Leadership Beyond the Management Track
Will Larson · 2021
In a sentence
A practical field guide to reaching and thriving in Staff-plus engineering roles—technical leadership positions that exist beyond the management track.
Staff Engineer demystifies the most ambiguous and under-documented career path in software engineering: the senior individual contributor track of Staff, Principal, and Distinguished engineers. Combining Will Larson's experience hiring, promoting, and supporting senior engineers with more than a dozen candid interviews from practitioners across companies like Stripe, Slack, Dropbox, Uber, and Etsy, the book maps four common Staff archetypes (Tech Lead, Architect, Solver, Right Hand), explains what these engineers actually do day-to-day, and provides concrete tools for operating effectively, getting promoted at your current company, or switching companies to attain the title. It is at once a strategic playbook (promotion packets, finding sponsors, engineering strategy, technical quality) and a humane meditation on energizing work, leadership without authority, and creating space for others. Whether you are a senior engineer choosing your next step, a newly minted Staff engineer feeling lost, or a manager trying to set your most senior engineers up for success, this book offers a clear, candid map through previously uncharted territory.
The four lenses
- Science
- Statistics
- Systems
- Strategy
Tags
The model
A causal model linking design levers and conditions (sponsorship, alignment, visibility, work prioritization, strategy and quality practices) through psychological and behavioral states (energized engagement, organizational trust, creating space for others) to outcomes (Staff-plus advancement, organizational impact, career sustainability).
Sponsor Access and Activationdesign lever
The degree to which an engineer has secured and effectively activated an empowered organizational sponsor (typically their manager or management chain) who advocates for their work, recognition, and advancement using their own organizational capital.
Alignment with Organizational Authoritydesign lever
The extent to which an engineer remains deeply aligned with their sponsor's and leadership's worldview, priorities, and values—never surprising their manager and feeding context upward—thereby retaining loaned organizational authority needed to lead.
High-Impact Work Prioritizationbehavioral pattern
The behavioral discipline of focusing effort on work that genuinely matters—avoiding snacking, preening, and chasing ghosts—while pursuing existential issues, editing, finishing projects, fostering growth, and work only the engineer can uniquely accomplish.
Engineering Strategy and Technical Quality Practicesdesign lever
The set of leadership practices for writing engineering strategy and vision (from design docs upward) and for managing technical quality (hot spots, best practices, leverage points, vector alignment, measurement, quality teams and programs) to guide and improve an organization's technical direction.
Internal and External Visibilitydesign lever
The degree to which an engineer is known for good work across the organization (and optionally externally), through working on what matters, distributing long-lived documents, leading forums, executive exposure, and external presence, while minimizing the organizational attention consumed.
Network of Peerscontextual condition
A personal network of trusted peers, mentors, and former colleagues doing similar work, built deliberately for honest feedback, vetting difficult decisions, and combating the isolation that grows with seniority.
Company Fit and Opportunity Conditionscontextual condition
Contextual conditions of the company—growth rate, archetype availability, durability, whether it disproportionately values the engineer's strengths, and whether it is meritocrat- or proceduralist-leaning—that determine the availability of and friction toward Staff-plus roles.
Energized Engagementpsychological state
The inward-looking psychological state of being energized and intrinsically motivated by one's work, which sustains effort across the longer, slower feedback loops of Staff-plus roles and prevents burnout or disengagement.
Organizational Trust and Credibilitypsychological state
The reservoir of trust, respect, and credibility an engineer holds across the organization—earned through consistent good judgment, alignment, low friction, and delivery—which enables them to be granted ambitious work and to influence decisions.
Creating Space for Othersbehavioral pattern
The behavioral pattern of deliberately involving others in discussions and decisions and ultimately sponsoring them for the work that earned the engineer their role, shifting from being essential to being adjacent so the team grows stronger than the individual's contribution.
Influence Without Frictionbehavioral pattern
The behavioral and communicative capacity to advance one's vision while blending with others' visions—listening through questions, reading the room, being right without dominating, and following when appropriate—so collaboration replaces conflict.
Staff-plus Advancementoutcome metric
The outcome of attaining and retaining a Staff-plus title and role, whether through promotion at the current company or by switching companies, reflecting organizational recognition of the engineer's leadership-level impact.
Organizational Impactoutcome metric
The outcome of meaningful, durable improvement to the company's technology, teams, and outcomes—measured by progress of the teams the engineer supports, alignment of work to company goals, and lasting architectural or cultural change rather than personal heroics.
Career Sustainabilityoutcome metric
The outcome of pacing one's career to one's life such that impact and personal growth are maintained over a decades-long career without burnout, achieved by working on energizing, high-impact work and remaining a long-term effective leader.
How they connect
- sponsorship access → predicts staff plus advancement
- alignment with authority → predicts organizational trust
- organizational trust → mediates organizational impact
- alignment with authority → predicts organizational impact
- work prioritization discipline → predicts organizational impact
- strategy and quality practices → predicts organizational impact
- internal visibility → predicts staff plus advancement
- work prioritization discipline → influences internal visibility
- energized engagement → predicts career sustainability
- work prioritization discipline → influences energized engagement
- creating space for others → predicts organizational impact
- creating space for others → predicts career sustainability
- influence without friction → predicts organizational trust
- peer network → influences influence without friction
- company fit conditions → moderates staff plus advancement
- staff plus advancement → influences organizational impact
The process
This playbook outlines the operational journey of a Staff-plus engineer, transitioning from individual contributor excellence to broad organizational influence. The process begins with mastering personal effectiveness—prioritizing high-impact work, managing time, and building foundational relationships with managers and peers. With this base, the engineer expands their scope by developing deep situational awareness of business and user needs, which informs the creation and execution of a cohesive technical strategy. This strategy is not developed in a vacuum; it requires significant advocacy, strategic communication, and the ability to influence change across teams and up to the executive level. The playbook emphasizes that a Staff-plus engineer's impact is scaled through others. Key processes focus on mentoring and sponsoring fellow engineers, fostering an inclusive engineering culture, and driving large-scale technical quality initiatives. This people-centric approach is crucial for building a resilient and high-performing organization. Finally, the playbook addresses career management, providing structured guidance on navigating promotions, evaluating new opportunities, and interviewing effectively. It also includes meta-processes for those who shape the organization itself, such as designing interview loops, managing other Staff-plus engineers, and optimizing organizational structures. The overall narrative is one of intentional, multi-faceted growth from a technical expert to a strategic leader.
Managing Personal Focus and Productivity
To structure the work week to protect time for deep, focused work while ensuring availability for collaborative meetings.
When to use: On a weekly basis to plan and structure time effectively, especially when feeling overwhelmed by meetings and distractions.
Step 1Categorize meetings into recurrent (e.g., 1:1s) and non-recurrent (e.g., project reviews).
Entry: A need to regain control over a chaotic calendar.
Exit: All known meetings are categorized.
In: Calendar invites, Meeting objectives · Out: Categorized list of meetings
ch19
Step 2Designate specific days for meetings and block out other days for focused, uninterrupted work.
Entry: Meetings are categorized.
Exit: Calendar is structured with designated meeting and focus days.
- Which days are best for meetings vs. focus?
In: Team availability, Personal work rhythm preferences · Out: A structured weekly calendar
ch19 · ch21
Step 3Maintain a simple, running document of weekly tasks.
Entry: A need for a lightweight task tracking system.
Exit: Task document is created and in use.
In: Project goals, Action items from meetings · Out: A living document of current tasks
ch21
Step 4At the start of each week, review the task document and delete uncompleted or irrelevant items from the previous week.
Entry: A new week is beginning.
Exit: The task list is pruned and reflects the current week's priorities.
- Is this old task still relevant?
In: Previous week's task list · Out: A clean, prioritized task list for the week
ch21
Identifying and Prioritizing High-Impact Work
To focus finite time and energy on tasks that deliver the greatest organizational value and address existential risks, while avoiding low-impact work.
When to use: When planning work for a quarter or project, or when feeling that current work is not impactful.
Step 1Evaluate potential work tasks based on their impact versus the effort required.
Entry: A list of potential tasks or projects.
Exit: Tasks are categorized by impact and effort.
In: Organizational goals, List of potential projects · Out: An impact/effort matrix of tasks
ch05p01
Step 2Avoid common low-impact work traps: 'snacking', 'preening', and 'chasing ghosts'.
Entry: Awareness of personal work habits.
Exit: Low-impact tasks are de-prioritized or eliminated.
In: Self-reflection on work patterns · Out: A refined list of potential tasks
ch05p01
Step 3Identify and prioritize work that addresses existential risks to the organization.
Entry: Understanding of the business's strategic vulnerabilities.
Exit: Work addressing existential risks is at the top of the priority list.
In: Business strategy documents, Discussions with leadership · Out: Prioritized list of strategic initiatives
ch05p01
Step 4Dedicate time to high-leverage activities like mentoring and supporting colleagues.
Entry: A prioritized list of technical tasks.
Exit: Time for mentoring is explicitly scheduled.
In: Team skill assessment · Out: A balanced work plan including team enablement
ch05p01
Developing a Strategic Relationship with Your Manager
To build a foundation of trust and open communication with your manager to align on career goals, receive support for impactful work, and facilitate growth.
When to use: Continuously throughout your employment, with specific focus during 1:1 meetings and project planning.
Step 1Build a track record of successfully delivering on assigned projects.
Entry: Assignment of a project or responsibility.
Exit: Project is successfully completed and delivered.
In: Project requirements · Out: Completed project, Demonstrated reliability
ch11
Step 2Establish regular 1:1 meetings with your manager.
Entry: A direct reporting relationship.
Exit: A recurring 1:1 meeting is on the calendar.
Out: Scheduled 1:1 meetings
ch13
Step 3Be honest and direct about your career aspirations and challenges.
Entry: A trusting relationship is being developed.
Exit: Manager understands your career goals and current challenges.
In: Personal career goals, Project status and blockers · Out: Shared understanding of career path, Managerial support for challenges
ch11 · ch13
Step 4Seek feedback and guidance on your career path and performance.
Entry: Regular 1:1s are established.
Exit: Actionable feedback is received and understood.
In: Specific questions about performance and growth · Out: Constructive feedback, A clearer development plan
ch13
Building Situational Awareness and Understanding User Needs
To maintain a comprehensive understanding of organizational projects, technical challenges, and internal customer needs to make well-informed strategic decisions.
When to use: Continuously, as an ongoing part of the role to stay informed and identify opportunities for impact.
Step 1Engage with internal customers and users informally.
Entry: Access to internal employees from different teams.
Exit: Gained direct insights into user pain points and needs.
In: Targeted questions about productivity and challenges · Out: A list of user needs and potential improvement areas
ch20
Step 2Review internal documents and communications from other teams.
Entry: Access to internal documentation and communication platforms.
Exit: Broader understanding of ongoing work and technical direction across the company.
- Which documents and meetings are most relevant to prioritize?
In: Internal wikis, Code repositories, Meeting invitations · Out: Enhanced awareness of company-wide initiatives
ch09
Step 3Attend relevant internal meetings and presentations.
Entry: Awareness of key recurring meetings.
Exit: Stayed current on cross-functional initiatives.
In: Meeting agendas · Out: Notes on cross-functional updates, Opportunities for collaboration
ch09
Step 4Synthesize gathered information to inform technical strategy and project planning.
Entry: Information has been gathered from multiple sources.
Exit: Strategic decisions are informed by broad situational awareness.
In: User feedback, Internal documentation · Out: Better-informed technical strategy, More impactful project proposals
ch09 · ch20
Building a Professional Network and Influence
To foster a diverse network of professional relationships that provides support, feedback, and collaboration opportunities, enabling influence without direct authority.
When to use: Continuously throughout one's career to build social capital and a support system.
Step 1Be visible and contribute to relevant discussions.
Entry: A desire to increase professional visibility.
Exit: Active participation in relevant communities.
In: Knowledge and opinions on relevant topics · Out: Increased visibility, Recognition as a subject matter expert
ch05p01 · ch12
Step 2Schedule regular one-on-one meetings with peers across different teams.
Entry: Identified key individuals in other teams.
Exit: A cadence of regular 1:1s is established with key peers.
- Which colleagues are most strategic to connect with?
In: Organizational chart, Project dependency maps · Out: Strengthened cross-team relationships, Enhanced understanding of the engineering landscape
ch11 · ch12
Step 3Create or join communities of practice.
Entry: A need for broader connection or knowledge sharing.
Exit: An active community forum is established or joined.
In: A platform like Slack, Interested participants · Out: Increased connections among peers, A space for knowledge sharing
ch17
Step 4Engage with the external community.
Entry: A desire to learn from and connect with peers outside the organization.
Exit: Active participation in external professional communities.
Out: A broader professional network, Access to external perspectives and knowledge
ch05p01 · ch23
Step 5Maintain relationships by periodically reaching out for advice and sharing insights.
Entry: An initial connection has been made.
Exit: The relationship is maintained over time.
Out: A durable and supportive professional network
ch05p01
Defining and Executing a Technical Strategy
To create and communicate a clear technical vision and strategy that aligns engineering efforts with business goals, guides decision-making, and empowers teams.
When to use: When there is ambiguity in technical direction, a need to align multiple teams, or a desire to proactively guide technological evolution.
Step 1Assess the current state by writing or reviewing multiple design documents.
Entry: A need for a new or updated technical strategy.
Exit: Common themes and strategic insights are extracted from existing designs.
In: Existing design documents, Project proposals · Out: A summary of common technical themes and challenges
ch05p01 · ch10
Step 2Draft the technical strategy document.
Entry: Foundational insights have been gathered.
Exit: A draft strategy document is created.
- What are the core principles that will guide our technical decisions?
In: Business goals, Technical assessment findings · Out: Draft technical strategy document
ch05p01 · ch19 · ch22
Step 3Share the draft strategy and gather feedback from stakeholders.
Entry: A draft document is ready for review.
Exit: Feedback from key stakeholders has been collected.
In: Draft strategy document · Out: Stakeholder feedback
ch05p01 · ch19
Step 4Revise and finalize the strategy.
Entry: Feedback has been collected.
Exit: A finalized strategy document is published and communicated.
In: Stakeholder feedback · Out: Finalized technical strategy, A decision log for key choices
ch05p01 · ch19
Step 5Execute the strategy through incremental improvements and mentorship.
Entry: Strategy is finalized and communicated.
Exit: Teams are making decisions consistent with the technical strategy.
In: Finalized technical strategy · Out: Code and architecture aligned with strategy, Empowered team members
ch09 · ch18
Step 6Continuously communicate and adapt the strategy.
Entry: Strategy is being executed.
Exit: The strategy remains relevant and understood over time.
- When should the strategy be revisited or updated?
In: Feedback from internal customers, Changing business priorities · Out: An evolving, living technical strategy
ch09
Structuring Project Proposals
To create clear, well-defined project proposals that align with user needs and business objectives, facilitating stakeholder buy-in and effective execution.
When to use: At the beginning of a new project or initiative to ensure clarity and alignment.
Step 1Identify the project's intent and the user needs it addresses.
Entry: A new project idea has emerged.
Exit: The core problem and user needs are clearly articulated.
In: Project idea, User feedback, Team insights · Out: A clear problem statement
ch20
Step 2Draft a structured plan or proposal document.
Entry: Problem statement is defined.
Exit: A draft proposal document is created.
In: Problem statement · Out: Draft project proposal
ch20
Step 3Socialize the proposal with relevant stakeholders for feedback.
Entry: Draft proposal is ready for review.
Exit: Feedback from stakeholders has been collected.
In: Draft project proposal · Out: Stakeholder feedback
ch20
Step 4Refine the proposal based on feedback.
Entry: Feedback has been collected.
Exit: The proposal is updated to reflect feedback.
- Should the project scope be changed based on feedback?
In: Stakeholder feedback · Out: A refined project proposal
ch20
Step 5Submit the final proposal for approval.
Entry: Proposal has been refined and socialized.
Exit: Project is approved and ready for execution.
In: Final project proposal · Out: Project approval, Resource allocation
ch20
Driving Technical Quality and Improvement Initiatives
To systematically identify, prioritize, and address issues in technical quality, performance, and architecture, leading to a more robust and maintainable system.
When to use: When technical debt is high, performance is degrading, incident rates are increasing, or a strategic investment in quality is needed.
Step 1Identify and measure quality hotspots and performance issues.
Entry: A recognized need to improve technical quality.
Exit: Key problem areas are identified and measured.
In: Performance metrics, Incident reports, Team feedback · Out: A prioritized list of quality hotspots
ch05p01 · ch12
Step 2Develop a strategic plan or initiative to address the identified issues.
Entry: Problem areas are identified.
Exit: A strategic plan for the improvement initiative is documented.
- What is the scope of the initiative?
- Which teams need to be involved?
In: List of quality hotspots, Organizational priorities · Out: A project plan for the quality initiative
ch15
Step 3Implement best practices and provide tools to improve quality.
Entry: A plan is in place.
Exit: New best practices and tools are adopted by teams.
In: Industry best practices, Tooling budget and resources · Out: Improved development practices, Higher quality code
ch05p01 · ch15
Step 4Monitor the effects of changes and iterate.
Entry: Changes have been implemented.
Exit: The impact of the changes is measured and understood.
In: Performance metrics, Quality metrics · Out: Data on the effectiveness of the initiative, Adjusted improvement plan
ch05p01 · ch12 · ch16
Step 5Establish a long-term quality program.
Entry: Initial quality initiatives have shown success.
Exit: A sustainable, ongoing quality program is established.
Out: A culture of quality, Sustained high technical standards
ch05p01 · ch16
Strategic Communication and Alignment
To effectively communicate complex technical information to different audiences, especially leadership, to build consensus, resolve misalignment, and ensure strategic alignment.
When to use: When preparing for a high-stakes meeting with executives, trying to resolve cross-team disconnects, or aligning engineering work with leadership's vision.
Step 1Identify the purpose of the communication.
Entry: A need to communicate with leadership or another team.
Exit: The primary goal of the communication is defined.
- What is the single most important outcome I want from this interaction?
In: Meeting invitation, Context of the issue · Out: A clear communication objective
ch05p02
Step 2Structure the information using a clear framework like SCQA.
Entry: Communication objective is clear.
Exit: A structured document is drafted.
In: Relevant data and context · Out: A draft document using the SCQA framework
ch05p02
Step 3Gather feedback on the structured document from peers.
Entry: A draft document is complete.
Exit: The document has been improved based on peer feedback.
In: Draft document · Out: A revised, clearer communication document
ch05p02
Step 4Act as a proxy for leadership to maintain alignment.
Entry: A clear understanding of leadership's vision is established.
Exit: Engineering teams are aligned with the strategic vision.
In: VP's strategic vision · Out: Aligned engineering teams
ch14
Step 5Facilitate communication between disconnected teams.
Entry: A communication breakdown between teams is identified.
Exit: A plan to improve inter-team communication is in place.
In: Perspectives from involved teams · Out: Improved collaboration between teams
ch14
Advocating for Technical Change and Initiatives
To successfully propose, build consensus for, and drive the adoption of significant technical changes, impactful projects, or new practices like SLOs.
When to use: When a necessary technical change, new project, or process improvement requires buy-in from multiple stakeholders or teams.
Step 1Identify an opportunity for an impactful project or improvement.
Entry: Deep understanding of a technical system or business need.
Exit: A clear proposal for a change or project is formulated.
In: System architecture knowledge, User feedback, Business goals · Out: A well-defined project or change proposal
ch11 · ch18
Step 2Conduct research and analyze trade-offs.
Entry: A proposal has been formulated.
Exit: A data-backed analysis of options is complete.
In: Technical data, Performance metrics · Out: A document analyzing trade-offs and providing a recommendation
ch10
Step 3Engage stakeholders informally to build consensus (Nemawashi).
Entry: A data-backed recommendation is ready.
Exit: Informal consensus has been built with key stakeholders.
- Which stakeholders are critical for success?
In: Stakeholder map, Initial proposal · Out: Refined proposal, Stakeholder buy-in
ch19
Step 4Present the final recommendation for formal approval.
Entry: Consensus has been built.
Exit: The change or project is formally approved.
In: Final proposal document · Out: Official approval for the initiative
ch10
Step 5Drive adoption through pilots and iterative rollout.
Entry: Initiative is approved.
Exit: The new practice or change is successfully adopted by target teams.
In: Documentation, Training materials · Out: Widespread adoption of the change
ch21
Mentoring and Sponsoring Engineers
To scale impact by enhancing the skills, confidence, and visibility of other engineers, fostering their growth and creating a stronger, more capable team.
When to use: As an ongoing activity to develop talent within the organization, especially when onboarding new members or helping engineers prepare for their next level.
Step 1Identify individual learning needs and professional goals of team members.
Entry: A commitment to mentor other engineers.
Exit: A clear understanding of the mentee's development needs.
In: Team members' career goals, Performance feedback · Out: A personalized development plan for the mentee
ch09 · ch14
Step 2Provide guidance on technical decision-making and project management.
Entry: A mentoring relationship is established.
Exit: Mentee demonstrates improved technical judgment and project management skills.
In: Technical challenges, Project plans · Out: Increased mentee confidence and independence
ch09
Step 3Scope and kick-off projects, then transition ownership.
Entry: An engineer is ready for a new challenge.
Exit: The engineer successfully takes ownership of the new project.
- When is the right time to hand over ownership?
In: Project ideas, Mentee skill assessment · Out: An empowered engineer leading a new project
ch20 · ch21
Step 4Actively sponsor less senior engineers by creating visibility for their work.
Entry: A junior engineer has done excellent work.
Exit: The engineer's work and talent are more widely recognized in the organization.
In: Opportunities for presentations, Internal communication channels · Out: Enhanced visibility and recognition for the sponsored engineer
ch16 · ch17 · ch22
Fostering Engineering Community and Inclusive Culture
To build a supportive, inclusive, and collaborative engineering culture by creating spaces for connection, sharing diverse perspectives, and addressing common challenges.
When to use: When teams feel isolated, when there's a need for more knowledge sharing, or as a proactive measure to build a strong and healthy engineering culture.
Step 1Create forums for engineering leaders to connect and share challenges.
Entry: A group of interested engineering leaders.
Exit: A recurring meeting for leaders is established.
In: Interested participants, Reading materials · Out: A collaborative space for knowledge sharing
ch17
Step 2Facilitate open discussions about the challenges and fears of senior roles.
Entry: A safe and trusting environment.
Exit: Common fears are identified and discussed openly.
In: Willingness from colleagues to be vulnerable · Out: A more open and supportive team culture
ch22
Step 3Incorporate diverse voices and experiences into professional narratives.
Entry: Recognition that your own perspective is limited.
Exit: A more inclusive narrative is created and shared.
- Which perspectives are currently missing?
In: Connections with industry practitioners · Out: A more inclusive book, blog post, or presentation
ch08
Navigating the Promotion Process for Staff-Plus Roles
To strategically prepare for and achieve a promotion to a Staff-plus role by documenting impact, building support, and aligning with organizational expectations.
When to use: Over a 6-18 month period leading up to a promotion cycle.
Step 1Draft an initial version of your promotion packet well in advance.
Entry: A goal to be promoted to a Staff-plus role.
Exit: An initial draft of the promotion packet exists.
In: Records of accomplishments, Engineering rubric for the next level · Out: Draft promotion packet, A list of identified gaps in experience or impact
ch06 · ch18
Step 2Share the draft packet with trusted peers and your manager for feedback.
Entry: A draft packet is ready for review.
Exit: Feedback has been incorporated into the packet.
In: Draft promotion packet · Out: A refined promotion packet
ch06 · ch12 · ch16
Step 3Identify and activate sponsors within the organization.
Entry: A clear goal for promotion.
Exit: Sponsors are aware of your goals and are advocating for you.
- Who are the most effective potential sponsors?
In: An understanding of organizational influence · Out: Advocate support for promotion
ch06
Step 4Gain access to key decision-making rooms.
Entry: Sponsorship has been established.
Exit: Increased visibility and participation in key meetings.
In: Sponsor advocacy · Out: Enhanced visibility with leadership
ch06
Step 5Submit the finalized promotion package for formal review.
Entry: The promotion packet is complete and has been reviewed.
Exit: The packet is submitted to the promotion committee.
In: Finalized promotion packet, Manager's recommendation · Out: A submitted promotion case
ch16 · ch18
Evaluating Career Transitions and Opportunities
To systematically evaluate whether to stay at a current company, pursue an internal transfer, or seek an external job opportunity, based on personal satisfaction, growth potential, and practical considerations.
When to use: When feeling burnt out, stagnant, or dissatisfied in a current role, or when presented with a new opportunity.
Step 1Conduct a personal inventory of motivations and job satisfaction.
Entry: A feeling of dissatisfaction or a desire for change.
Exit: Clarity on personal drivers and sources of dissatisfaction.
In: Self-reflection · Out: A list of personal career motivations and values
ch07 · ch11
Step 2Analyze internal opportunities for growth.
Entry: Clarity on personal motivations.
Exit: A clear understanding of viable internal options.
In: Internal job postings, Conversations with other managers · Out: A list of potential internal roles
ch07
Step 3Consider alternatives to leaving, such as a sabbatical.
Entry: Burnout has been identified as a key factor.
Exit: Alternatives to leaving have been explored.
In: Company leave policies · Out: A decision on whether to pursue a sabbatical
ch07
Step 4Create a checklist for leaving the company.
Entry: Leaving the company is being seriously considered.
Exit: A clear understanding of the feasibility and risks of leaving.
- Is it feasible to leave without another job lined up?
In: Financial statements, Visa status, Job market analysis · Out: A personal readiness assessment for leaving
ch07
Step 5Make a decision based on the comprehensive evaluation.
Entry: All factors have been assessed.
Exit: A clear decision on the next career step is made.
In: All gathered information · Out: A career action plan
ch07
Navigating the Staff-Plus Interview Process (Candidate)
To effectively prepare for and navigate the interview process for Staff-plus engineering roles, assessing company fit while demonstrating the required skills.
When to use: When actively interviewing for a new Staff-plus role.
Step 1Clarify your criteria for companies you are willing to consider.
Entry: A decision to seek a new role has been made.
Exit: A clear set of criteria for evaluating companies.
In: Personal values, Career goals · Out: A target company profile
ch07
Step 2Seek details of the interview structure from the recruiting team.
Entry: An interview has been scheduled.
Exit: A clear understanding of the interview loop structure.
In: Communication from recruiter · Out: A list of interview formats and topics
ch07
Step 3Prepare for the specific formats required.
Entry: The interview structure is known.
Exit: Preparation for each interview stage is complete.
In: Job description, Interviewer profiles · Out: Prepared answers and stories, A list of questions to ask
ch07
Step 4Observe signals about the company's understanding of the Staff-plus role.
Entry: The interview process is underway.
Exit: An assessment of the company's Staff-plus maturity level.
- Does this company truly understand and support the Staff-plus role?
In: Interview questions, Interviewer seniority · Out: An evaluation of company fit
ch07
Step 5Politely raise concerns about the process design if it seems misaligned.
Entry: A misalignment in the interview process is identified.
Exit: Feedback has been provided to the company.
- Is it worth continuing the process if it is poorly designed?
In: Observations about the interview process · Out: Feedback to the recruiter
ch07
Designing a Staff-Plus Interview Process (Hiring Manager)
To create an effective and accurate interview process for evaluating Staff-plus candidates, focusing on the key signals of success beyond standard technical skills.
When to use: When opening a new Staff-plus requisition or when the existing interview process is proving ineffective at identifying successful candidates.
Step 1Define the key signals of a successful Staff-plus engineer.
Entry: A need to hire a Staff-plus engineer.
Exit: A clear list of the core competencies to be evaluated.
- What are the most critical signals for this specific role?
In: Job description, Analysis of successful current Staff-plus engineers · Out: A list of key evaluation signals
ch26
Step 2Choose interview formats that effectively test for these signals.
Entry: Key signals are defined.
Exit: A set of interview formats is chosen for the loop.
- Which format is best for evaluating each key signal?
In: List of key signals · Out: A structured interview loop with specific formats
ch26
Step 3Train the interview panel.
Entry: Interview loop is designed.
Exit: Interviewers are trained and aligned.
In: Interview loop design · Out: A well-prepared interview panel
ch26
Step 4Collect feedback from candidates and the panel on the process.
Entry: Interviews have been conducted.
Exit: Feedback on the process is collected.
In: Candidate surveys, Interviewer debriefs · Out: Process feedback
ch26
Step 5Continuously refine the interview loop.
Entry: Feedback has been collected.
Exit: The interview process is improved for the next candidate.
In: Process feedback, Hiring data · Out: An improved interview loop
ch26
Managing Staff-plus Engineers
To effectively manage and empower Staff-plus engineers by providing sponsorship, context, and autonomy rather than direct task management.
When to use: As an ongoing management philosophy for supporting senior technical leaders.
Step 1Sponsor and support rather than direct.
Entry: You are managing a Staff-plus engineer.
Exit: The engineer feels supported and empowered.
Out: An autonomous, high-impact engineer
ch25
Step 2Establish a reproducible process for sharing information and context.
Entry: A need to keep the engineer aligned with company strategy.
Exit: A reliable information-sharing cadence is established.
In: Key team decisions, Strategic updates · Out: A well-informed Staff-plus engineer
ch25
Step 3Assign them unrefined, ambiguous problems.
Entry: A complex, strategic problem is identified.
Exit: The engineer takes ownership of the problem and begins to solve it.
In: High-level business or technical problems · Out: A solution or strategy for the ambiguous problem
ch25
Step 4Provide frequent, high-quality feedback.
Entry: Regular 1:1s are in place.
Exit: The engineer has a clear understanding of their performance and areas for growth.
In: Observations of their work and impact · Out: Actionable feedback
ch25
Step 5Cede ownership and create space for their leadership.
Entry: A desire to grow the engineer's leadership capabilities.
Exit: The engineer is leading significant initiatives with autonomy.
Out: A stronger technical leadership pipeline
ch25
Assessing and Adjusting Organizational Structures
To evaluate and optimize the reporting structures for Staff-plus engineers to ensure they are positioned for maximum impact and have appropriate managerial support.
When to use: During organizational planning cycles, when a Staff-plus engineer seems misaligned or ineffective, or when managerial bandwidth is strained.
Step 1Define and assess the current reporting structure for Staff-plus engineers.
Entry: A need to evaluate organizational effectiveness.
Exit: A clear map of the current reporting structure and its potential issues.
In: Current organizational charts, Role descriptions · Out: An assessment of the current reporting structure
ch24
Step 2Review managerial bandwidth to ensure leaders can effectively support their reports.
Entry: Reporting structure has been mapped.
Exit: An assessment of managerial capacity is complete.
In: Manager-to-report ratios, Feedback from managers · Out: Identification of overloaded managers
ch24
Step 3Develop a proposal for organizational adjustments.
Entry: Issues in the current structure have been identified.
Exit: A formal proposal for changes is drafted.
In: Assessment findings · Out: A proposal for organizational adjustments
ch24
Step 4Consult with management and implement changes.
Entry: A proposal is ready.
Exit: Approved changes are implemented.
- Are the proposed changes feasible and timely?
In: Proposal document · Out: An optimized reporting structure
ch24
Step 5Monitor and evaluate the effectiveness of the new structure.
Entry: Organizational changes have been implemented.
Exit: The new structure is validated as effective.
In: Feedback from engineers and managers · Out: A continuously improving organizational design
ch24
Launching and Operating an Internal Incubator
To foster innovation and explore new product ideas within a large organization by providing a structured, autonomous environment for experimentation.
When to use: When a company's core business is facing increased competition and there is a strategic need to explore new avenues for growth.
Step 1Establish the incubator's charter and obtain executive sponsorship.
Entry: A strategic need for innovation has been identified.
Exit: The incubator is formally chartered and funded.
In: Business strategy · Out: Incubator charter, Executive sponsorship
ch13
Step 2Create a process for engineers to submit ideas for funding.
Entry: Incubator is established.
Exit: A clear process for idea submission is in place.
Out: A pipeline of new ideas
ch13
Step 3Evaluate pitches and fund promising ideas.
Entry: Ideas have been submitted.
Exit: The first cohort of projects is funded.
- Which ideas have the most potential and should be funded?
In: Project pitches · Out: Funded projects
ch13
Step 4Monitor the progress of funded projects.
Entry: Projects are underway.
Exit: Project progress is assessed.
- Should this project receive more funding, pivot, or be shut down?
In: Project progress reports · Out: Decisions on project continuation
ch13
Step 5Graduate successful projects into their own lines of business.
Entry: A project has met its success criteria.
Exit: The project is successfully integrated into the broader organization.
In: Project performance data · Out: A new product or business line
ch13
The story
The reader A senior software engineer who wants to grow their career and impact without becoming a manager, aspiring to or newly holding a Staff-plus role.
External problem
There is no clear map for the technical leadership track—ambiguous role definitions, inconsistent titles, opaque promotion criteria, and no standard path beyond Senior engineer.
Internal problem
They feel directionless, isolated, and unsure whether they're working on the right things, often feeling demoralized by slow feedback loops or like an imposter in 'the wrong room.'
Philosophical problem
Talented technical leaders deserve resources, community, and recognition equal to the management track; it's wrong that the industry leaves them to navigate alone.
The plan
- Identify which Staff archetype fits the work that energizes you and is available at your company.
- Learn to operate at Staff: work on what matters, write strategy, manage technical quality, stay aligned with authority, and create space for others.
- Build a promotion packet as a living map, find and activate a sponsor, complete a meaningful project, and become visible internally.
- If your current company can't support the role, find a company that disproportionately values you and negotiate the title and offer.
- Build a network of peers to vet decisions and get honest feedback as your authority tempers feedback.
Success
- You operate as a trusted organizational leader with clear, energizing impact and proxied authority you retain through alignment.
- You grow the engineers around you, leaving a legacy beyond your own contributions.
- You free yourself from constantly re-proving your competence, reinvesting that energy into meaningful work.
- You find work that sustains you over a decades-long career rather than burning out.
At stake
- You spend a decade pursuing a Staff role only to discover you despise the work or feel unequipped for it.
- You stall in 'Staff purgatory,' recognized in title but kept away from real leadership opportunities.
- You burn bright and then lack the relationships and support to make forward progress.
- You optimize for visibility and your company's pathologies, leaving you stuck and undeveloped.
Chapter by chapter
ch01Acknowledgments
In this chapter, the author expresses gratitude to the individuals and communities who contributed to the creation of the book, highlighting the collaborative efforts that shaped its content.
ch02Foreword
In this foreword, Tanya Reilly articulates the often-overlooked challenges faced by engineers pursuing technical leadership roles, emphasizing the need for clear guidance and community resources in navigating these complex career pathways.
ch03Preface
The preface discusses the author's personal journey in writing and the motivations behind choosing the complex topic of Staff engineering roles, emphasizing the challenges many face in this critical phase of their careers.
- The pursuit of a Staff Engineer role can lead to unexpected confusion and dissatisfaction if the journey is not navigated thoughtfully.
- Many talented engineers experience significant barriers that can hinder their promotions, which reflects a need for systemic change in the industry.
- Engaging with the collective experiences of others can illuminate one's own path and foster understanding of the broader challenges in achieving Staff roles.
- Defining effective leadership is a personal journey that requires introspection and open dialogue with peers and mentors.
ch04Overview
The chapter details the landscape of career advancement for software engineers, specifically addressing the dual-track path of technical leadership versus engineering management, and the nuances of attaining and defining roles such as Staff engineer.
- The Senior software engineer level is often a pivotal point for considering advancements into either technical leadership or management.
- A recognized dual-track career path is emerging, allowing engineers to pursue roles that align with their strengths and career goals.
- It is crucial to navigate the ambiguity surrounding Staff-plus roles by understanding the expected competencies and organizational dynamics.
- Insights from experienced Staff-plus engineers provide valuable guidance for those contemplating their next career move.
ch05p01Operating at Staff (part 1/2)
Transitioning to a Staff engineer role requires shifting mindsets from technical execution to leadership, mentorship, and strategic influence, challenging former assumptions about control and impact.
- The transition to a Staff engineer is less about increased control and more about embracing indirect influence and mentorship.
- Slower feedback cycles inherent in leadership roles can lead to feelings of discouragement; understanding this shift is critical.
- Working on what truly matters requires diligent prioritization amidst a congested workload, which varies significantly across career stages.
- Strong alignment with and responsiveness to authority are essential pillars of effective leadership in technical roles.
ch05p02Operating at Staff (part 2/2)
This chapter explores the unique challenges and strategies for effectively communicating with company executives, emphasizing the importance of understanding their informational preferences and aligning with their priorities during discussions.
ch06Getting the title where you are
This chapter explores the complex journey from a Senior engineer to a Staff engineer, emphasizing the critical skills and strategic visibility required, alongside the realities of promotion systems that can often hinder progression.
- Achieving a Staff engineer title is not merely about technical skills; it requires navigating systemic barriers in promotion processes.
- The development of relationships and internal visibility within an organization is as crucial as skill development for career advancement.
- Having mentors and sponsors is vital; they can provide pathways through the complexities of organizational dynamics.
- Persistence in building a clear personal brand within your company can counter the ambiguity in promotion criteria.
ch07Deciding to switch companies
Navigating the decision to switch companies is a critical juncture for technology professionals seeking advancement, where weighing internal credibility against external opportunities can shape one's career trajectory.
- Staying at a single company may seem loyal, but for career advancement in tech, it can sometimes be a hindrance.
- Changing companies can offer new opportunities to leverage your skills and gain necessary recognition.
- Feeling burned out or stagnant could serve as a catalyst for exploring new roles outside your current company.
- Current reputations can stick, but new positions allow individuals to leave past baggage behind.
ch08Stories
In this chapter, the author reflects on the significance of personal experiences and diverse narratives in shaping one’s professional identity, emphasizing the need to transcend individual-centric perspectives to connect with a broader audience.
- Embracing diverse narratives enriches professional understanding and fosters a sense of community.
- The author’s realization about their own limited perspective reveals the broader need for inclusivity in industry storytelling.
- Engaging with the stories of others can provide profound insights and guidance on navigating complex career paths.
- Inclusivity in narratives aids in building connections and empathy within professional spaces, making shared understanding possible.
ch09Ras Kasa Williams - Staff Engineer at Mailchimp
Ras Kasa Williams, a Staff Engineer at Mailchimp, provides insight into the multifaceted role of a Staff-plus engineer, emphasizing the importance of technical leadership, mentoring, and strategic alignment in engineering teams.
- A Staff Engineer's role transcends technical execution; it's about fostering an environment where others can thrive and succeed.
- Building relationships within the organization enhances collaborative problem-solving and decision-making, increasing overall project effectiveness.
- Visibility and recognition are vital; they empower Staff Engineers to influence the engineering strategy and align with business objectives.
- Emphasizing mentorship and personal development transforms team dynamics and cultivates a culture of growth and self-sufficiency among engineers.
ch10Keavy McMinn - Senior Principal Engineer at Fastly
Keavy McMinn, a Senior Principal Engineer at Fastly, shares insights into her role, the impact of trust and collaboration in engineering, and her journey in advocating for effective API design.
- Trust is essential for effective engineering leadership; being hired with it is a significant advantage that can facilitate impactful change.
- The role of a Staff-plus engineer is not defined solely by technical expertise but by the ability to advocate for and influence organizational practices collaboratively.
- Implementing design documentation early in project phases minimizes future complications and optimizes workflow efficiency.
- Public speaking can serve as a powerful platform for visibility and career development, opening up unexpected opportunities for growth.
ch11Bert Fan - Senior Staff Engineer at Slack
Bert Fan’s journey as a Senior Staff Engineer at Slack illustrates the multifaceted role of a Staff-plus engineer, the significance of trust and relationships, and the balance between technical implementation and strategic impact.
- The role of a Staff-plus engineer transcends coding; it’s about enabling others and strategically influencing outcomes.
- Success in advancing to a Staff-plus position often hinges on the strength of relationships, not just technical competence.
- Engineers must recognize that luck and timing play significant roles in career advancement, but proactive effort is critical.
- Embracing the practice of regular communication fosters an environment of trust and honesty that benefits everyone's work experience.
ch12Katie Sylor-Miller - Frontend Architect at Etsy
Katie Sylor-Miller discusses her journey as a Frontend Architect at Etsy, emphasizing the pivotal role of web performance and the unique challenges of managing influence without authority in a rapidly evolving tech landscape.
- Prioritizing web performance is essential for maintaining competitiveness; it should be an organizational focus rather than an afterthought.
- Engaging in proactive problem identification and advocacy can elevate your role from an individual contributor to an organizational influencer.
- Quantifying contributions in less tangible roles requires diligence and self-reflection; implementing structured tracking systems can aid this process.
- Empathy for users and a broader understanding of their experiences can significantly enhance technical decisions and architectural outcomes.
ch13Ritu Vincent - Staff Engineer at Dropbox
Ritu Vincent shares her journey as a Staff Engineer at Dropbox, detailing her pivotal role in a new internal incubator meant to drive innovation and how her responsibilities have evolved with the company's needs.
ch14Rick Boone - Strategic Advisor to Uber’s VP of Infrastructure
Rick Boone’s role as a Strategic Advisor to Uber's VP of Infrastructure navigates strategic, technical, and cultural complexities, embodying a unique synthesis of engineering leadership and organizational psychology.
- The role of a Strategic Advisor necessitates a fluid understanding of both technical and cultural contexts.
- Successful alignment with leadership is rooted in shared values, trust, and a commitment to advocating for the team.
- Mentorship plays a crucial role in fostering talent and promoting inclusivity within tech organizations.
- Awareness of team emotional states can significantly influence organizational health and productivity.
ch15Nelson Elhage - Formerly Staff Engineer at Stripe
Nelson Elhage reflects on his journey and responsibilities as a Staff Engineer at Stripe, detailing the complexities of technical leadership and organizational navigation in a rapidly evolving company.
ch16Diana Pojar - Staff Data Engineer at Slack
Diana Pojar shares her journey from mid-level engineer to Staff Data Engineer at Slack, highlighting the pivotal skills necessary for growth within technical leadership roles and the importance of mentorship.
- Advancing to a Staff-plus engineer role involves more than technical expertise; leadership and mentorship are equally crucial.
- Building relationships and advocating for peers can significantly enhance an engineer's influence within an organization.
- Reflective career planning and intentional choices are key elements in navigating the path to leadership in technology.
- Overcoming impostor syndrome requires a community of support and belief in oneself as capable of driving impactful change.
ch17Dan Na - Staff Engineer and Team Lead at Squarespace
Dan Na shares how transitioning from a hands-on developer to a Staff Engineer at Squarespace reshaped his role, emphasizing the balance between technical strategy and cultural advocacy within the engineering organization.
- Transitioning to a Staff-plus role requires a shift from primarily focusing on technical outputs to also encompassing broader business and cultural responsibilities.
- Effective engineering leadership is defined not only by technical acumen but by a proactive approach to enhancing team culture and collaboration.
- Real impact as a Staff-plus engineer comes from advocating for changes that address both technical needs and the interpersonal dynamics of engineering teams.
ch18Joy Ebertz - Senior Staff Software Engineer at Split
Joy Ebertz articulates her journey to becoming a Senior Staff Software Engineer, shedding light on how she navigates her role through technical vision-setting, advocacy for change, and the importance of mentoring others in the engineering landscape.
ch19Damian Schenkelman - Principal Engineer at Auth0
Damian Schenkelman, a Principal Engineer at Auth0, discusses the intricacies of his role, emphasizing the blend of leadership and technical influence required to drive company-wide initiatives in a rapidly evolving tech landscape.
- The role of a Principal Engineer goes beyond coding; it involves influencing and shaping the organization’s technical strategy.
- Clarity in technical direction is critical for maintaining team efficacy and morale in a rapidly growing environment.
- Engaging various stakeholders early in the decision-making process enhances buy-in and reduces resistance to change.
- Creating structured guidelines can empower teams to make informed technical decisions autonomously.
ch20Dmitry Petrashko - Tech Advisor to the Head of Infra at Stripe
In this chapter, Dmitry Petrashko shares insights into his dual roles as a Staff Engineer and Technical Advisor at Stripe, highlighting the importance of collaboration, strategic thinking, and the challenges faced by engineers at different levels of impact.
- Empowerment of others leads to increased innovation; staff engineers should prioritize sponsorship alongside mentorship.
- Better communication and collaborative planning can significantly enhance project outcomes, ensuring alignment between technical and business objectives.
- A strategic balance between hands-on coding and advisory responsibilities is critical for staff engineers to maintain their effectiveness.
- Understanding the needs of users and regularly engaging with them informs better engineering practices and project scoping.
ch21Stephen Wan - Staff Engineer at Samsara
Stephen Wan's journey as a Staff Engineer at Samsara illustrates the evolving role of technical leaders who simultaneously advocate for technological innovation and nurture their team's growth in a fast-growing company.
ch22Ending words
This chapter critiques the existing perceptions of technical leadership within the engineering industry, arguing that transformation is possible through collective and individual efforts to redefine the Staff-plus engineer role.
- Technical leadership in the software industry is perceived as broken, but this can change through collective action.
- Improving the Staff-plus engineer role is not an isolated responsibility; it requires a supportive cultural shift from all involved parties.
- Managers often lack experience with effective Staff-plus engineers; partnering with them can help align visions and dispel fears.
- Fear of ineffective technical leadership creates barriers; this fear can be alleviated by cultivating a community of effective role models.
ch23Additional resources on Staff-plus engineering
This chapter emphasizes the importance of building a strong professional network and provides a curated list of resources essential for aspiring Staff-plus engineers, underscoring that personal connections often eclipse traditional learning materials.
- Networking is paramount for growth as a Staff-plus engineer; it often outweighs traditional learning methods in significance.
- The most valued resources for professional development are often peers and mentors, not solely books and articles.
- Engaging in community conversations can provide insights that formal education may overlook.
- Understanding the roles and responsibilities of different engineering positions is crucial for aspiring leaders.
ch24Where do Staff-plus engineers fit into the org?
This chapter explores the organizational placement of Staff-plus engineers, examining whether they should report to immediate managers or more senior leaders to optimize their effectiveness and access to vital resources.
- Organizational mathematics can effectively guide team design, but the placement of Staff-plus engineers often reveals significant layer contradictions.
- Many organizations struggle to align their theoretical reporting structures with actual practices, leading to frustration among senior technical leaders.
- The 'Office of the CTO' can alleviate issues related to trust and delegation, but its adoption must be deliberate and justified.
- Timeliness in making reporting adjustments can significantly influence an employee's adaptation and organizational efficiency.
ch25Managing Staff-plus engineers
This chapter addresses the unique challenges and strategies involved in managing Staff-plus engineers, emphasizing how their roles differ from those of Senior engineers and the essential support they require from their managers.
- Managing Staff-plus engineers requires a fundamental shift from directive management to a sponsorship role, fostering independence and accountability.
- Regular feedback is essential for high-potential engineers to navigate less immediate success metrics and maintain their motivation.
- Engaging Staff-plus engineers in the planning process can effectively harness their expertise and allow for better alignment of technical initiatives with business goals.
- It’s vital for managers to create space for deep thinking and strategic work while ensuring engineers stay connected to their team's day-to-day context.
ch26Designing a Staff-plus interview loop
The chapter demystifies the complexities of creating an effective interview loop for Staff-plus engineering roles, emphasizing the need to focus on distinct signals and pertinent formats beyond conventional assessments.
ch27Staff-plus career ladders
In exploring effective career ladders for Staff-plus roles, this chapter argues against the rigidity of traditional frameworks, emphasizing the need for adaptability and individual context when navigating career progression.
- Career ladders, while important, should not be viewed as inflexible blueprints for career progression.
- The complexities of Staff-plus roles demand a tailored approach to career advancement that reflects individual journeys.
- Critical engagement with existing frameworks enhances self-awareness and career satisfaction.
- Understanding the distinction between how career ladders work in theory and in practice is essential for navigating professional growth.
Questions this book answers
- What do Staff-plus engineers actually do, and how does the role differ from a Senior engineer?
- What are the different archetypes of Staff-plus roles and which fits you?
- Does the Staff title even matter, and what advantages does it confer?
- How do you operate effectively as a Staff-plus engineer?
- How do you get promoted to Staff at your current company versus switching companies?
Glossary
- Sponsor Access and Activation
- The presence of an empowered organizational sponsor who advocates for the engineer's recognition and advancement, and the engineer's effectiveness in activating and supporting that sponsorship.
- Alignment with Organizational Authority
- The degree to which the engineer remains aligned with their sponsor's and leadership's worldview, priorities, and values, maintaining trust by avoiding surprises and feeding upward context.
- High-Impact Work Prioritization
- The disciplined practice of allocating finite working time to genuinely high-impact work while avoiding snacking, preening, and chasing ghosts.
- Engineering Strategy and Technical Quality Practices
- The leadership practices of producing bottom-up engineering strategy and vision and of systematically managing technical quality to align technical direction and improve durable outcomes.
- Internal and External Visibility
- The extent to which an engineer is known for good work across the organization and (optionally) externally, while minimizing consumed organizational attention.
- Network of Peers
- A deliberately cultivated set of trusted peers, mentors, and former colleagues who provide honest feedback and decision vetting and reduce isolation.
- Company Fit and Opportunity Conditions
- The contextual conditions of the company—growth, archetype availability, durability, alignment of valued skills, and meritocrat/proceduralist orientation—that shape the availability of and friction toward Staff-plus roles.
- Energized Engagement
- The psychological state of being intrinsically energized and motivated by one's work, sustaining effort through the slow feedback loops characteristic of Staff-plus roles.
Related in the library
- Self-Publishers Legal Handbook
- A Philosophy of Software Design (2nd Edition)shared: Systems
- Accelerate The Science of DevOpsshared: Systems
- Analytics Engineering with SQL and dbt Building Meaningful Data Models at Scaleshared: Systems
- Architecture Patterns with Pythonshared: Systems
- Artificial Intelligence - A Very Short Introductionshared: Systems
Tools these methods power