What the level actually means — scope, blast radius, and how to tell.
Mid-Level Engineer
Also seen as: Software Engineer II, SDE II, L4, IC2, Engineer
Scope
A whole feature or component, including the parts nobody specified. Takes a loose problem and returns a working thing.
Blast radius
A subsystem their team owns. A bad call costs their team a sprint, not the company a quarter.
Autonomy
Give them the problem, not the solution. Will come back with questions at the right moments rather than at the end.
With other people
Gives useful code review on correctness. Not yet reliably shaping other people's designs.
Resume tells
Owns a named component or service, not just tickets in one
Can describe a trade-off they chose and what it cost them
Mentions on-call, production debugging, or a real incident
Shipped something that outlived a reorg or a rewrite
Title inflation risk
The most commonly skipped level. Small companies jump people straight from Junior to Senior because there's no rung in between on the org chart, so a 'Senior' from a 30-person startup is very often a strong Mid.
Calibration questions
“Tell me about a feature you owned from an unclear request through to production. Where did the requirements change under you?”
“What's something you built that you'd design differently now, and what did the current design cost the team?”
Where this goes wrong
Hired as Senior because the title matched, then struggling with ambiguity and cross-team work. The cost is slow and lands on the hiring manager three to six months in, long after the placement looked successful — which is why this mis-level so rarely gets traced back to the screen that caused it.
Years of experience: 2-5 years, but this is where the range starts to lie. Someone with 8 years of repeating the same year is still here.
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?”