Engineering Career Ladder Template (IC and Manager Tracks)

Engineering Career Ladder: [Organisation name]

Career framework for software engineers and engineering managers: the individual contributor (IC) and manager tracks, the levels and their scope, six competency areas with behaviour descriptors per level, the expectations matrix, the promotion process and evidence rules, calibration, level-change rules, fairness and bias checks, and the review cadence for the ladder itself. There is no formal standard for engineering ladders; the structure draws on common industry practice and on open reference ladders, and every descriptor is original text. Replace every [bracketed] value and every row marked Example. Employment, pay-equity and anti-discrimination rules differ by country: this is a documentation format, not legal advice.

Document control

Approvals

Revision history

Contents

1. Purpose, principles and scope
2. Roles and responsibilities
3. Tracks and levels
4. Competency areas
5. Behaviour descriptors per level
6. Expectations matrix
7. Promotion process and evidence
8. Calibration
9. Level-change rules
10. Fairness and bias checks
11. Using the ladder day to day
12. Review cadence and change control
13. Glossary and references

1. Purpose, principles and scope

1.1 Purpose

This ladder gives every engineer and manager at [Organisation name] a shared, written answer to three questions: what is expected at my level, what does the next level look like, and how is a level decision made. It is the single reference for hiring levels, promotion decisions, development conversations and the mapping to pay bands.

1.2 Principles

1.3 Scope

The ladder applies to the roles listed in Document control. Specialist families (for example data engineering, site reliability, security engineering) use the same levels and competency areas and may add a short family supplement with domain examples. A supplement may add examples; it must not change level definitions.

1.4 What the ladder does not do

• It does not set pay. Each level maps to a pay band owned by People; the band document is linked in Document control.
• It does not rate annual performance. Performance is rated against the expectations of the current level (section 11.2).
• It does not guarantee a promotion timetable. Time in level is an observation, never a criterion (section 9.1).

2. Roles and responsibilities

R = Responsible, A = Accountable, C = Consulted, I = Informed.

Promotion committee. Three to five people at least one level above the target level (for L6 and L7 cases: at the target level or above, including the CTO or M6 and above leaders), from at least two teams, with at most one person from the candidate's reporting line. At least one member has completed the bias-awareness briefing in the current year.

Calibration facilitator. A trained manager or People partner who does not manage anyone being calibrated in that session. The facilitator owns the timebox, the evidence rules and the decision log.

3. Tracks and levels

3.1 Track structure

The manager track starts at M3, aligned in scope and pay band with L3. A switch between tracks keeps the same level number where scope matches (section 9.4).

3.2 Level summary, IC track

Career level. L3 is the career level: an engineer may stay at L3 for their whole career with full performance ratings. Promotion beyond L3 depends on business need for larger scope as well as on the person's growth.

3.3 Level summary, manager track

Span figures are Example values for orientation; level depends on scope and complexity, not headcount alone.

3.4 Worked example: Corvid Commerce level distribution

Example for the fictional SaaS company Corvid Commerce, IC track only. Use your own distribution as a health signal (a pyramid that is very top-heavy often means level inflation), never as a quota.

4. Competency areas

Weighting by track. All six areas apply to both tracks. For the manager track, CMP-05 expands to include people management (hiring, performance, career growth, team health) and becomes the primary area; CMP-01 shifts from personal output to the quality of technical decisions the team makes.

5. Behaviour descriptors per level

Descriptors are cumulative: a person at L4 also shows the L3 behaviours. Read each row as "consistently, over the review period".

5.1 CMP-01 Technical skill

5.2 CMP-02 Delivery

5.3 CMP-03 Impact and scope

5.4 CMP-04 Collaboration and communication

5.5 CMP-05 Leadership and mentoring

5.6 CMP-06 Operational and security ownership

5.7 Manager track descriptors

Managers are assessed on all six areas. The table below states what changes for the manager track; other descriptors apply at the equivalent IC level.

