Scrolls
11 min read
On this page

Preparing for the Next Level

At some point in your Senior Engineer career, you will face a fork: continue deepening your technical impact as a Staff Engineer on the IC track, or move into people leadership as a Team Leader on the management track. Both paths are legitimate. Neither is a promotion over the other. But preparing for either one requires deliberate, sustained effort that goes well beyond doing your current job well.

This chapter covers what it takes to get ready for both paths, the foundations they share, and how to signal your readiness to the people who make promotion decisions.

Understanding the Fork

                         ┌─ Staff Engineer (IC track)
Senior Engineer ─────────┤
                         └─ Team Leader (Management track)

The fork is not a one-way door. Engineers move between tracks throughout their careers. But the initial transition is easier if you prepare intentionally rather than drifting into whichever opportunity appears first.

Both paths require you to expand beyond individual contribution. The difference is the medium through which you create leverage. Staff Engineers create leverage through technical systems, architecture, and cross-team alignment. Team Leaders create leverage through people — hiring, developing, and enabling a group to deliver more than they could individually.

If you are not sure which path to pursue, that is normal. The best preparation strategy is to build the shared foundations first and then specialize as your preference becomes clear.

Shared Foundations

Before diverging into track-specific skills, both paths demand a common set of capabilities. These are not nice-to-haves — they are prerequisites.

Communication

At Senior, most of your communication is with your immediate team. At the next level, regardless of track, your audience expands: other teams, product managers, designers, leadership. The bar for clarity rises sharply.

Start practicing now:

Communication upgrades for Senior Engineers:
- Write design documents for features you own, even if nobody asks
- Summarize technical decisions in writing after meetings
- Present at team demos with context a non-engineer can follow
- Send weekly status updates to your manager with crisp summaries
- Practice explaining trade-offs without defaulting to jargon

A Staff Engineer who cannot write a clear RFC will fail. A Team Leader who cannot run a productive meeting will fail. Both start with the same underlying skill: structuring your thoughts and communicating them to people with different contexts.

Mentoring

Mentoring is the earliest form of leverage you can build as a Senior. Every hour you spend helping a mid-level engineer level up saves dozens of hours downstream. It also builds the trust and influence you will need in either track.

Effective mentoring at Senior level looks like:

  • Pairing with junior engineers on their pull requests, not just reviewing them
  • Helping teammates debug their approach to a problem before they write code
  • Giving feedback that is specific, actionable, and delivered promptly
  • Identifying when someone is stuck and intervening without being asked
  • Sharing your mental models for how you approach unfamiliar problems

If you are not actively mentoring at least one person, you are not preparing for either path.

Ownership & Accountability

Both tracks require you to own outcomes, not just tasks. At Senior, it is easy to define success as "I finished the ticket." At the next level, success means the project shipped, the system is reliable, and the team did not burn out getting there.

Practice taking ownership of ambiguous situations. When a production incident happens and nobody is sure whose responsibility it is, step in. When a project is slipping and the root cause is unclear, investigate. When a dependency team is blocking your work, drive the resolution instead of waiting.

This kind of ownership is visible. Managers and skip-level leaders notice engineers who take responsibility without being asked.

Preparing for Staff Engineer (IC Track)

The Staff Engineer path rewards depth of technical judgment, breadth of organizational awareness, and the ability to influence without authority. You will not get there by writing more code — you will get there by solving bigger problems.

Identifying High-Leverage Work

The single most important Staff-level skill is choosing what to work on. At Senior, your backlog is mostly defined for you. At Staff, you are expected to identify the highest-leverage problems in the organization.

Start building this muscle now:

Finding high-leverage work as a Senior:
1. Map your team's pain points — what slows people down repeatedly?
2. Look at cross-team dependencies — where do handoffs create friction?
3. Read incident postmortems from other teams — are there systemic patterns?
4. Talk to product managers about upcoming roadmap items that have no technical plan
5. Identify technical debt that affects multiple teams, not just yours

A Senior at a payments company noticed that three different teams were each building their own retry logic for third-party API calls. Each implementation had different bugs. She wrote a proposal for a shared resilience library, built a prototype, and got buy-in from all three teams. That single initiative demonstrated Staff-level scope.

Writing Proposals & RFCs

Proposals are how Staff Engineers drive decisions at scale. A well-written RFC can align a dozen teams. A poorly written one wastes everyone's time and erodes your credibility.

