Should You Apply If You Don't Meet All the Job Requirements?

Should you apply if you don't meet all the job requirements? Usually yes, as long as the requirements you are missing are the soft kind. Most postings list everything a hiring manager could hope for, and the person they hire rarely ticks every box. The useful question is not "do I meet 100%?" but "which of these requirements actually decide who gets interviewed, and do I meet those?"

This guide gives you a quick way to sort a posting's requirements, a rule of thumb for when to apply and when to skip, and what to do about the gaps once you hit send. At the end it shows how to run the same check in Curri.

Why job postings ask for more than they need

Job seekers keep asking this question because postings are confusing on purpose and by accident. A few patterns come up again and again:

• Requirements are collected, not edited. A posting is often assembled from an old ad, a manager's wish list and a template. Nobody goes back to check whether "3+ years" makes sense for an entry-level title.
• "Required" and "preferred" get blurred. Some employers split must-haves from nice-to-haves. Many put everything in one long list.
• Employers hire from the people who apply. If nobody meets every point (which is common), the job goes to the strongest candidate in the pile. That can be you.

None of this means every requirement is fake. Some are firm, and applying without them wastes your time. The trick is telling the two apart.

Sort every requirement into three buckets

Before you decide, read the posting once and put each requirement into one of these buckets.

1. Hard gates

These are requirements the employer usually cannot waive, even for a great candidate:

• A license or certification required by law (nursing, teaching in many public schools, electrical work, accounting sign-off)
• A security clearance
• A degree needed for a work visa or a regulatory reason
• The legal right to work in that country, or a location the job truly requires

If you are missing a hard gate, skip the posting unless it says the employer will sponsor or train for it.

2. Core skills

These are the skills you would use every week in the job: the main programming language, the main tool, the type of work (sales, support, analysis, teaching). They usually show up in the job title, the first lines of the description and the "what you will do" section. Missing one core skill is common. Missing most of them means the job is a different job.

3. Nice-to-haves and wish-list items

Specific secondary tools, industry experience ("experience in healthcare a plus"), a particular framework when you know a close cousin of it, and often the exact number of years. These are where postings inflate the most, and where a strong applicant is forgiven most easily.

A simple rule for when to apply

Once the requirements are sorted, apply when all three of these are true:

1. You meet every hard gate.
2. You meet most of the core skills, and the ones you lack are close to something you already do (another SQL database, another frontend framework, another CRM).
3. The level is roughly right. Being 6 months short of "2+ years" is close. Being 1.5 years into your career and applying for a senior role that asks for 5+ years and mentoring others is a long shot, even if you know every tool.

Nice-to-haves barely matter for this decision. If you meet the first three points and none of the nice-to-haves, you are still a plausible applicant.

Two signals help with the level question. Read the responsibilities, not just the requirements: "lead", "own", "mentor" and "set direction" describe a senior role whatever the title says. And look at the salary range if there is one. A low range on a posting that asks for many years often means the employer will take someone earlier in their career.

Check whether "missing" really means missing

Many people rule themselves out for skills they actually have but never wrote down. Before you decide you don't qualify, go through the requirements you marked as missing and ask:

• Have I done this at work under a different name?
• Have I done it in a side project, a course, volunteer work or a previous field?
• Is it on my resume at all, or only in my head?

If you find evidence, add it to your resume, with a specific line that shows it. A recruiter (and an applicant tracking system) can only credit what is on the page. Our guide on quantifying resume achievements when your job has no numbers helps with writing those lines.

How to handle the gaps after you apply

On the resume: show evidence, don't apologize

Your resume does not need to point out what you lack. Lead with the requirements you meet, using the posting's own words where they are true, and put your closest adjacent experience near the top. Never add a tool, title or result you do not have. Interviews are built to find those.

In the cover letter: address one gap, briefly

If you are missing something the posting clearly marks as required, one or two sentences can help: name the gap, then point to the closest evidence. For example: "I haven't used PostgreSQL in production, but I design and query MySQL databases daily and have shipped two features that needed schema changes." That is enough. Do not write a paragraph explaining why you might not be qualified.

In the interview: be honest and specific

If they ask about a missing skill, say so plainly, then give the adjacent experience and how fast you picked up the last similar tool. "I meet most of the criteria and learn fast" is weaker than one concrete example of learning something new on the job.

Spend your effort where the odds are best

Applying to stretch roles is fine. Spending two hours tailoring a resume for every one of them is not. A practical split:

• Strong fits: tailor the resume carefully, write a cover letter if they accept one, follow up.
• Plausible fits with a gap or two: tailor the summary and top bullets, address the main gap in a sentence.
• Long shots: apply with your closest existing version, or skip.

If you are not sure how many resume versions to keep for this, see how many resume versions you need. And keep a record of which version went where, as covered in how to keep track of job applications.

Checking a job against your profile in Curri

Doing the bucket exercise by hand works, but it gets slow when you are reading twenty postings a week. Curri's Jobs For You page does a version of it for you: it finds open jobs from your profile and saved searches, and can score each one against your profile.

What a match score shows

Each scored job gets a score from 0 to 100 and a label: Strong match (80 and up), Moderate match (60 to 79) or Weak match (under 60). Open a job and the How you match panel breaks the score down:

• A one-sentence summary of the fit
• Must-have and Nice-to-have lists, with each requirement marked met or missing. Met ones quote the line of your profile that shows it; missing ones say "Not found in your profile"
• An Experience line comparing your years and level with what the job asks
• A Role line saying whether the job's main work is the kind of work you do

This maps closely onto the buckets above. Here are two jobs scored against the same demo profile, a frontend developer with about 1.5 years of professional experience.

The first is a senior role. Most must-haves are missing, and the Experience line says why it is a long shot: 1.5 years against the 5+ asked, for a senior role with mentoring.

The second is a full stack role. The frontend must-haves are met, the backend ones (Node.js, PostgreSQL) are missing, and the Experience line reads "Close to the experience asked." That is a plausible stretch: worth applying, with the backend gap addressed in a sentence and any real backend work moved up the resume.

Turn the checklist into action

• Fix what is only missing on paper. If a requirement says "Not found in your profile" but you do have the experience, add it to your profile. The score is then marked as possibly outdated ("Your profile changed since this score"), and Re-score checks the job again.
• Tailor for the ones worth it. Tailor CV writes the job onto a new or existing CV and starts the tailoring in the AI chat, where you can add your own instructions, such as "lead with my MySQL work for the database requirement."
• Filter and sort by fit. The filters include the match score tiers, and the results can be sorted by best match, so the strong and moderate jobs come first.

Every account gets 25 free scores. After that, scoring uses your credits, like the rest of Curri's AI features; see pricing for how credits work. Treat the score as a second opinion from a careful reader, not a verdict: you know things about the job and yourself that the posting does not say.

The short answer

Apply when you meet the hard gates, most of the core skills and roughly the right level. Skip when you lack a legal or clearance requirement, or when the job is several levels above you. Everything in between is a judgment call worth making quickly, so you can spend your best effort on the jobs where you are a strong applicant. To see how your profile reads against real postings, browse open roles on the job board, or start with the resume builder.