6. Expectations matrix

6.1 Rating vocabulary

6.2 Minimum profile per level

The table shows the profile a person needs to hold a level. To be promoted to a level, the person shows that level's profile, with evidence, before the promotion (section 7.3).

The "Allowed Developing" row counts the areas rated Developing in the same column: for example L3 allows one, which is CMP-05. Primary areas carry most weight in calibration when evidence is mixed.

6.3 Archetypes for L4 and above

Senior IC roles take different shapes. Calibrate against the archetype the person actually plays, with the same level bar.

7. Promotion process and evidence

7.1 Cycle

Promotions run [twice a year] on a fixed calendar published at the start of the year. Out-of-cycle promotions are limited to the cases in section 9.3.

7.2 Nomination

• Managers must review every direct report against the next level once per cycle and record "nominate", "not yet, with gaps" or "not seeking" after talking with the person.
• Engineers may self-nominate. A self-nomination is reviewed by the committee even if the manager disagrees; the manager then adds a written view.
• Skip-level managers should check that nomination rates do not differ unexplained between teams.

7.3 Evidence rules

7.4 Worked example: evidence map

7.5 Communicating outcomes

Communicate every outcome in a live conversation first, then in writing within [five working days]. A "not yet" outcome must include the specific gaps by competency ID, with examples of evidence that would close them, so the next growth plan starts from facts.

7.6 Appeals

A candidate may appeal within [15 working days] on process grounds (a rule in this ladder was not followed, evidence was ignored or misread). The People partner runs the appeal with a reviewer who was not on the committee. The appeal outcome is final for the cycle.

8. Calibration

8.1 Purpose and inputs

Calibration compares level decisions across teams so that evidence of the same strength leads to the same outcome. Inputs are the packets, the committee recommendations and the expectations matrix. Ratings from performance reviews are not inputs to level decisions.

8.2 Session rules

1. The facilitator restates the level bar and the evidence rules before discussing any case.
2. Cases are discussed in random order, not grouped by team or by manager seniority.
3. The committee lead summarises each case in two minutes; the manager adds facts only, then leaves the advocacy to the evidence.
4. Discussion refers to competency IDs and artefacts. Statements about personality, "presence", availability outside working hours or likeability are stopped by the facilitator.
5. Each case ends with a decision (promote / not yet) and a one-line rationale in the decision log, with dissent recorded.
6. At the end, the group reviews the decisions together for consistency: compare similar cases side by side.
7. Distributions are reviewed for anomalies (section 10). There is no forced distribution or quota.

8.3 Decision log fields

9. Level-change rules

9.1 Promotion

• Promotion is one level at a time. Skipping a level is not allowed.
• There is no minimum time in level. Time in level is reported for fairness monitoring only.
• Promotion recognises demonstrated performance at the next level; it is not used to retain someone who has an outside offer unless the evidence already meets the bar.

9.2 Hiring level

New hires are levelled using the interview evidence and the Technical Interview Rubric (career/technical-interview-rubric). Years of experience inform but never decide the level. If evidence is borderline, hire at the lower level and state in the offer the evidence that would support an early review at the first cycle.

9.3 Out-of-cycle changes

Allowed only when the scope of the role changes materially and immediately (for example, a new team is formed and the person leads it). The committee reviews the case with the same evidence rules.

9.4 Track switch

9.5 Re-levelling down

Re-levelling to a lower level happens only by mutual agreement (for example a request to reduce scope) or after a documented performance process run by People under local employment law. It is never a calibration outcome by itself. Pay protection rules are set in the pay band document.

9.6 Family supplements and specialists

Specialist families (SRE, security, data) use the same level numbers. A specialist at L4 is held to the same scope bar as any L4.

10. Fairness and bias checks

10.1 Process controls

10.2 Outcome metrics

