Promotion decisions

Promotion readiness

Promotions fail when readiness is assumed. Scenario assessments test decision quality in next-level contexts—trade-offs, prioritization, stakeholder alignment—producing defensible readiness signals for calibration.

Promotion readiness
Problem
Promotion decisions can be subjective and inconsistent. Without evidence, organizations increase failure risk and bias exposure.
Outcome
Higher-quality promotions, reduced failure risk, and fairer advancement decisions supported by comparable evidence.
Worked example

What it looks like at Nano Masters AI Systems Software

Role: Senior software engineer on the integration connectors team, under consideration for promotion to staff engineer
Format: 20-minute next-level scenario with three linked decision points, delivered by link
Fictional blueprint company, used for illustration.

The situation

Core platform teams build reusable connectors that solution teams configure for enterprise customers, and the company has recently pushed for faster deployments with stronger governance. An upstream ERP vendor has changed its API, and the connector is now failing intermittently for several customers. Product management wants the team's committed feature shipped this sprint, and solution teams are already asking for customer-specific fixes.

The decision

As the most senior engineer on the team, the candidate is asked by their manager to recommend how the team spends the next two weeks. There is not enough capacity to do everything.

Option A
Pause the feature, lead a single versioned fix to the shared connector with an observability alert for this failure mode, and agree revised dates with product and solution leads.
The feature slips, but every affected customer gets one supported fix and the next upstream change will be caught early. This is how staff-level engineers are expected to weigh scale against local pressure.
Option B
Help solution teams ship quick customer-specific patches so the feature can still go out on time.
Each customer is unblocked, but the platform now carries several divergent fixes that will break again with the next change. It is a reasonable senior-engineer choice that does not yet reflect next-level thinking.
Option C
Keep the sprint commitment and leave the failures to support until the next planning cycle.
The roadmap stays intact while enterprise customers experience silent workflow failures. It signals that the candidate is optimizing for delivery metrics rather than platform reliability.

What the scorecard shows

The scorecard maps each decision to the staff engineer criteria, such as cross-team prioritization and influence without authority, so it can sit alongside manager input in calibration. The candidate receives a development-focused summary: strengths in technical judgment, for example, and a growth area in negotiating trade-offs with product, with suggested actions before the next cycle.

What we measure

Next-level prioritization
Whether the candidate chooses work by platform-wide impact rather than by the loudest request.
Technical judgment at scale
Whether fixes are designed to hold across customers and future upstream changes.
Influence without authority
How the candidate brings product and solution leads to a revised plan they did not originally want.
Trade-off communication
Whether the costs of the chosen option are stated openly, including what slips and why.
Reliability mindset
Whether observability and early detection are treated as part of the fix, not an afterthought.

FAQ

Common questions

Yes—rubrics can map directly to your promotion criteria and leadership principles.

No—IC promotions also benefit when decision quality and stakeholder handling matter.

Share a development-focused summary that highlights strengths, risks, and suggested growth actions.

No—this adds consistent evidence that complements manager insight and reduces bias.
Want this use case tailored to your roles?
We generate scenarios, decision points, and scorecards in days.