Start writing proposals before you have the Staff title. Pick a real problem on your team and write an RFC for it, even if the solution seems obvious. The practice of articulating the problem, evaluating alternatives, and recommending a path forward is what matters.

A strong RFC includes:

RFC structure:
- Problem statement: what is broken & why it matters now
- Context: what has been tried before & why it did not work
- Proposed solution: how it works, with enough detail to evaluate
- Alternatives considered: at least two, with honest trade-offs
- Migration plan: how we get from here to there without stopping the world
- Risks & open questions: what you are not sure about

Share your RFCs broadly. Invite feedback from engineers outside your team. The act of defending your proposal across organizational boundaries is exactly the kind of influence-building that demonstrates Staff readiness.

Building Org-Wide Influence

Influence at Staff level comes from trust, not authority. You build trust by consistently demonstrating good judgment, helping other teams succeed, and being honest when you do not know something.

Concrete steps to build influence:

  • Attend architecture reviews for systems outside your team and ask thoughtful questions
  • Offer to review design documents from other teams when they post them
  • Contribute to shared infrastructure or developer tooling that benefits the org
  • Build relationships with Staff Engineers and Tech Leads on adjacent teams
  • When you disagree with a technical direction, write down your reasoning and share it respectfully

A Senior engineer who is only known within their own team will not be promoted to Staff. The promotion committee will ask: "Who outside this team can speak to this person's impact?" If the answer is nobody, the case is weak.

Preparing for Team Leader (Management Track)

The Team Leader path rewards people skills, operational discipline, and the ability to create clarity from ambiguity. You will not get there by being the best coder on the team — you will get there by making everyone around you more effective.

Delegation

Delegation is the hardest skill for engineers transitioning to management. Your instinct is to do the work yourself because you can do it faster. That instinct is correct in the short term and catastrophic in the long term.

Start practicing delegation now, while you are still an IC:

Delegation practice for Senior Engineers:
- When a bug comes in that you could fix quickly, route it to a junior
  engineer and coach them through it instead
- Assign parts of your design to teammates and let them own the decisions
- Resist the urge to rewrite someone's pull request — give feedback instead
- Let someone else present work that you contributed to
- Accept that delegated work will be 80% as good as yours, and that is fine

A Senior engineer at a logistics company was leading a database migration. Instead of writing the migration scripts himself, he broke the work into pieces, assigned each piece to a different team member, wrote a detailed guide, and held daily check-ins. The migration took 20% longer but three engineers learned the system deeply. His manager noted this as clear evidence of leadership readiness.

Feedback & Difficult Conversations

As a Team Leader, you will deliver feedback weekly — sometimes daily. You will tell people things they do not want to hear. You will have conversations about underperformance, interpersonal conflict, and career disappointment. If you cannot do this with clarity and empathy, you will fail.

Practice now:

  • Give specific, direct feedback to peers after code reviews or project collaborations
  • When you notice a teammate struggling, have a private conversation instead of ignoring it
  • Practice the SBI model: Situation, Behavior, Impact — describe what you observed and its effect
  • Receive feedback gracefully when it is given to you, even if you disagree

Emotional Regulation

Management is emotionally demanding in ways that IC work is not. A frustrated engineer vents to you about a decision you did not make. A team member cries during a one-on-one. Two engineers on your team have a personal conflict that is affecting sprint velocity. Your skip-level asks why the project is late, and the real reason is that you underestimated the scope.

You need to stay calm, fair, and clear-headed in all of these situations. This is a trainable skill, not a personality trait.

Emotional regulation practices:
- Notice your physiological stress responses (tight chest, racing heart)
  and practice pausing before responding
- Journal after difficult interactions to process your reactions
- Develop a habit of asking "What does this person need right now?"
  before reacting to what they said
- Find a peer group of other aspiring or current managers to debrief with
- Recognize that your mood is contagious — your team reads your energy

People Skills & Relationship Building

The management track requires you to build relationships intentionally. You need to understand what motivates each person on your team, what their career goals are, and what kind of support they need to do their best work.

Start by running informal one-on-ones with teammates. Ask about their career goals. Learn what frustrates them about the development process. Practice active listening — let someone finish their thought before you respond.

Pay attention to team dynamics. Who collaborates well together? Who avoids working with whom? Where are the unspoken tensions? A Team Leader who cannot read a room will be constantly surprised by problems that were visible to everyone else.