The impact ratio threshold mirrors the four-fifths guideline used in US employment selection monitoring (29 CFR Part 1607, section 1607.4). It is a screening signal for investigation, not a legal test or a target. In small groups, ratios swing widely; look at several cycles together and seek specialist advice before drawing conclusions. As of October 2026 the EEOC has announced plans to rescind the Uniform Guidelines, and a June 2026 US Department of Justice opinion questions parts of them; they remain codified, and Title VII disparate-impact claims remain available to private plaintiffs. Check their current status before relying on them. The screening check stays useful whatever their status, because unexplained gaps in outcomes are a ladder-quality problem as well as a legal one.

EU pay transparency. Where the ladder maps to pay bands, it is also the main evidence for the pay-progression transparency duty in the EU Pay Transparency Directive (Directive (EU) 2023/970, Article 6): employers make the criteria used for pay, pay levels and pay progression easily accessible to workers, and those criteria are objective and gender-neutral. Member States may exempt employers with fewer than 50 workers from the pay-progression part. The transposition deadline was 7 June 2026 and national laws differ in timing and detail; check the national law that applies to you.

10.3 Data handling

Process demographic data only where local law allows, on a stated lawful basis (under the GDPR, also an Article 9(2) condition for special-category data; in the UK, the equality-of-opportunity monitoring condition in DPA 2018 Schedule 1 paragraph 8), with access limited to the People team, and report aggregates only (suppress any group smaller than [five] people).

10.4 Worked example

Example: Group B's ratio (12.0 / 20.0 = 0.60) is below 0.8, so the People partner reviews nomination rates and stretch-work allocation for Group B and reports findings to the Head of Engineering before the next cycle.

11. Using the ladder day to day

11.1 Growth conversations

Managers hold a growth conversation at least [quarterly]: pick one or two competency areas, agree concrete opportunities (a project, a review role, an incident lead), and record evidence as it happens in a Brag Document (career/brag-document).

11.2 Performance reviews

Performance reviews (career/performance-review) rate results against the current level's expectations. A high performance rating does not by itself mean readiness for the next level, and a promotion does not require a top performance rating.

11.3 Hiring and onboarding

Job descriptions (career/job-description) quote the level summary and the primary areas. New hires receive the ladder in their first week, and the 90-Day Plan (career/ninety-day-plan) and Onboarding Guide (dev/onboarding-guide) set first goals against current-level descriptors.

11.4 Links to other programmes

• Security champions (security/security-champions-program): count champion work as CMP-06 and CMP-05 evidence.
• Engineering strategy (dev/engineering-strategy): staff-level roles should map to strategic problems named there.
• Delivery and developer experience data (dev/delivery-performance-report, dev/developer-experience-survey): team-level signals; never use them to rate an individual.

12. Review cadence and change control

Change rules.

1. Changes are proposed as change requests (LAD-CHG-NNN) with the reason and the affected IDs.
2. Material changes (level definitions, matrix, process rules) take effect at the start of a cycle, never during one, and are announced at least [one cycle] ahead.
3. Candidates in an open cycle are assessed against the version that was effective when the cycle opened.
4. Keep competency and level IDs stable; retire an ID rather than reuse it.

Health metrics for the ladder. Track the share of "not yet" outcomes later overturned on appeal, calibration changes to committee recommendations, and survey clarity scores; rising numbers show the descriptors need work.

13. Glossary and references

13.1 Glossary

13.2 References

Standard and licence note

Structure aligned with common industry practice for engineering career frameworks, with inspiration from the open Engineering Ladders project by Jorge Fioranelli (Apache-2.0). No text, table or level wording is copied from that project or from any other ladder; all descriptors are original text written for this collection. Fairness monitoring references the Uniform Guidelines on Employee Selection Procedures (29 CFR Part 1607, a US government publication, whose rescission the EEOC has announced it plans), the EU Pay Transparency Directive (Directive (EU) 2023/970) and UK Acas guidance for context only; check the current official versions and the law that applies to your organisation before use. This is a documentation format, not legal advice. Template licence: MIT.