Sample ReportIllustrative content · not generated from a real assessment

Engineering Career Intelligence Report

Sample engineer · Backend, distributed systems · 7 years experience · Current level: Senior Engineer · Target: Staff Engineer · Archetype: Systems Thinker

Promotion readiness
64%
Senior → Staff
Technical
84
of 100
Maturity
72
of 100
Leadership
48
of 100
01 · Executive Summary

Technically strong, leadership-bound

This engineer is operating consistently above bar on technical execution. System design, code quality, and debugging instincts are all approaching Staff-level. The promotion gap is not technical depth — it is leadership influence and strategic framing.

Promotion to Staff requires visible impact across teams and a strategic narrative that reframes execution as business outcomes. The next 90 days should focus on cross-team surface area, not deeper technical work.

02 · Current Position

Where you stand today

Current
Senior Engineer
Calibrated · stable
Target
Staff Engineer
12–18 months realistic
Readiness
64%
Above-average trajectory
Promotion readiness
64% · Senior → Staff

You are a credible Senior with Staff-shaped technical instincts. Closing the gap is a scope and visibility problem, not a skills problem. Most engineers in this position promote within 4 calibration cycles when they address influence directly.

03 · Dimension Analysis

Three dimensions, one clear gap

Each dimension blends multiple sub-domains. Technical Excellence is strong; Leadership & Influence is the bottleneck.

Technical Excellence
84 / 100
Strong system design, code quality, and debugging instincts. Operating above bar for Senior; approaching Staff-level technical scope.
Engineering Maturity
72 / 100
Reliable execution and ownership within team scope. Process and prioritization are solid; cross-team planning is still developing.
Leadership & Influence
48 / 100
Primary gap. Limited visible influence outside the immediate team. Mentorship is informal and strategic narrative is underdeveloped.
04 · Engineering Archetype

Systems Thinker

You think in interfaces, invariants, and failure modes. You are the engineer the team turns to when something subtle is wrong. This archetype produces durable technical leaders — when paired with deliberate influence work.

Strengths
  • Reasons clearly across system boundaries and trade-offs.
  • Spots failure modes others miss in design review.
  • Writes technical artifacts that hold up over time.
Blind spots
  • Defaults to depth when the situation calls for breadth.
  • Under-invests in narrative — assumes the work speaks for itself.
  • Avoids ambiguous people-shaped problems.
Promotion risks
  • Skip-level leaders see strong execution but unclear scope.
  • Promotion packet reads like a feature list, not a strategy.
  • Cross-team peers cannot point to your influence on their work.
Growth path
  • Trade one quarter of depth for one quarter of cross-team influence.
  • Publish thinking, not just code. RFCs, post-mortems, vision docs.
  • Pick one ambiguous org-level problem and own its framing.
05 · Career Blockers

What is actually holding you back

Ranked by impact on your next promotion. Address top-down.

Blocker 01

Leadership Influence

High impact
Why it matters

Staff-level promotions require demonstrable influence beyond your immediate team. Skip-level leaders cannot currently name a project you drove across orgs.

Recommended action

Lead one cross-team initiative this quarter. Publish a design doc that at least two adjacent teams review and adopt.

Blocker 02

Strategic Thinking

High impact
Why it matters

You execute well on assigned scope but rarely frame work in terms of business or org-level outcomes. Promotion packets need a strategic narrative, not a feature list.

Recommended action

For each major project, write a one-page brief: business problem, alternatives considered, why this bet, expected impact.

Blocker 03

Product Thinking

Medium impact
Why it matters

You defer most product trade-offs to PM. Staff engineers shape what gets built, not just how. This shows up as missing user-impact framing in your work.

Recommended action

Partner with PM on one feature end-to-end. Own the trade-off doc and present user-impact metrics in review.

06 · 90-Day Roadmap

The next quarter, sequenced

Concrete moves designed to close your top blockers, not generic advice.

Month 1
Visibility
  • Publish a system design RFC for a system you own.
  • Volunteer to lead one cross-team sync as note-taker and driver.
  • Schedule three skip-level coffees to map their priorities.
Month 2
Influence
  • Drive consensus on a contested technical decision across two teams.
  • Mentor one mid-level engineer with weekly 1:1s and a written growth plan.
  • Present a technical talk at an internal engineering forum.
Month 3
Strategic Scope
  • Scope a multi-quarter initiative with clear business impact framing.
  • Co-author the team's planning doc for next half.
  • Collect peer feedback from three cross-team collaborators.
07 · 12-Month Plan

The arc to Staff

Quarterly direction, not a checklist. Adjust as calibration signals come in.

Q1
Build cross-team surface area

Establish yourself as a technical voice outside your team. One published RFC, one cross-team initiative, three skip-level relationships.

Q2
Own a strategic initiative

Drive a multi-team project end-to-end. Frame it in business terms. Make the trade-offs and outcomes visible to leadership.

Q3
Develop other engineers

Formal mentorship of two engineers. Contribute to hiring bar-raising. Land a measurable improvement in team velocity or quality.

Q4
Promotion packet & calibration

Assemble evidence with strategic narrative. Align with manager and skip-level. Target the next calibration cycle as a credible Staff candidate.

Your report, your engineer

Find out exactly what is blocking your next level.

A 20-minute professional assessment. You get a calibrated level, your archetype, your real blockers, and a roadmap built for you — not generic advice.

This is sample content. Your report will reflect your actual answers.