Expectations by Level

Topics Covered

Why the Level Changes the Bar

Levels are defined by scope

The same signal at different heights

Why companies care so much about level

Titles do not transfer cleanly

Your current level is not your target

Reading the job description for level clues

How levels map across companies

How the bar shifts within a level

What happens when the loop disagrees about level

Level and the rest of the loop

A note on years of experience

The previous lesson showed that rubric anchors are written per level, so the same story can score a three for one candidate and a one for another. This lesson goes through what the anchors actually say at each level, from junior to principal, and how to tell whether your stories match the level you are targeting. Level is the most common reason strong engineers get disappointing outcomes in behavioral rounds. They tell good stories, but stories pitched at the level they currently hold or the level below, and the committee concludes they are not yet operating at the target.

Levels are defined by scope

Every engineering ladder, whatever its titles, is organised around scope. At the bottom, an engineer is trusted with well defined tasks. A level up, they own features. Above that, they own projects that involve several people. Higher still, they set direction across teams, and at the top they shape the technical direction of an organisation. Behavioral rounds test scope because coding and design rounds cannot. A coding round shows whether you can solve a problem in forty five minutes. Only your stories show the size of the problems you are trusted with at work and how you behave when they span many people.

Scope has several dimensions. One is the number of people your work involves, from yourself to a team to several teams. Another is time horizon, from days to quarters to years. A third is ambiguity: how much of the problem was defined for you before you started. A fourth is impact: whether the outcome mattered to a feature, a product line or the whole company. Interviewers listen for all four, and a story that is large on one dimension and small on the others is usually read at the lower level.

The same signal at different heights

Each signal from the rubric reappears at every level, but the expected height rises. Ownership at junior level means finishing your tasks and following up. At senior level it means owning an outcome across a project, including the parts no one assigned to you. At staff level it means owning a problem that spans teams, often one nobody else was willing to take. Conflict at junior level might be a disagreement with a reviewer. At staff level it might be a disagreement between two directors about the architecture of a platform, which you resolved without authority over either.

Each level up widens the scope of work along people, time, ambiguity and impact.

Why companies care so much about level

Levelling decides pay, expectations and who you work with, so companies treat it seriously. Hiring someone above their real level is expensive in two ways. They are paid more than their contribution, and they are given work they cannot yet do, which tends to fail and hurt both them and their team. Hiring someone below their level is cheaper but often leads to frustration and early departure. Committees therefore spend as much time on the level decision as on the hire decision, and the behavioral round provides most of the evidence for it.

Titles do not transfer cleanly

Titles mean different things at different companies. A senior engineer at a fifty person startup may own whole systems alone but have little experience coordinating across teams. A senior engineer at a large company may own a narrower technical area but routinely lead work across three teams. When you move between companies of different sizes, expect the committee to level you on the scope your stories demonstrate, not on your title. That is why describing scope explicitly matters so much. Without it, the committee guesses, and guesses tend to be conservative.

Your current level is not your target

Most candidates interview for the level they hold or one above. If you are interviewing for a level above your current one, your stories need to show that you already operate at the target level some of the time. Promotions at most companies work the same way: you are promoted for doing the next level of work consistently, not for doing your current level well. A candidate whose stories show only current level work is usually offered their current level, even when they interview for the next.

Reading the job description for level clues

Job descriptions often hint at the scope a role expects. Phrases such as drive technical direction across multiple teams or partner with product and design leadership describe staff scope. Phrases such as own features from design through launch describe mid level scope. Reading the description carefully and noting its scope words tells you which stories to lead with and what the committee will be looking for.

How levels map across companies

Level names vary widely. Google uses numbers from L3 for new graduates through L5 for senior and L6 for staff. Meta uses E3 through E6 and beyond. Amazon uses SDE I, II and III, with principal above. Many smaller companies use titles such as Engineer, Senior Engineer and Staff Engineer without numbers. Sites that compare compensation across companies publish rough mappings, and they are useful for orientation, but the mapping is never exact. A senior title at one company might correspond to mid level at another, especially when the companies differ greatly in size.

For behavioral preparation, the exact mapping matters less than the scope description behind each level. Ask the recruiter which level you are being considered for and, if possible, find the public ladder or a description of that level. Then prepare stories against the scope description, not the title. A story that clearly shows the scope the target level requires will be read correctly whatever the title on your resume.

How the bar shifts within a level

Levels are not single points. Within senior, for example, there is a range from engineers newly promoted, who show senior scope in some of their work, to engineers close to staff, who show it consistently and occasionally go beyond. Committees often describe candidates in these terms, such as low senior or strong senior. The distinction can affect compensation within the level, and it is driven by the same evidence: how consistently your stories show target level scope and whether any of them reach above it.

Within a level, consistency of target level stories decides whether a candidate reads as low, solid or strong.

What happens when the loop disagrees about level

Interviewers sometimes disagree about level as well as hire. One write up might describe strong senior evidence while another describes mid level evidence on the same signal. Committees resolve this by reading the specific stories behind each view. If the senior evidence came from one story told well and the mid level evidence came from several, the committee will usually level conservatively. Having several stories at target level, rather than one excellent one, is the most reliable way to avoid a split.

Level and the rest of the loop

The behavioral round is not the only source of level evidence. System design rounds show the scale of systems you can reason about, and coding rounds show fluency. Committees combine all of them. A candidate with strong senior design evidence but mid level behavioral stories often receives a split read and, more often than not, the lower level. Behavioral evidence tends to carry extra weight on level because it is the only part of the loop that reflects what you actually do at work over months, rather than what you can do in an hour.

A note on years of experience

Years of experience correlate with level but do not determine it. Some engineers reach senior scope in four years, others take ten, and some excellent engineers prefer to stay at a level where they can focus on deep individual work. Committees do not level on years. They level on evidence, which is why a candidate with fewer years but strong scope stories can receive a higher offer than one with more years and narrower stories.

Level is scope

Levels are defined by scope along four dimensions: people involved, time horizon, ambiguity and impact. Every signal reappears at every level with a higher expected height. Committees level on demonstrated scope, not titles, so stories need to show work at the target level.