Should You Apply If You Don't Meet Every Requirement?

You're looking at a posting you half-match, cursor hovering over the apply button, doing math on whether it's worth it. Short version: yes, almost always apply. The real skill isn't deciding whether to submit, it's reading the posting closely enough to tell the two or three requirements that would actually disqualify you from the dozen that are just a wish list. This post gives you that read, plus how to close the gap inside your application instead of quietly ruling yourself out.

The short answer: a posting is a wish list, not a checklist

A job posting is what a team would love in a perfect world, written by someone describing their dream hire, often copied from an older template. It is not a list of pass/fail conditions where one miss ejects you. Recruiters know almost nobody arrives matching every line, and for intern roles especially they're hiring on potential, not a filled-in checkbox grid.

So the default is apply. The exception is small: a short set of requirements that really are hard gates, where sending it anyway wastes your evening and the recruiter's. Learn to spot those, treat everything else as soft, and you've solved most of the "am I qualified for this internship" question before it starts.

The two or three requirements that are actually hard

These are the ones worth respecting. If you fail one of these outright, the application usually goes nowhere no matter how strong the rest of you is.

Work authorization and visa sponsorship

If a posting says it can't sponsor a visa, or requires authorization to work for the full term, that's a genuine constraint, not a preference. Answer these questions honestly on every application, and never fudge your status to get past a form. If you're an international student and the wording is unclear, your school's international student office is the right place to sort out what you're eligible for. We don't give visa or legal advice here, and neither should a recruiter over email.

Enrollment status and graduation window

Many internships require you to be currently enrolled and returning to school afterward, and a lot of them name a graduation-date window ("graduating December 2027 or later"). These exist because the program is legally and structurally built for students who go back to campus. If you graduate before the window, you're often applying to the wrong product, and a new-grad role is the one you actually want.

Degree program and class year

Some roles are genuinely scoped to a major or a class year: a program open only to rising juniors, or an engineering track that assumes a technical degree. Read whether this is a firm boundary or a soft "ideally." A hard "must be enrolled in a computer science or related program" is different from "coursework in CS preferred," and the second one is not a gate.

On-site or relocation, and rarely citizenship

If the role is in-person in a city you can't get to and won't relocate for, that's real. And a small number of postings, mostly defense, government, or security-cleared work, require citizenship or clearance for legal reasons you can't argue around.

Everything above is where "just apply anyway" wastes everyone's time. Clear these, and almost every other line on the posting is soft.

The requirements that look scary but aren't

These read like walls and function like speed bumps. Missing them lowers your odds. It doesn't zero them.

• Years of experience. A "2+ years" line on an intern posting is usually boilerplate copied from a full-time template. Internships exist so you can build the experience, so recruiters rarely hold interns to it. On an intern role, "experience" is almost always satisfiable with coursework, projects, and clubs that count as proof.
• A specific tool or language. They list React and you know Vue. They want SQL and you've done Python. These are learnable, transferable, and often interchangeable in a recruiter's mind. Name the closest thing you've actually used and don't sweat the exact match.
• A GPA line. A stated number is often listed as "preferred" and, outside a few competitive lanes, often isn't verified up front. Before you let it stop you, read whether that GPA line is a real filter for the kind of employer you're targeting.
• Anything under "preferred," "nice to have," "bonus," or "a plus." This is the wish-list section by definition. You can miss most or all of it and remain a completely legitimate applicant. The difference between "required" and "preferred" is exactly the difference between must-have and would-be-nice.
• Vague soft skills. "Strong communicator," "detail-oriented," "team player." You evidence these with a story, not a certificate. A club role, a group project, a part-time job: all of it counts.

The match check: how much is enough?

Here's the working rule. Clear the hard requirements, hit roughly half of the rest, and apply. That's it.

You'll see the figure "you only need to meet 50 to 60% of requirements" quoted everywhere, often attached to a line that women apply only when they're 100% qualified while men apply at 60%. Treat that as a rule of thumb, not a measured fact. An investigative look at where the number came from traced it to a speculative comment by a Hewlett-Packard executive rather than any published dataset, despite it later appearing in outlets like Harvard Business Review and Lean In (Behavioural Insights Team). So don't treat "60%" as a scientific cutoff. Use it directionally: partial matches are normal and expected.

The real logic is simpler than any percentage. Recruiters almost never get a perfect-match applicant, so the shortlist is built from people who cleared the essentials and looked promising on the rest. The only number that should genuinely worry you is the 0% hit rate on the application you never send. Wave 1 of the cycle runs roughly July through October, the pile is thin early, and a self-rejection is the one guaranteed way to lose.

Close the gap in your application, don't self-reject

When you're missing a soft requirement, the move isn't to hope nobody notices. It's to bridge it on purpose.

Surface your closest real proof at the top of the relevant resume section. If they want a tool you half-know, put the nearest project you've actually shipped first, so the skim lands on evidence, not absence. Then tailor that copy to the posting so the overlap is obvious in ten seconds.

In your cover letter, name the bridge in one honest sentence, not the gap. Something like: "I haven't used Figma in a job, but I designed and shipped my club's site in a comparable tool, and I pick up new design software fast." That's one honest cover-letter sentence that reframes a miss as adjacency. The hard rule: never claim a skill you can't defend live. If listing it means an interviewer will open on it and catch you out, leave it off.

And when the thing you're missing is only "preferred," a referral or a genuinely sharp, tailored application often offsets it entirely. A human who reads you on a colleague's word isn't scoring you against the wish list line by line.

When it's genuinely not worth applying

Two cases, and both are rare. You fail a true hard requirement (no work authorization for a role that can't sponsor, wrong graduation window, can't be on-site and won't relocate). Or you match almost nothing: the role wants three years of a specialized skill and you can't point to a single credible piece of related proof.

Outside those, apply. The far more common mistake, by a wide margin, is talking yourself out of a role over two or three soft misses that were never going to matter.

Frequently asked questions

How many of the qualifications do I actually need to meet?

Meet the hard requirements and roughly half of the rest. There's no official cutoff, and the widely-quoted "50 to 60%" is a rule of thumb, not a measured rule. Clear the genuine gates, show real proof on a fair share of the wish list, and you're a legitimate applicant.

Is it OK to apply for an internship I'm not fully qualified for?

Yes, and it's expected. Recruiters rarely see a full-box candidate, so partial matches are the norm they hire from. The worst realistic outcome is a no you'd have gotten anyway, and the application you don't send fails automatically.

What's the difference between "required" and "preferred" qualifications?

Required means must-have to be considered. Preferred means the wish list. You can skip most or all of the preferred section and still be a serious, legitimate applicant, which is exactly why the two labels aren't interchangeable.

Should I still apply if I don't have the experience they ask for?

Yes. On an intern posting, "experience" is usually satisfiable with coursework, projects, part-time work, and clubs. A "years of experience" line is often boilerplate from a full-time template, and internships are how you build the experience in the first place.

Do you really only need to meet 60% of the requirements, like the study says?

That "study" is the Hewlett-Packard 100%/60% line, and it was never published as data. Treat it as a directional rule of thumb, not proof. The real takeaway is simple: don't self-reject over a handful of soft misses.

What to do today

Pick one posting you talked yourself out of this week. Run the hard-versus-soft split: mark the two or three genuine gates, then everything else as wish list. Confirm you clear the hard items and about half the rest. If you do, spend ten minutes tailoring, name your one honest bridge sentence, and submit it. When you need fresh roles to run this on, browse open internships and put the read to work.