Aurum
Download

Engineering Career Ladder

A working engineering career ladder: clear levels and competencies, a technical track as strong as management, promotion cycles that are fair and calibrated, and engineers who know what the level above looks like.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Then open the Marketplace in the app, search for Engineering Career Ladder, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

⚙️ Software Engineering

Engineering Career Ladder

Defining levels, expectations and promotion criteria for engineers, including a technical track that does not force people into management.

  1. Audit of current engineering levels and titles
  2. Ladder charter with goals and owners
  3. Choosing the number of levels and the title scheme
  4. Competency dimensions for every level
  5. Level descriptors written by scope and impact
  6. Splitting the staff and manager tracks
  7. Mapping current engineers onto the new levels
  8. Ladder ownership and change process
  9. Self-assessment against your current level
  10. Promotion cycle calendar and process
  11. Promotion calibration sessions
  12. Weekly brag document for your promotion evidence
  13. Quarterly level check-in with each engineer
  14. Promotion outcome fairness review
  15. Annual ladder revision
  16. Ladder FAQ and question log
  17. Level and pay band alignment with the people team
  18. Promotion readiness pipeline for your reports
  19. Writing a promotion case a committee can judge
  20. Writing evidence-based level descriptors
  21. Recognising bias in level and promotion decisions
  22. Understanding staff engineer archetypes
  23. Judging scope and impact beyond shipped features
  24. Delivering a not-yet promotion decision
  25. Comparing published engineering ladders
  26. Title benchmark against the hiring market
  27. Deciding on time-in-level rules
  28. Promotion standard of already working at the level
  29. Making glue work count on the ladder
  30. Ladder addenda for specialist engineering roles
  31. One-page summary for each level
  32. Policy for moving between technical and manager tracks
  33. Offer levelling for new hires
  34. Budgeted or uncapped promotions decision
  35. Executive sign-off of the ladder
  36. Launching the ladder to the engineering organisation
  37. First promotion cycle on the new ladder
  38. Preparing your own promotion packet
  39. Retrospective after each promotion round
  40. Growing from senior to staff engineer
  41. First career ladder for a growing startup
  42. Promotion fairness for engineers returning from leave
  43. New manager learning an existing ladder
  44. Plan for an engineer stuck at one level
  45. Harmonising ladders after a merger or acquisition
  46. One ladder across countries and business units
  47. Principal and distinguished engineer levels
  48. Promotion appeals process
  49. Ladder alignment with job architecture and the HR system
  50. Measuring whether the ladder works

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Audit of current engineering levels and titles

Before anyone writes a new ladder, someone has to see the mess the old one left: two people with the same title doing very different work, levels granted at hire that were never revisited, and teams that invented their own names. A single spreadsheet of every engineer, their title, level, tenure in level and manager turns arguments about fairness into a picture everyone can look at.

First tasks

  • Export title, level, team and hire date for every engineer from the people system
  • Add the date of each engineer's last level change from promotion records
  • Mark rows where title and pay band disagree
  • Write the one-page summary of the five biggest inconsistencies

Ladder charter with goals and owners

Ladders fail quietly when nobody agreed what they were for. Writing down the problems this ladder must solve (unclear promotions, a missing technical track, inconsistent hiring levels), who owns it and who signs off keeps the later design arguments short and stops the work drifting into a compensation project.

First tasks

  • List the problems from the levels audit that the ladder must fix
  • Invite three managers and two senior engineers into the working group
  • Write what the ladder will not cover in this version
  • Send the charter to the executive sponsor for approval

Choosing the number of levels and the title scheme

Too few levels and promotions become rare cliffs that drive people away; too many and the gaps between them are impossible to describe. Most engineering organisations settle on six to nine levels from graduate to principal, and the titles chosen now will appear on offer letters and public profiles for years, so this decision deserves comparison rather than habit.

First tasks

  • Sketch three candidate level structures on a single page
  • Place the current roster provisionally on each candidate
  • Note where each candidate leaves a gap or a crowded level
  • Hold a decision meeting with the working group and record the choice

Make it yours.

Install Engineering Career Ladder, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.0 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.