Job Titles Have Stopped Describing Engineering Scope

In the searches we run, we've stopped trusting job titles as a signal of scope, and we'd suggest hiring managers do the same. A "Senior Project Engineer" at one firm owns budget, schedule, and client relationships. At another, it's a technical execution role with no commercial exposure at all. Same title, functionally different job.

Where the drift came from

Some of this is title inflation used as a cheap retention tool - promoting someone's title without changing their compensation or scope. Some of it is companies borrowing titles from tech and finance to sound more competitive in a tight labor market, without those titles mapping to any consistent structure in engineering. Whatever the cause, the effect is the same: the title on a resume tells you almost nothing reliable about what a person actually did.

What we see when we screen against titles alone

• Candidates who were titled "Lead Engineer" but never had approval authority on a design decision.
• Candidates titled "Engineer I" who were, in practice, running site coordination for multi-discipline crews.
• Job descriptions that copy a competitor's title verbatim without adjusting the responsibilities to match.

What actually predicts fit

Scope of decision authority, the size and complexity of what was designed or delivered, and the standards or codes worked under tell you more than any title. A hiring manager comparing two "Project Engineers" should be asking who signed off on the drawings, who owned the client relationship during scope changes, and what happened when the schedule slipped - not comparing titles side by side.

What this means for job postings

If you're writing a requisition, the title is the least useful part of it. We'd rather see three sentences on what the person will actually be accountable for in the first six months than a title pulled from a competitor's org chart. Candidates read postings the same way we screen them - the accountable sentence, not the label, is what tells them whether the job matches what they're looking for.

Why this matters more now

As engineering roles blend design, field, and project-management responsibilities more than they used to, a single title increasingly can't carry the weight of describing the job. Firms that keep writing postings as if titles are self-explanatory are filtering out qualified candidates who read the title, assume it doesn't match their background, and never apply.