A "Senior Developer" at a 12-person startup might mean the most experienced engineer on the team, running architecture decisions solo. A "Senior Developer" at a company with a mature leveling system might sit two full rungs below Staff, with a well-defined and fairly narrow scope. Same title, genuinely different jobs — and often, genuinely different pay.

Why titles drift

Small companies tend to inflate titles because they don't have many rungs on the ladder to offer instead — "Senior" becomes the ceiling, handed out for tenure or for lack of a better title to give someone good. Large companies with formal leveling systems tend to be stingier with senior titles because the title change usually triggers a real pay-band jump, so it's gated by a formal review process. Neither company is being dishonest; they're just using different systems.

What to check instead of the title

The practical impact on your next move

If you're "Senior" at a small company and interviewing at a company with a strict leveling ladder, don't assume the title transfers directly. Come prepared to describe your actual scope — team size, decision authority, systems you owned end-to-end — because that's what the interviewer will map onto their own ladder, title or no title.

Conversely, if you're being recruited away from a big company with a rigid ladder, a startup title bump ("we'll call you Staff") is worth less than it sounds unless it comes with real scope change. Ask what specifically is different about your day-to-day, not just what's printed on the offer letter.

The takeaway

Titles are a compression of a much richer reality — team size, decision rights, blast radius of your mistakes, and who reviews your work. When comparing two offers, compare those things directly instead of trusting the label to do the translation for you.