RecruitLingo

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

Principal / Distinguished Engineer

Also seen as: L7, L8, IC5, IC6, Fellow, Distinguished Engineer, Chief Architect

Scope

Company-wide technical direction, or a domain the company's business depends on. Often the person who decides which bets are technically viable.

Blast radius

Existential in the extreme cases. Getting the technical strategy wrong at this level can cost a company a market.

Autonomy

Sets direction rather than receiving it. Frequently reports into or advises the executive layer.

With other people

Operates through other Staff and Senior engineers. Rarely the person writing the majority of the code, and shouldn't be judged as if they were.

Resume tells

  • An externally checkable footprint IF there is one — talks, papers, patents, standards work, open source. Its absence proves nothing: regulated industries, defence and most enterprise work leave no public trace, and public output tracks free time and confidence as much as ability
  • Named as the technical authority on a system a real business depends on — this is the tell that works regardless of industry
  • Track record across multiple companies or multiple eras of one company
  • Talks in terms of bets and trade-offs at company scale, not systems

Title inflation risk

At small companies 'Principal' is sometimes just the top of a three-rung ladder and closer to Staff elsewhere. Conversely, genuine Principals sometimes have unremarkable titles at companies with flat ladders — look at what they were trusted with, not what they were called.

Calibration questions

  • “What's a technical direction you set that the company committed to? How did you know it was right, and what would have told you it was wrong?”
  • “Tell me about a bet you got wrong at scale. What did it cost, and what changed afterwards?”

Where this goes wrong

Screened on hands-on coding depth and rejected for being 'rusty'. If the role genuinely needs someone shipping code daily, this is the wrong level — that's a mismatch in the req, not a flaw in the candidate.

Years of experience: 10-15+ years in practice, but this level is defined by track record, not tenure. It's the one rung where you should expect to find named, checkable evidence.

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.