What Coaching Sessions Actually Cover

Sessions run 60 to 90 minutes, with a pre-session note describing what is open. The agenda is set by what the engineer is working on right now, not by a curriculum. Topics shift session to session but tend to cluster in a small set of themes.

• Scope definition: choosing the next 6 to 12 month technical bet, the work that earns the title
• Influence without authority: getting a multi-team change adopted without a manager role
• Technical strategy: writing the document that frames a decision so leadership can sign off
• Organizational design: when to push for a new team, when to argue against creating one
• Working with engineering leadership: how to be a useful peer to a director or VP without being a junior
• Promotion packet preparation: artifacts, narratives, sponsors, calibration timing
• Career decisions: stay vs leave, join a smaller company, take a manager track instead, ride out a reorg
• Sponsorship dynamics: finding sponsors, navigating sponsor changes, building visibility outside the immediate team

The Four Staff Archetypes and Which One the Engineer Is

Larson and Reilly's framework names four common shapes the staff role takes: Tech Lead, Architect, Solver, Right Hand. The framework is not a strict taxonomy, and Alex Ewerlof and others have pointed out that treating archetypes as job descriptions becomes an anti-pattern. The honest use is diagnostic: most senior engineers default to one archetype that fits their existing skills, and the promotion fight is usually about whether the company needs that archetype, whether the engineer's manager recognizes it, and whether the engineer is willing to do the work that archetype actually requires.

• Tech Lead: partners with one or two managers on a focused area, drives execution and craft, the most common entry archetype to staff
• Architect: owns direction and quality in a critical area, deep technical constraints plus organizational leadership, common past 100 engineers
• Solver: digs into arbitrarily hard problems, jumps between hotspots, the rarest hire and the hardest to staff for
• Right Hand: extends an executive's scope and authority, lives close to the VP or CTO, mostly exists past 1,000 engineers
• The diagnostic question is rarely "which archetype are you" but "which archetype does your company currently need and does anyone realize it"
• Coaching adapts the engineer's current trajectory to fit the gap the company has open, not the other way around

Why Staff Promotions Stall

A senior engineer who is great at senior work and expecting promotion to staff is the most common stall pattern in the industry. The level shift is not "be more senior", it is a different job. The patterns below repeat across companies and tend to be visible to an outside coach in one to two sessions.

• Doing senior work harder: the engineer is the best IC on the team but the work they do is still senior-shaped, not staff-shaped
• No visible scope outside the immediate team: staff work is cross-team by definition, and the engineer's impact reads as local
• No written artifacts: staff work is preserved in docs, RFCs, and decision logs; if the engineer ships great code but writes nothing, leadership cannot calibrate them up
• No sponsor at the staff or principal level: promotion to staff almost always requires a senior person who will speak for the engineer in calibration
• No retired bad work: staff engineers also kill things, and engineers who have only added are missing half the resume
• Wrong archetype for the company's actual need: the engineer is acting as a Solver in a company that needs a Tech Lead, and the work does not get recognized

Two Buyer Types: IC-Funded and Employer-Funded

The promotion question has two natural funders. The engineer themselves, paying out of pocket because they want a confidential voice their manager is not. Or the company, paying because they want to retain and grow a high-potential senior who is close to staff but stuck. The shape of the coaching work is similar; the contract and reporting differ.

• IC-funded: month-to-month, sessions billed individually or in small packs, full confidentiality, no employer involvement
• IC-funded use cases: out-of-pocket investment in their own career growth, second opinion on a stalled promotion, prep before a job search
• Employer-funded: invoiced to the company, scope agreed with the manager, periodic written progress note (objectives and themes, never session contents)
• Employer-funded use cases: retention investment for a flight-risk senior, deliberate development of a staff candidate, succession planning under a strong manager
• Confidentiality is non-negotiable in both cases: the coach never reports session contents to the employer; only the objectives and high-level themes
• Pricing tracks buyer: IC-funded usually 10 to 20 percent cheaper per hour than employer-funded, in exchange for tighter scope and direct billing

