RecruitLingo

What the level actually means — scope, blast radius, and how to tell.

Junior / Entry-Level Engineer

Also seen as: Software Engineer I, SDE I, L3, IC1, Associate Engineer, Graduate Engineer

Scope

A well-defined task inside a system someone else designed. The work arrives already broken down.

Blast radius

A single feature or endpoint. Mistakes are caught in code review or staging, and the team expects to catch them.

Autonomy

Needs the problem framed and the approach sanity-checked. Will finish the task; won't reliably notice that it was the wrong task.

With other people

Receives review. Asks questions about how, not usually about why.

Resume tells

  • Describes features implemented, not decisions made
  • Tooling and language lists are longer than the outcomes list
  • Internships, bootcamp projects, or coursework carrying real weight
  • 'Worked on' and 'assisted with' rather than 'owned' or 'led' — though see the note on under-selling below

Title inflation risk

This level now fails in both directions, and resume polish no longer tells you which one you're looking at. UNDER-SELLING: strong juniors describe team wins in the passive voice and list tools instead of outcomes — common among self-taught candidates, non-native English speakers, and anyone who hasn't been coached. OVER-SELLING: AI-assisted writing has made junior resumes read fluent and achievement-shaped regardless of what sits underneath. Both are now routine, so judge on specifics rather than on how well the resume is written.

Calibration questions

  • “Walk me through something you built end to end. What parts did you decide, and what was decided for you?”
  • “You've written that you 'improved' or 'optimised' something — what was it before, what is it now, and how do you know?”
  • “Tell me about a time your code review got substantial feedback. What changed in how you write code afterwards?”

Where this goes wrong

The screen goes wrong in whichever direction the recruiter isn't watching for. A thin resume gets rejected when the person is genuinely strong; a polished one gets advanced when it dissolves under a single 'what did YOU decide?' question. One follow-up asking for specifics separates them, and it works on both.

Years of experience: 0-2 years, though this is the one level where years roughly track reality — mostly because there hasn't been time for the range to widen yet.

Where was the title earned?

The same title means different things at different companies. Apply this before believing the level on a resume.

Seed / early startup (under ~50 people)

Titles are recruiting currency and cost nothing to give. 'Senior' often means 'third engineer hired'. Scope can genuinely be large — they may have built whole systems alone — but calibration against a wider bar has never happened.

“How many engineers were at the company when you joined, and when you left?”

Growth-stage (~50-500 people)

The ladder is usually being invented while people are on it. Titles are often regularised in a single re-levelling event, so the same person can be Mid one quarter and Senior the next without the job changing.

“Was there a re-levelling or a formal promotion process, and where did you land in it?”

Large tech company with a calibrated ladder

Titles mean something specific and were defended in a promotion committee. A Senior here has been measured against a written bar. This is the most reliable title signal you'll get — and the reason level codes (L5, IC3) are worth asking for.

“What level were you at, in your company's internal terms, and when were you last promoted?”

Agency, consultancy or outsourcing firm

Titles are often client-facing and inflate to justify billing rates. Scope tends to be broad but shallow — many projects, rarely owning anything after handover. The 'operate it after launch' evidence that separates Senior from Mid is frequently missing, through no fault of theirs.

“Which of those projects did you stay on after go-live, and what did you have to fix?”

Non-tech company (bank, retailer, manufacturer, public sector)

Ladders are often HR-wide rather than engineering-specific, and titles can be tied to tenure or grade rather than scope. Deep domain expertise is common; exposure to modern tooling and fast release cycles may not be.

“How often did your team release, and who decided when something shipped?”

The levels either side

Individual contributor track

Management track

Open the full tool for the glossary, role profiles, and the JD decoder.