# Coaching Senior ICs to Staff Engineer

Source: https://www.techinterview.org/post/3233475148/coaching-senior-ic-to-staff-engineer/
Updated: 2026-07-12 · techinterview.org

The Senior → Staff transition is one of the hardest in engineering. Many strong senior engineers stay at Senior for 5+ years, sometimes their entire career. As an EM, helping the right people make that jump is one of the highest-leverage things you do.

## What is different at Staff

Senior engineers ship features. Staff engineers shape the work. Specifically:

- They influence multiple teams or the whole org, not just their team.

- They propose 6–12 month technical directions.

- They grow the engineers around them.

- They partner deeply with product, design, and executives.

- As a multiplier, their work makes other engineers more effective.

The "do more" version of senior is not staff. The "different kind of work" is.

## Common gaps

### Strong code, narrow scope

Engineer is a brilliant individual contributor but works only on their team's problems. Doesn't engage with adjacent teams or org-level technical decisions.

Coaching: assign cross-team initiatives. Encourage attendance at architecture review meetings. Give them visibility into the broader org.

### Strong scope, weak written communication

Engineer has good technical instincts but does not document them. Decisions disappear into Slack threads.

Coaching: require design docs for medium+ projects. Provide feedback on writing. Promote those who do this well.

### Strong execution, weak strategic thinking

Engineer can deliver any project assigned but does not propose new directions.

Coaching: ask "what should our team be working on in 6 months?" Push them to propose, not just execute.

### Strong strategy, weak follow-through

Engineer proposes great ideas but does not see them through. Other engineers do not trust their proposals.

Coaching: pick one of their proposals; commit to delivery. Build the track record.

## The visibility problem

Even with the right skills, an engineer cannot be promoted without visibility. Calibration discusses people leadership has heard of.

Coaching:

- Get them to present at architecture reviews

- Have them write engineering blog posts or internal Loom videos

- Pair them with cross-team partners explicitly

- Mention their work in your weekly updates to your manager

## The promotion calendar

Senior → Staff promotions typically take 18–36 months of deliberate work:

- 6 months: identify the right person and the gap

- 6–12 months: targeted scope expansion and visibility

- 6–12 months: build the track record at staff-level work

- Promotion cycle: build the case

Trying to compress is rarely successful.

## The promotion packet

For Staff promotion, the packet typically includes:

- Concrete examples of work at the next level

- Peer testimony from senior engineers and EMs

- Cross-functional recognition

- Comparison to the level rubric

Stronger packets have specific, dated examples with measurable impact.

## The "calibration says no"

Sometimes you advocate; calibration disagrees. Your job:

- Take the feedback seriously

- Document the specific gaps cited

- Plan for next cycle with those gaps in mind

- Be straight with the report; don't blame calibration

"You did not get promoted; here is exactly what to focus on" beats "calibration is unfair."

## When promotion is not the answer

Sometimes the right move is:

- Lateral to a different team where staff scope exists

- Stay at senior with growing comp (some companies stack senior comp generously)

- Move to a different company at the staff level

- Re-evaluate whether IC track is the right fit

## The competing-offer leverage

Strong seniors often get external staff offers. This forces calibration:

- If you genuinely think they are staff-ready, fight for the promotion + comp adjustment

- If you think they are not yet staff-ready, tell them plainly and accept they may leave

Don't make promises you cannot keep.

## Frequently Asked Questions

### How do I tell if a senior is "almost staff"?

Look at the level rubric. Are they consistently meeting most of the staff-level criteria? "Almost" usually means 70%+ of criteria.

### What if my company does not formalize Staff?

Some companies stop at Senior. Push for a meaningful career path or accept that strong seniors may leave for companies with longer ladders.

### What if my report wants Staff but is not ready?

Level with them. Document the gap. Plan together. Set explicit milestones. Re-evaluate in 6 months.