What a Successful Six-Month Engagement Produces

The point of coaching at this level is not vague growth; it is the engineer making and shipping decisions that move them onto the staff track. The deliverables below are the kind of artifacts that show up when the engagement is working.

• A written technical strategy doc for the engineer's area, reviewed by leadership, that becomes the calibration evidence for the next promotion cycle
• A killed or retired piece of work, with a writeup, that demonstrates the engineer can subtract not just add
• A multi-team or cross-org change shipped where the engineer was the central technical voice
• A sponsor relationship at the staff or principal level, plus a second sponsor outside the direct chain of management
• A clear archetype identification: the engineer knows which staff shape fits their company, and is operating to it consciously
• Either a promotion to staff, or a deliberate decision to leave for a company where the staff shape they are best at exists

Cadence and Format

Most engagements settle into a bi-weekly rhythm with async support in between. Weekly cadence is correct during heavy promotion-cycle moments (packet prep, calibration prep, performance review). Monthly cadence is correct in steady-state periods between cycles. The async channel matters more at this level than at junior coaching, because most of the work is interrupting bad political moves in real time.

• Bi-weekly during steady periods, 60 to 90 minutes per session
• Weekly during the 6 to 8 week window before performance calibration or promotion submission
• Monthly check-in cadence in extended steady-state periods
• Async channel between sessions: tight Slack DM or email thread, response within 24 hours on weekdays
• Live document review: the coach reads the engineer's docs, RFCs, and promotion packets in writing, not just in session
• Pre-session note: one paragraph, what is happening this week, what decision is open, what is at stake

Pricing

Senior IC coaching pricing has hardened in 2026 as the staff-plus market has matured and more companies invest in retention. Public benchmarks from MentorCruise, IGotAnOffer, and direct senior-engineer coaches cluster in a tight range for the senior-to-staff jump.

• Single session, IC-funded: $300 to $600 for 60 to 90 minutes
• Single session, employer-funded: $500 to $900 for the same time, invoiced to the company
• Monthly retainer, IC-funded: $1,500 to $3,000 per month for 2 to 4 sessions and async support
• Monthly retainer, employer-funded: $3,000 to $6,000 per month, typically with a quarterly written progress note
• Promotion-cycle intensives: $5,000 to $10,000 for an 8 to 12 week sprint covering packet prep, calibration prep, and stakeholder mapping
• Red flag: anyone offering staff engineer coaching without having been a staff or principal engineer themselves; the patterns do not transfer from outside

When Coaching Is the Wrong Answer

Coaching does not fix a structural mismatch between the engineer and the company. Some honest disqualifiers below.

• The engineer is not actually close to staff: they have one or two years of senior under them, not five, and the gap is too wide to coach in 6 months
• The company does not promote to staff: some companies cap at senior or staff equivalents and the engineer needs to leave, not coach
• The engineer's manager is the bottleneck and is not coachable themselves: coaching the IC sharpens them, but the promotion will still not happen
• The engineer wants to switch to engineering management; staff coaching does not transfer cleanly and a separate EM coach is the right answer
• The engineer has stalled because of a fit problem with the codebase, the company's technology, or the industry; coaching cannot fix domain mismatch

How to Interview a Staff Engineer Coach

A 30 to 45 minute intro call usually tells the engineer whether the coach has lived the shift or only read the books. The questions below tend to expose the difference quickly.

• Ask for a specific staff-level promotion they navigated themselves, what the packet contained, who their sponsors were
• Ask how they would diagnose a senior engineer who is stuck: which signals do they look at first
• Ask what they would do if the engineer's manager were the blocker: tests for political realism
• Ask which archetype they default to and which they coach into most often; honest answers are specific
• Ask for a writing sample of a technical strategy or RFC they wrote at staff level, not just talked about
• Ask how they end engagements: a coach who cannot describe how they make themselves unnecessary is selling indefinite dependency

FAQ