A Senior Title Isn't Senior Work: Check Level Before You Present

Titles inflate. A "Senior Engineer" at a ten-person startup and at a large bank can be very different jobs. Years of experience don't settle it either: someone can repeat their first year ten times.

For an agency, getting level wrong is expensive. Present a mid-level candidate as senior and the client finds out in the first technical question. After that, they read your next submission with doubt.

Level is about the depth of the work

When we built level checks into TrueScreenHR job links, we set one rule: level describes the depth of the person's own work. Not their title, not their years, and not whether they managed people.

• Scope: did they work on a piece of it, or own the whole thing?
• Decisions: can they explain why they chose one approach over another?
• Trade-offs and failures: what went wrong, and what they changed afterwards.
• Ambiguity: what they did when the requirements weren't clear.

How the level read works

When you create a job, you set its level (Junior, Mid-level, Senior or Lead / Principal) and an optional years range. The questions are pitched at that level. After the interview, each applicant gets a level fit of below, at or above, with one sentence on why. It's judged only from the answers, never from years, job titles or age.

Years tell you how long. Answers tell you how deep.

Credentials are different. A certification or license needs to be verified separately: the interview shows how someone applies the knowledge, not whether they hold the credential.