How to apply for a job when you don't meet all the requirements

Every job posting reads like a wish list. Ten years of a language that has existed for six. A degree in a field the person doing the job doesn't have themselves. A stack of tools that changes twice a year. Read enough of them and it stops feeling like a description of a job and starts feeling like a polite way to tell you not to apply.

Don't take the hint. I've changed industries three times — heavy civil construction to project management to robotics — and every one of those moves started with a job I wasn't technically qualified for. Same for a lot of the people I've hired and worked with. The postings aren't lying, exactly. They're describing the perfect candidate, who almost never applies. The real question isn't whether you meet every bullet. It's whether you meet enough of the ones that actually matter, and whether your résumé says so plainly.

Here's the rule I use, and what I write when the answer is "close enough."

The 60% rule (and the two must-haves you don't skip)

The number that comes up over and over, from LinkedIn's own research and plenty of hiring managers I've talked to, is around 60%. If you meet roughly 60% of the requirements — and both of the must-haves I'll get to in a second — you're inside the range where an application makes sense. Under that, it's usually a stretch not worth the hours; over that, you're already one of the more qualified people in the pile.

There's a piece of that same research that gets quoted a lot: women often wait until they meet 100% of the listed requirements before they apply, while men apply at around 60%. Take from that what you will, but the practical lesson is the same for anyone: the person you're competing against isn't waiting for a perfect match. Don't hand them the seat by refusing to sit down.

The two must-haves that are not optional:

• Legal ability to do the job where the job is. Work authorization, licenses that take months or years to earn (a P.E., a CDL, an active FAA Part 107 for drone work, a nursing license, a specific security clearance). If a requirement takes longer to acquire than the hiring cycle, "I'll get it once hired" is not a plan. Skip.
• The one skill the job is literally about. A backend engineering role will teach you a new framework; it won't teach you to code. A CFO role will train you on their software; it won't train you on accounting. Find the central skill the job cannot exist without, and be honest with yourself about whether you have it. Everything else is negotiable.

If you clear those two, and you meet 60% of the rest? Apply. Write the résumé like you belong in the conversation, because you do.

Read the posting like a hiring manager wrote it, not a lawyer

A job description is not a legal document. It's a wish list drafted by a manager, usually in a hurry, often copied from the last person who left the role, and then padded by HR to filter volume. That means the bullets are not weighted equally. Some of them are the actual job. Some of them are habits. Some are aspirational. Your job is to tell them apart.

A trick I use: read the posting twice. First pass, star every requirement that appears in the "responsibilities" section or the first two bullets of "requirements." Those are the job. Second pass, look at everything else with a squint. If a bullet feels tacked on ("familiar with agile," "experience with Microsoft Office," "team player"), it probably is. Nobody's rejecting you over "team player." They're rejecting you over the two or three things they'll actually need on day one.

Now weigh yourself against the starred list, not the full list. It's a different picture.

Write the résumé for what they'll need on day one

Here's where most underqualified applications go wrong. They try to disguise the gap — usually with a wall of buzzwords, or by inflating a small project into a "led enterprise transformation" line. Both signals read as "this person is scared of the gap." The confident move is the opposite: acknowledge the shape of your background, then prove you can do the day-one work.

Three moves I actually use:

• Reorder the top of the résumé around the job's real focus. If the posting cares about system integration, your project bullets should lead with integration work, even if it wasn't your official title. Same job, different framing. The truth stays the truth; the emphasis follows the role.
• Translate the vocabulary. In construction, "punch list" is the exact same idea as "backlog grooming" in software — closing out the last defects before you ship. If you have the concept, use the word the field uses. Not as a costume; as a translation. Google the target field's five most common verbs and match your bullets to them.
• Show one on-your-own-time proof. A course, a certificate, a small personal project, a portfolio site, a genuine contribution to an open source repo. Not to inflate your résumé — to prove you're already moving in the direction of the role. When I switched into robotics-adjacent work, the "proof of commitment" line on my résumé was a self-paced program I did on nights and weekends, plus a stack of certifications I paid for myself. Small. But it said, out loud, that this move wasn't a whim.

If you're doing all three, you don't need to hide the gap. The résumé will read like a person moving toward the role from a real starting point — which is exactly what you are.

What to actually say about the requirement you don't have

If the missing requirement is small — a specific tool, a certification you can get in a weekend, a framework you haven't used but have used something close to — say so in one line, in the summary, and move on. Something like: "Currently earning my [X] certification; equivalent experience with [close tool]." Recruiters read those every day. They know a lot of gaps are hours, not years.

If the missing requirement is bigger, the résumé isn't the place to argue about it. The résumé is the place to make it easy for a manager to justify bringing you in for a conversation. Then, in the cover letter or the first call, you address it directly: "You're right that I haven't done exactly this — here's the closest thing I have, here's what I'd need to learn, and here's what I'd expect to be productive in." Numbers, plans, dates. That's a negotiation, not a plea.

If the missing requirement is one of the two must-haves — the legal one or the core-skill one — don't write around it. Move on. There will be another job.

When to move on (and where to point your effort instead)

Not every stretch is worth stretching for. A few signs I read as "put your hours somewhere else":

• You'd have to lie or heavily stretch to hit the top three requirements. Not "reframe" — lie. Different thing.
• The posting has been open for months and keeps re-listing. That's usually a hiring team that doesn't know what they want, or a role that churns for a reason.
• You can't picture your first ninety days. If you can't imagine what you'd actually do on Monday morning — not the title, the work — you don't have enough of the map yet. Do a smaller version of the role first.

If any of those hit, the fastest path is not another application. It's another proof point. One month of a course, one weekend project, one informational conversation with someone in the seat — any of those change what you can write next month more than another submitted résumé changes what you can write today.

The tool note

I built ResumAI partly because I got tired of hand-tailoring the same résumé for jobs I was technically underqualified for. It reads the job posting, compares it to your master résumé, and helps you emphasize the right experience for that specific role — the same reorder-the-top move I described above, just faster. Your résumé stays on your device. Personal details (email, phone, LinkedIn, current employer) are masked before any AI model ever sees them, so a search you're running quietly stays quiet.

But the tool doesn't decide whether to apply. That's still on you, and the 60%-plus-two-must-haves rule is a better filter than anything a model will give you. Meet the bar, tell the truth, aim your résumé at the day-one work, and put your name in.

Worst case, you learn something about how the target field reads applications. Best case, you get an interview for the job you thought wasn't for you.

I've been surprised at how often it's the second one.