Career Ladders & Promotions

A career ladder is your company’s map of levels — from junior, through mid and senior, into lead, staff or management. Each rung comes with role expectations: the scope of problems you own, how much independence you have, and how far your impact reaches. Promotions feel mysterious until you see that they mostly reward one thing — consistently operating at the next rung before the title catches up. This module shows you how the ladder and the promotion cycle fit together so you can plan rather than hope.

How to read the ladder

Most ladders describe each level along a few axes: scope (a task, a project, a whole area), autonomy (how much guidance you need), and impact (just your work, your team, or the wider org). A junior engineer ships well-defined tasks with support; a senior one takes an ambiguous problem and turns it into a plan others can follow. The titles vary by company, but the underlying progression — from doing the work to shaping the work to multiplying others — is remarkably consistent.

Find the written ladder for your role and read the rung above yours closely. That description is the actual job you are trying to grow into, stated in your company’s own words. It is the single best study guide you have, and surprisingly few people read it.

How promotion cycles really work

A promotion cycle is a scheduled window — often once or twice a year — when managers put forward people who are ready. In most companies it is not your manager alone who decides. Your manager writes a promotion case arguing you are already performing at the next level, and a committee or panel of other leaders reviews it for consistency and fairness across teams. This calibration step is why “my manager said yes” is necessary but not always sufficient.

The crucial detail: promotions usually recognise a level you are already operating at, not a level you might reach if promoted. The case is built from evidence — projects you led, decisions you owned, the times you raised the bar for others. That evidence has to exist before the cycle opens.

Why expectations rise

When you move up, the role expectations reset to the new level — and your old level’s “exceeds expectations” becomes the new level’s baseline. This is normal, not a punishment. It is why a promotion can feel like starting over, and why steady, sustained performance at the new level matters more than one heroic project.

A promotion confirms a change that has already happened in your work. Aim to make the title a formality, not a leap.

Building your case over time

Because the decision rests on evidence reviewed by people who may not see your daily work, your job between cycles is to generate and surface that evidence. Take on projects that stretch into next-level scope. Make your contributions visible — not by boasting, but by writing things down, presenting results, and letting your manager see the ambiguity you handled. Keep notes you can hand your manager when they sit down to write your case; you are effectively giving them the raw material.

Spot the level

Read each situation and decide for yourself, then tap a card to flip it and check your answer.

Sort the evidence

Drag each piece of evidence into the bucket showing which level it supports—or tap a chip, then tap a bucket. Hit Check placement when you’re done.

How to use it

Open the conversation early, not in the cycle. Once or twice a year is too late to start. In a 1:1, try:

• “What does the next level look like for someone in my role?”
• “Where am I already operating at that level, and where’s the gap?”
• “What would a strong promotion case for me need to show?”
• “Is there a project coming up that would stretch me into next-level scope?”

Then act on the answers: pick up the stretch work, document the impact, and revisit the gap every quarter. When the cycle opens, you and your manager are assembling a case from real evidence rather than scrambling. Promotions reward people who made the decision easy — start being that person a level early, and the rest tends to follow.