How to Signal Readiness

Doing the work is necessary but not sufficient. You also need the decision-makers to know you are doing the work. This is not about self-promotion — it is about making your impact visible.

For the IC Track

Signals of Staff readiness:
- You have authored RFCs or proposals that were adopted beyond your team
- Engineers outside your team seek your opinion on technical decisions
- You have identified & driven solutions to cross-team problems
- Your technical writing is clear, thorough, and widely read
- You can articulate the technical strategy for your domain
- You have a track record of making correct calls on ambiguous problems

For the Management Track

Signals of Team Leader readiness:
- You have led projects involving multiple people & delivered results
- Teammates come to you when they are stuck or need guidance
- You have given difficult feedback and the person improved
- You have demonstrated delegation — results through others, not just yourself
- You can describe team dynamics & individual motivations accurately
- You have stepped up during operational crises and maintained calm

Making Your Intent Known

Tell your manager which track you are interested in. This is not a binding contract — it is information that helps your manager create opportunities for you. Many engineers are never considered for Staff or Team Leader simply because nobody knew they were interested.

Ask your manager: "What would I need to demonstrate to be ready for Staff Engineer?" or "What would I need to demonstrate to be ready for Team Leader?" The answer will be specific to your organization and your current gaps.

Practical Steps for Both Paths

Regardless of which track you are pursuing, these concrete actions accelerate your readiness:

Quarterly preparation checklist:
- [ ] Update your impact log with specific, measurable contributions
- [ ] Seek feedback from at least two people outside your immediate team
- [ ] Complete one piece of work that is explicitly above your current level
- [ ] Have a career conversation with your manager about your target track
- [ ] Read one book or in-depth resource on your target track's core skills
- [ ] Mentor or coach at least one engineer more junior than you
- [ ] Contribute to at least one initiative outside your team's backlog

For the IC track specifically: write one RFC or technical proposal per quarter. Even if it is not adopted, the practice sharpens your thinking and creates artifacts that demonstrate your judgment.

For the management track specifically: volunteer to lead a project, facilitate a retrospective, or onboard a new team member. Each of these gives you a low-risk opportunity to practice leadership skills while your manager observes.

Common Pitfalls

  • Waiting to be asked. Neither promotion happens to people who wait. Both tracks reward initiative — you need to seek out the opportunities that demonstrate readiness.
  • Conflating the two tracks. Preparing for Staff by practicing delegation, or preparing for Team Leader by writing RFCs, is not wrong — but it is not targeted. Know which track you are aiming for and prioritize accordingly.
  • Optimizing for visibility over substance. Volunteering for high-profile projects without delivering real impact will be noticed — and not in the way you want. Decision-makers distinguish between presence and contribution.
  • Assuming your work speaks for itself. It does not. You need advocates, artifacts, and explicit conversations with your manager about your goals. Modesty is a career liability at this stage.
  • Trying to skip the shared foundations. An aspiring Staff Engineer who cannot mentor is missing a core signal. An aspiring Team Leader who cannot write clearly is missing a core signal. Build the foundations before specializing.
  • Burning bridges by moving too fast. Taking on cross-team work or leadership opportunities while neglecting your primary responsibilities damages your reputation. Expand your scope gradually and with your manager's support.
  • Deciding under pressure. Do not choose your track because your manager needs a Team Leader right now or because a Staff slot just opened up. Choose based on what energizes you and where your strengths lie. The wrong track at the right time is still the wrong track.

Key Takeaways

  • Senior Engineer is a fork: you can advance as a Staff Engineer (IC track) or a Team Leader (management track), and both are equally valid career paths.
  • Both tracks share common foundations: communication, mentoring, and ownership. Build these first regardless of which direction you are heading.
  • The Staff Engineer path requires identifying high-leverage work, writing proposals, and building org-wide influence through trust and technical judgment.
  • The Team Leader path requires delegation, delivering feedback, emotional regulation, and deep understanding of people and team dynamics.
  • Signaling readiness means making your impact visible through artifacts, advocates, and explicit career conversations with your manager.
  • Tell your manager which track you want. Many engineers are overlooked simply because nobody knew they were interested.
  • Preparation is not passive — both tracks reward people who seek out above-level work and demonstrate the behaviors before they have the title.
  • The wrong track at the right time is still the wrong track. Choose based on what energizes you and what you are naturally drawn to, not what is available.