I never applied for the last job I had. I was a PM going after a Director-level CX role, a stretch role no resume screener was ever going to approve.
A stretch role almost never survives the resume screen, because the screener won’t do the math on why your experience transfers. So you skip the application, get into a conversation, and hand the hiring manager the pieces so they draw the conclusion themselves. Here’s how I did it, and how I coach clients to do the same.
Why a stretch role dies at the resume screen
Recruiters spend about seven seconds on a first pass, per Ladders’ eye-tracking study. In that window they read your current title, your current company, and the dates. That’s it. So if your title says “Senior PM” and the req says “Director,” the screener sees a mismatch, not a story. They aren’t paid to figure out why your experience transfers. They’re paid to find the obvious match and move on.
Here’s the thing: a resume makes them do the math on you. When the answer isn’t obvious in seven seconds, the answer is no.
I’ve been the one screening those resumes. I know how fast a stretch candidate gets binned, and it isn’t personal. It’s risk. Every dimension where you deviate from the mental model of the hire is a pivot point: level, function, company size, industry. One pivot point is a minor risk. Stack three and you’re the candidate who gets the “we went with someone more closely aligned” email. A stretch role is a level pivot by definition, and a title change like PM to Director CX adds a function pivot on top. That’s why getting rejected is usually about risk, not skill.
First, do the math on yourself
Before you chase a stretch role, check whether it’s actually a stretch. In my practice, most people who tell me “I think I’m a stretch for this” already have most of the requirements. The real gap is that they don’t understand what the role is for, so they can’t see their own overlap.
Run this exercise. Print the job description. Next to every requirement, mark one of three things:
- Done it, same title. You held the title and did the work.
- Done it, different title. You did the work under a different title, or in a different job.
- Haven’t done it. No version of this exists in your history.
Now count. If the “haven’t” column is under a third of the list, you’re not a unicorn, but you’re a rhinoceros: you’ve got the horn, the legs, and the tail. A hiring manager can look at that and recognize most of what they need. That’s a stretch worth making.
If the “haven’t” column is over half, that’s not a stretch. That’s a career change, and it needs a different playbook. Don’t dress a five-pivot move up as a one-pivot move; the interview loop will find the gap and you’ll burn a target company you can’t get back.
Hand them the pieces, don’t draw the picture
Once you know your overlap, the instinct is to explain it. “I’ve never been a director, but I’m a fast learner and I adapt quickly.” Stop. That sentence draws the rhino for them. It flags the exact difference you wanted them to overlook, and then it asks for ramp time the other candidate isn’t asking for.
Instead, hand them the dots and let them draw the unicorn. For a PM going after a Director CX role, the three pieces look like this:
- The level piece: a time you ran the team, the budget, or the escalation, whatever your title said.
- The function piece: the customer metrics the role owns, and the time you owned them under a different title.
- The stage piece: proof you’ve done both at a company their size, in their kind of market.
Notice what’s missing. You never say “even though I wasn’t a director.” You never say the three pieces came from two different jobs. They don’t need to know you’ve done all of it at one time. They need to know you can do all of it. Hiring managers hire the highest floor, not the highest ceiling, so the pieces you hand over should prove the floor: day two, you’re already operating.
And if they ask straight out whether you’ve held the title? Answer straight. Skirting too far becomes lying. “No, not the title. Here’s the work.” Then the three pieces again.
Get into the conversation before the posting exists
The pieces only travel in conversation. A resume can’t carry them, because it can’t answer the follow-up question. So the move is to network in, and to do it before the req goes public, when the manager is still forming their mental model of the hire.
The data backs this up. In Ashby’s analysis of 38 million applications, referred candidates went from application to interview 40% of the time. Cold inbound applicants: 3%. For a stretch candidate the gap is wider still, because the referral is the only thing that turns your resume from a math problem into an answer someone already checked.
Here are the six moves, in order:
- Build the list first. Twenty to thirty companies that hire your stretch title at your company size. The posting is a lagging indicator; by the time it’s live, the manager already has a shortlist in their head.
- Start with a team member, not the hiring manager. Team members have no authority to hire, so they have no reason to perform. What they do have is a strong opinion about who joins the team, and a desk to put your resume on.
- Talk to the person who just left. Search your network for someone who left that team in the last few months. They know why the role is open and they’re free to say so.
- Warm up before you ask. Two weeks of real comments on their posts, then a connection request with a note. In my own tracking of about 240 requests, connections made with a note replied about 25% of the time; connections made without one replied almost never. The note is the whole game.
- Ask for 15 minutes about the work, and nothing else. “I’d like to understand what your team is solving this year” gets a yes. “Can you refer me” gets a maybe, then silence.
- In the room, run the 30-second version. Three pieces, then one question: “What does the person who’s crushing this role six months in look like?” Their answer tells you which pieces to lead with next time. Then let them offer the referral. They usually do.
That last move is the whole point. You’ve handed over the context your resume can’t carry, and the person you handed it to is now the one doing the math, in your favor, in a meeting you’re not in.
What it looked like when it worked
I never sent an application for that Director role. I made sure there wasn’t one. I networked in, had the conversation, and handed over the context my resume couldn’t carry: what I’d run, what I’d owned, and where. By the time the interviews happened, nobody in the loop was doing the math on me. They already had the answer. That’s why tech leaders who still use LinkedIn as a job board keep losing stretch roles to candidates who were in the room first.
Frequently asked questions
Should you apply for a stretch role at all? One or two pivot points, yes. Four or five, no. That’s a career change wearing a stretch’s clothes.
What do you say about the experience you don’t have? Answer it straight, then hand over the three pieces you do have. Never volunteer the gap, and never patch it with “I’m a fast learner.”
What to do next
If you want to know what the resume-screen losses are costing you each month, run the job search cost assessment. Ninety seconds, and it shows you which stage of your search is bleeding the most.
If getting into the conversation before the posting is the part you want to get better at, read Reverse Job Search: Find the Humans Behind the Posting next. It walks through finding the exact team, manager, and recent leaver for any role.
If you’d rather have someone count your pivot points with you and tell you which stretch is worth making, book a free strategy call.