What to Do When You're Underqualified on Paper

The standard advice, when a posting asks for things you don't have, is to apply anyway. Men apply when they meet a fraction of the listed requirements; women, on average, wait until they meet more of them; the fix everyone lands on is to just apply. That advice isn't wrong. It's also not useful by itself, because it tells you what to do with your mouse and nothing about what to do with the resume. Clicking apply on a posting you're underqualified for, with a resume that does nothing to address the gap, gets you the same outcome as not applying. The useful question isn't whether to apply. It's which requirements you're actually missing, and what to do about the ones you are.

A requirements list is not a checklist

Postings are written by whoever needed the role filled, often fast, often by combining an old job description with whatever the hiring manager said out loud in a meeting. The result reads like a checklist but functions more like a wish list with a few real constraints buried in it. Some lines are things a candidate must have on day one. Others are things the team hopes for and would be glad to get, but the role has run fine without. A posting rarely marks which is which, so the work of sorting them falls on you.

The sort isn't guesswork. Read for what would actually stop someone from doing the job versus what would just make the first few months smoother. A specific certification, a security clearance, fluency in a particular language, a tool the whole workflow depends on — those tend to be real. "Experience with cross-functional stakeholder management" attached to a role that's mostly individual contributor work is usually padding, copied from a template or a more senior version of the job. If you can picture someone doing the role well without a given line, it probably isn't a hard requirement, whatever the formatting implies.

Years of experience is the weakest line on the list

"5+ years" is doing less work than it looks like it's doing. It's a proxy for a level of judgment and independence the hiring manager wants, and proxies are what people reach for when the real thing is hard to specify in a posting. Two candidates with the same four years can be at completely different points on that curve, and a hiring manager who has actually interviewed people knows this — which is part of why a rounding-down of the years number rarely kills a candidate who is otherwise strong. Treat it as a rough signal of seniority, not a gate. The gate question is whether you can do the work the posting describes, not whether you've been paid to do adjacent work for a specific count of years.

You usually meet more of it than the resume shows

Before deciding a gap is real, check whether it's actually a gap in your experience or a gap in what you wrote down. This is the same problem a thin source profile causes everywhere: most people's resumes are a compressed, general-purpose summary, trimmed for a different audience than the one reading it now. A requirement that looks unmet might be sitting in your history under a different label, described for a different job, or left off entirely because it didn't seem worth a line at the time.

Go back through everything you've done — not just the version of it that made the last resume — and look for the specific thing the posting is asking for, described in whatever words you'd use for it, not the posting's words. This is the same exercise that makes a career change readable: the match usually exists somewhere in the record, and the job is finding it and writing it in language the reader doesn't have to translate. A surprising number of "gaps" turn out to be requirements you meet but never bothered to say.

The gaps that are real

Some of what's left after that search will still be real. You don't have the tool. You haven't led a team that size. You've done the analysis but never presented it to executives. Don't paper over these — a bullet that implies you've done something you haven't will not survive a follow-up question in an interview, and getting caught costs you more than the honest gap would have.

The move for a real gap isn't to hide it, and it isn't to lead with it either. It's to put it in the one place built to hold context a bullet point can't: the cover letter. A resume bullet has to stand alone as a fact, which means it can't explain, qualify, or make a case — that's what the cover letter is for. "I haven't managed a team of this size, but I ran point on hiring and onboarding for the three hires my last team added, and the jump from individual contributor to first-time manager is the one I'm ready to make" is a sentence a resume bullet can't say and a cover letter can. It names the gap, doesn't dress it up, and gives the reader a reason to discount it. That's a different and better outcome than hoping the gap goes unnoticed.

When it means don't apply

Sometimes the honest read is that the gap is disqualifying, not stretchable. A role that requires an active clearance, a license you don't hold, or fluency in a language you don't speak isn't asking for judgment about proxies — it's asking a yes-or-no question, usually enforced by an application-form knockout question before a human ever sees your resume. Applying anyway doesn't get you a chance to explain; it gets you an automatic no and time you didn't need to spend. The skill this whole exercise depends on is telling that kind of requirement apart from the softer, negotiable kind, so you can put your effort into the applications where a gap is actually arguable.

Most of what reads as "underqualified" on a first pass is really two smaller problems: material you have but didn't write down, and material you're missing but haven't said so out loud yet. Sorting a posting's requirements into what's load-bearing and what isn't, then finding the real matches in your history and being honest about what's left, is more work than either applying blind or not applying at all. It's also the only version that changes the outcome. That sorting is exactly what selecting from an accurate, complete record of your own history is for — not to make a gap disappear, but to make sure it's the only thing actually left unaddressed.