Talking About Engineering Ladders in English

An engineering ladder is a framework that defines the expectations, skills, and behaviours associated with each level of seniority in an engineering organisation. Understanding the vocabulary of engineering ladders is essential for discussing your own career growth, giving performance feedback, and having productive conversations with your manager about promotion.

Key Vocabulary

Engineering ladder An engineering ladder (also called a career ladder or levelling framework) is a structured set of criteria that defines what is expected of engineers at each seniority level, from junior to staff and beyond. Example: “Our engineering ladder describes the technical skills, communication abilities, and leadership behaviours expected at each level.”

Individual contributor (IC) An individual contributor is an engineer who contributes through their own technical work rather than through managing others. The IC track typically includes levels from junior engineer up to principal or distinguished engineer. Example: “I’ve decided to stay on the individual contributor track — I’d rather grow as a technical leader than move into people management.”

Scope of impact Scope of impact refers to how broadly an engineer’s work affects the organisation. A junior engineer’s scope might be limited to their team’s immediate tasks, while a staff engineer’s scope might span multiple teams or the entire engineering organisation. Example: “One of the key criteria for promotion to senior is demonstrating scope of impact beyond your own feature work.”

Levelling Levelling is the process of determining the appropriate seniority level for an engineer, either during hiring or as part of a promotion process. It typically involves calibration sessions where managers compare candidates against the ladder criteria. Example: “We are in the process of levelling all engineers against the new framework to ensure consistency across teams.”

Calibration A calibration session is a meeting where a group of managers or senior engineers compare performance and levelling assessments to ensure consistency and fairness across the organisation. Example: “Your promotion case will be reviewed in the calibration session next month.”

Common Scenarios Where This Language Is Used

In a one-on-one with your manager: “I’ve been looking at the engineering ladder criteria for senior engineer and I think I’m meeting most of the technical expectations. I’d like to discuss where you think my gaps are and what I should focus on over the next two quarters.”

When giving structured feedback: “Looking at the ladder criteria for your current level, I think you are consistently meeting the technical expectations. The area I’d like to see growth in is mentorship — the senior engineer level expects you to actively support the development of more junior colleagues.”

In a promotion discussion: “I’d like to put forward a case for promotion to L5. I’ve prepared some examples of how my work this year has met the criteria on the ladder. Could we schedule time to review them together before the next calibration?”

In a hiring calibration: “This candidate is strong technically, but based on their answers I’d level them at L4 rather than L5 — their scope of impact has been team-level, and the L5 criteria require demonstrated cross-team influence.”

Useful Phrases for Engineering Ladder Discussions

• “What are the key criteria I need to demonstrate to be considered for promotion?”
• “I’d like to understand which areas of the ladder I’m already meeting and where my gaps are.”
• “My impact this year has primarily been at the team level — I’m working on expanding that.”
• “The ladder describes mentorship as a core expectation at the senior level.”
• “Can you give me some concrete examples of what ‘cross-functional impact’ looks like at this company?”
• “I want to make sure my promotion case is well-evidenced — should I keep a running record of my contributions?”
• “The calibration process ensures that our levelling decisions are consistent across the organisation.”
• “I’m not looking to move into management — I want to grow on the IC track.”
• “Based on the ladder criteria, I think there’s a strong case for levelling this candidate at L4.”
• “Could you share some examples of what distinguishes an L4 from an L5 in practice at this company?”

Writing a Promotion Case in English

A promotion case is a document that presents evidence of why an engineer meets the criteria for the next level. It is one of the most important professional documents you will write in your engineering career.

Structure your promotion case around the ladder criteria, not around a chronological list of your work. For each criterion, provide one or two specific examples with measurable outcomes. Use the STAR format: Situation, Task, Action, Result.

“When the team identified performance issues in the search service (Situation), I took ownership of the investigation (Task), profiled the database queries, identified three slow queries, and rewrote them using covering indices (Action). This reduced the p99 latency from 2.1 seconds to 340ms, which resolved several customer complaints (Result).”

Avoid vague claims like “I had a significant impact on the team.” Replace them with specific, evidenced statements.

Practice Suggestion

Find your company’s engineering ladder (most are published internally; some companies like CircleCI and Rent the Runway have published theirs publicly). Read the criteria for your current level and the level above. Write three concrete examples from your recent work that demonstrate you are meeting criteria at the next level. Use the STAR format and write each example in 100-150 words of clear English. These examples will be valuable in your next performance review or promotion conversation.