The Title Convergence Problem

Staff Engineer and Engineering Manager stopped being different jobs at senior levels. The things that still differ are decision authority, blast radius, and information access.

A few years ago I sat with someone over coffee who asked me a version of the question I've heard at least twenty times. "Should I go EM or Staff?" She had an offer for each, at two different companies, and she wanted the one that would set her up better for the next decade.

I used to answer that question with confidence. In 2016, I would have said something like: if you get energy from writing code and designing systems, go Staff. If you get energy from developing people and shaping teams, go EM. Pick the ladder that matches the work you actually want to do.

I don't answer it that way anymore, because the ladders have quietly converged.

Back when the dual-ladder story was clean, the two jobs looked different from ten feet away. An EM owned people, careers, and headcount. A Staff engineer owned systems, architecture, and technical direction. Pay was different. Skills ran on different tracks. The body language in a planning meeting signaled which ladder you were on. You could tell who was who without reading the org chart.

Something shifted in the last five or six years. I noticed it in offer packets first. Companies started paying Staff and EM at the same band once you got past a certain level. By 2026, compensation data from the public sites shows Staff ICs and engineering managers at top-tier tech companies landing in roughly the same total comp range at the top of the ladder. The financial signal that used to separate the two paths stopped separating them.

Then I saw it in the work itself. At a previous company, I watched a Staff engineer run what was effectively a multi-team program. She had no direct reports, but three squad leads coordinated through her. She owned the planning cadence. She wrote the roadmap. When a project slipped, she was the one explaining why to the VP. Her calendar looked exactly like an EM's calendar.

Across the same years, I watched an EM at another organization spend two days a week in code reviews, drive architecture decisions for his platform, and argue with principal engineers about service boundaries. He had eight direct reports. He also shipped code. His title said one thing; his day looked like a Staff engineer with a skip-level tax.

One pattern I had to correct in myself was assuming the title told me what someone did. Title plus company size gets you partway there. A Staff Engineer at a 200-person startup looks nothing like a Staff Engineer at a 50,000-person tech company, and most people in the industry can sketch the difference without asking. At senior levels, even that combination stops being enough. When I actually asked what people spent their time on, the picture rarely matched the stereotype the two labels suggested. "Engineering Manager" at one company looked like "Director" at another and "Team Lead" at a third, and company size didn't reliably explain the gap.

The part that hurt to watch was engineers picking the title over the work. I saw someone turn down a Staff offer at a smaller company for an EM offer at a bigger name, convinced the EM label would travel better. Two years later she called me from a role where she spent four days a week in recurring meetings and zero days doing the work she'd accepted the job for. The title traveled fine. Two years in, she was still looking for the job she'd pictured.

I saw it go the other way too. An EM at one organization moved to Staff at another because he wanted out of people management. The new role had no direct reports on paper, but he was running a cross-team initiative with four squads contributing. He was doing scope negotiation, coaching, and what was effectively performance calibration for the leads he coordinated with. Six months in, he told me he'd changed his title and his commute. The rest was the same.

At senior levels, the title has stopped being a reliable signal. What you want to evaluate instead is what differs between two roles, even when the labels match.

Start with decision authority. Who can say no and make it stick? Figure out whether this role can kill a project, block a hire, or force a re-architecture, or whether its job is to advise, recommend, and escalate. Staff and EM titles vary wildly on this axis. Some Staff roles have veto power over a platform's direction. Some EMs can't finalize a hire without three approvals above them. Ask to see a recent decision the role made that a more junior version couldn't have made. If the answer is vague, the authority is vague.

Then look at blast radius. When this role gets a decision wrong, who feels it, and for how long? One team for a quarter, or the whole platform for a year? Blast radius maps to seniority more honestly than title does. A Staff engineer whose choices break one service for a sprint is junior for the title. An EM whose staffing decisions shape an org for three years is senior, no matter what the line on the org chart says. The interview question that surfaces this is boring: "Walk me through the worst consequence of a decision this role has made in the last year." Listen for scope.

The third thing to check is who reports what to whom. The reporting line is half the answer. The information flow is the other half. Ask whether the role sits in the quarterly business review, if the weekly revenue numbers land in its inbox unfiltered, and what budget line carries its name. Information access tells you more about actual scope than the job title ever will. A Staff engineer who reads the same dashboards the VPs read has a different kind of pull than one whose numbers come filtered through two layers.

There's a reason nobody in the industry wants to talk about the convergence out loud. Recruiters need the titles to sound different so the ladders look distinct. Companies want the optionality of paying people the same without admitting they do the same work. Candidates want to believe that picking correctly matters more than it does. Everyone has a reason to keep the old story alive, so the old story keeps getting told.

If you're picking between two senior roles, stop asking which title is better for your resume. Focus on three things instead. What the role can actually decide. What breaks when the role gets a call wrong. Whose numbers it sees every Monday morning. Those answers diverge even when the titles don't.

Five years ago the labels stopped telling the truth, and nobody updated the candidates.