Senior Engineering Manager

Also seen as: Senior EM, M2, Group Engineering Manager, Manager of Managers, Head of (small companies)

Resume tells

Managed managers, not only engineers — say so explicitly if it's true
Made an org-design decision: split a team, merged two, changed who owned what, and can explain why
Owned headcount planning or a budget
Ran something cross-functional where they had no authority over half the people involved

Title inflation risk

At companies under a few hundred people, 'Senior EM' or 'Head of Engineering' is frequently the same job as EM elsewhere. Also watch for 'managed three teams' that turns out to mean three people working on three things. Ask for the headcount underneath them and how many layers.

Calibration questions

“How many people were under you in total, and how many layers?”
“Tell me about a time you changed how the teams were organised. What prompted it, and what did it break?”
“How did you coach a manager who was struggling? What specifically did you change in how they worked?”

Where this goes wrong

Confused with Director, especially at smaller companies where the titles overlap completely. The practical difference is whether they set the direction or execute against someone else's. Ask who decided what their org worked on.

Years of experience: Usually 2-4 years managing before this, but the meaningful question is whether they've managed managers, which is a genuinely different job from managing engineers.

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.

RecruitLingo