You’re getting interviews. You’re just getting them one level below the senior role you actually want.
The fix isn’t more experience. It’s proving you did the work at the target level, not just that you did the work.
That distinction sounds small, but it decides the outcome. When someone has the background for a senior role and keeps getting routed to the tier underneath it, their resume and their stories are describing tasks they completed instead of scope they owned. Those are two different claims, and most candidates only make the first one.
The question behind every senior interview
When I score a mock interview, I’m tracking three things: delivery, content, and appropriateness. Delivery is how it was said. Content is the substance. Appropriateness is the one that quietly kills strong candidates, and it comes down to a single question:
Are you telling me you did this job, or that you did your jobs?
Those aren’t the same claim. Plenty of people can prove they were in the room for important work. Far fewer prove they were the one steering it. Companies aren’t being coy about this, either. SHRM defines job leveling as the process that establishes a job’s “duties, responsibilities, tasks and level of authority within the organization’s job hierarchy”. Authority sits right there in the definition. So when your story leaves your authority ambiguous, you haven’t just been vague. You’ve answered the leveling question, and you answered it low.
This is also why the rejection feels so confusing. They didn’t pass on you because you can’t do the job. They passed because the hire felt risky at that level, and the cheapest way for a hiring manager to settle that doubt is to slot you where the evidence is obvious.
Four signals that set your level before you say a word
Signal 1: Who found the problem
Here’s a diagnostic I use in story calls: are you House, or the admitting nurse? The nurse sees the obvious symptom and writes it down. House asks why, runs the tests, and names the actual disease. If your story opens with “my VP asked me to reduce churn,” you’ve cast yourself as the nurse. However, if it opens with “churn looked flat, so I broke it out by cohort and found we were losing enterprise accounts in month four,” you’re the diagnostician. Same project. Different level.
Signal 2: Who made the call
Senior work involves decisions that could have gone the other way. So name the fork. What were the two or three options, what did you pick, and what did you give up to pick it? Candidates who skip the tradeoff sound like they executed someone else’s plan, because that’s exactly how it reads.
Signal 3: How far the consequences traveled
A level is largely a measure of blast radius. Did the outcome move your team, your function, or the company’s numbers? Be specific about where it landed. But don’t confuse blast radius with headcount. “I got buy-in from 20 people across four management chains” reads as bureaucracy at a startup, not influence.
Signal 4: Theory or memory
This is the fastest tell. Junior candidates lecture: “of course you need to consider the compliance implications.” Senior candidates remember: “I flagged the compliance risk in week two, so we ran legal review in parallel with the build.” Lived theory beats theory. One sounds like someone who read about the job. The other sounds like someone who’s held it.
How to position yourself for a senior role on paper
Someone reads your resume before any of this comes up, so start there.
Match your most recent title to the target title. In my experience it’s the single biggest predictor of whether you get the interview at all. Recruiters pattern-match on titles, and a mismatch does the sorting for them. If the work you actually did was technical program management and your company called it something else, describe the work accurately. That isn’t inflation – it’s removing a translation step nobody else is going to do for you.
Rewrite your verbs from execution to ownership. Look at how the government’s own occupational database describes a technology management role. O*NET’s task list leads with “direct daily operations,” “establish priorities,” “develop standards,” and “assign and review the work of systems analysts, programmers, and other computer-related workers.” None of those are completion verbs. As a result, if your bullets run on “supported,” “assisted,” “participated in,” and “helped,” you’re describing the level below the one you want, whatever the header says.
Cut the words that hand back your ownership. “Helped drive.” “Was part of.” “Contributed to.” Each one returns the credit you’re trying to claim.
One caution, though, because this cuts both ways. O*NET classifies these management roles as Job Zone Four, “considerable preparation needed,” which is the polite way of saying employers expect you to have already done a version of the job. Claiming a level your stories can’t defend is how a promising candidate turns into an obvious no.
What changes in the room
Your materials get you the conversation. The room decides whether you get the senior role.
Lead with the decision, not the context. Most candidates burn the bulk of the answer setting the stage and a few seconds on the call they made. Flip that ratio.
Ask a clarifying question before you answer an ambiguous behavioral prompt. For example: “Do you want one I turned around, or one that didn’t go well?” It breaks the ask-answer rhythm, and it reads as command of the room, which is itself a level signal.
Calibrate your failure story. A junior lesson is “I should have asked for help sooner.” A senior lesson is “I should have pressure-tested that assumption with legal before we scoped the build.” The specificity of the lesson is the proof of seniority.
Finally, don’t raise the level gap yourself. If the interviewer hasn’t mentioned it, it doesn’t exist in the room. Unsolicited acknowledgment of awkwardness creates awkwardness. That applies to how you open, too. Your opening should sound like someone who already holds the job.
Quick answers
How do I know if I’m being under-leveled or genuinely not ready?
Look at where you lose. If you reach final rounds and finish second, it’s positioning. If you get screened out before a human reads anything, it’s usually materials or targeting. The five pillars diagnostic will tell you which one is leaking.
Should I apply for the senior role or the one below it?
Apply to the level your stories can defend, then fix the stories and move up. Applying down to “get a foot in the door” reads as flight risk, and hiring teams screen for it.
Does restating my title count as lying?
Describing the work you actually performed isn’t lying. Claiming scope you never held is. The test: could you defend every line of it for 20 minutes under questioning?
How long does this take to fix?
Rewriting three or four core stories with the level signals in them is usually a week of real work, not a quarter. I’ve placed 250+ mid-career tech professionals, and in my experience repositioning moves faster than people expect. Deciding to start is the part that takes months.
What to do next
If you want to find out which part of your search is actually leaking, take the RHINO quiz. Five minutes, no email required.
If you want to get sharper at spotting the level a posting is really written for, read How to Read a Job Description: What’s Real, What’s Not next.
If you’d rather have someone read your stories and tell you exactly where they drop a level, book a free strategy call.