◆TDW

How to Know If You're Qualified for a Tech Job Before You Apply

A requirements list is a wish list written under time pressure, not a contract. What the research says about how requirements are written and screened, which numbers to stop quoting, and a five-step check to run before you apply.

Most advice on this question comes down to one of two slogans: "apply anyway" or "only apply if you tick every box". Neither holds up. The useful answer depends on how job requirements are actually written, how applications are actually screened, and which gaps an employer can live with. There is decent research on the first two. On the third the evidence is thinner, and this post says where it runs out.

Requirements lists are written loosely

A job description is usually not drafted from scratch for each opening. In the Harvard Business School and Accenture study Hidden Workers: Untapped Talent (2021), which surveyed 2,275 executives in the US, UK and Germany, 72% of employers said they reused existing descriptions for middle-skills roles, and 38% used existing or only slightly changed ones for high-skills roles. The study describes descriptions that collect "nice to have" items over time, layered on top of whatever the last version asked for (HBS Working Knowledge).

Reuse doesn't prove that any particular line is optional. It does mean the list in front of you may describe the person the team hired three years ago, or a wish list assembled by several people, rather than a strict minimum.

Employers say as much themselves. In a 2019 Robert Half survey of more than 300 US HR managers, respondents estimated that 42% of the resumes they receive come from people who don't meet the stated requirements. 84% said their company was very (14%) or somewhat (70%) open to hiring and training someone who lacked a required skill. In the same survey, 62% of 2,800 office workers said they had been offered a job without matching every listed qualification (Robert Half).

Those numbers come with caveats. They are self-reported attitudes, not recorded hiring outcomes; the survey covers all industries, not tech in particular; and it predates the hiring slowdown that started in 2022. Taken together with the HBS finding, though, they point the same way: missing a listed item is common, and it is not automatically fatal.

The first cut is often made by software

The flexibility hiring managers describe only helps if your application reaches a person. In the same HBS study, 63% of employers used a recruitment management system (69% at firms with more than 1,000 staff). Among those, 92% relied on it to make the first cut or rank applicants for high-skills roles, and 94% for middle-skills roles. And 88% of employers agreed that qualified high-skills candidates are screened out because they don't exactly match the criteria in the job description (HBS Working Knowledge; HR Dive).

"Relied on it to make the first cut" does not mean every rejection is automatic with no human involved. It does mean the order in which a recruiter sees applications, and whether they see some at all, is often decided by how closely the application matches the posting's wording and filters.

Two practical consequences follow:

  • Describe your skills in the posting's terms. If the listing says "PostgreSQL" and your resume only says "SQL databases", a filter or a skimming recruiter may not connect the two.
  • Answer screening questions accurately. Knockout questions about work authorization, location or salary expectations are where a hard "no" is most likely to be applied mechanically.

Degree and credential filters haven't gone away

Many large employers announced that they were dropping degree requirements. The best study of what happened next is Skills-Based Hiring: The Long Road from Pronouncements to Practice (Burning Glass Institute and Harvard Business School, February 2024), built on job-posting and hiring data from 2014 to 2023. About 3.6% of roles removed a degree requirement, and in those roles the share of hires without a degree rose by only about 3.5%. Across the US workforce, the authors estimate the change made a difference in fewer than 1 in 700 hires in 2023 (Burning Glass Institute report).

The study sorts the firms into three groups. "Leaders", about 37%, really did hire more people without degrees. "In name only" firms, about 45%, showed "no meaningful difference in actual hiring behavior". "Backsliders" made early gains and then reverted (Harvard Kennedy School summary). The report's conclusion is that a degree still works as an informal heuristic for hiring managers even when the posting no longer asks for one.

For you this means: "no degree required" on a listing is a good sign, not a guarantee. If you don't have the degree, the rest of your application has to carry more weight, mainly evidence that you have already done the work the role describes.

The same caution applies to vendor reports on skills-based hiring. LinkedIn's 2025 material, for example, says a skills-based approach can make a company's AI talent pipeline 8.2 times bigger. That is a modelled estimate of how large the pool could be, not a count of hires (LinkedIn Economic Graph).

Two numbers to stop quoting

"Women apply only when they meet 100% of the requirements, men at 60%." This is one of the most repeated hiring statistics, and it has no verifiable source. It traces back to an internal Hewlett-Packard report that was never published. Lean In and McKinsey repeated it, and the McKinsey author confirmed he had never seen the document (Curt Rice). LinkedIn's 2019 Gender Insights Report cites it through a 2014 HBR article. LinkedIn's own data measures something different: women were 16% less likely than men to apply after viewing a job and applied to 20% fewer jobs, while viewing a similar number (LinkedIn Gender Insights Report). Nothing in it records what share of the requirements anyone met.

"Recruiters look at a resume for 7.4 seconds." The figure comes from a 2018 study by the job site Ladders, which published no sample size or method; its 2012 version said about 6 seconds (HR Dive). Treat it as a rough sign that the first human read is a skim, not as a measurement.

There is one data point on how much of a match you need, and it is weak. In TalentWorks' 2018 analysis of more than 6,000 applications from its own users, people who matched about half of the listed skills got interviews at about the same rate as those who matched 90% or more (CNBC). That is vendor data with no published method. It fits the employer surveys above, but don't plan around an exact percentage.

A five-step check before you apply

No study has validated a method for judging your own fit, so the steps below are practical reasoning built on the findings above, not research results. They are ordered from the checks that most often end an application to the ones that matter least.

  1. Hard constraints first. Check work authorization, the countries or regions the role is open to, time zone overlap and employment type (employee or contractor). These are the facts most often enforced by knockout questions, and they are the least negotiable, because changing them costs the employer money or legal effort. A "remote" role that is limited to one country is a no if you live elsewhere, however good your skills are. Our post on why remote jobs turn out hybrid or region-locked covers how to read these signals.
  2. Salary second. If the posting gives a range, compare its top to your minimum. If the top is below your floor, an offer is unlikely to land where you need it. If there is no range, that is a cost of time on your side, not a reason to skip.
  3. Separate core from nice-to-have. Split the technical list into the stack the team ships in every day (the language, the main framework, the main data store) and everything else. Missing a core item is a real gap. Missing two items from a list of eight extras is normal, as the reuse data suggests.
  4. Read years of experience as a range. "5+ years" usually describes a level of independence, not a counter. With four years of directly relevant work you are close. With two you are applying one level up, which is possible but should be a deliberate choice.
  5. Decide what you will say about each gap. For every core item you are missing, have one concrete sentence: what you have used that is closest to it, and how quickly you have picked up something similar before. If you can't write that sentence, the gap is probably too large for this role.

If the role passes steps 1 and 2 and you meet most of the core stack, apply. If it fails step 1, don't. Everything in between is a judgment call, and it should be made on the core requirements, not the full list.

Doing the check before you apply

This check is what the job match score on The Dream Work does for every listing, before you apply. Each role is scored against your profile out of 100, and the breakdown shows where each point comes from:

  • Tech stack (35 points) counts only the skills a company marked as required. Nice-to-have skills are listed on the job page but don't move the score, which matches step 3 above.
  • Experience (15 points) gives partial credit: three years against a five-year requirement earns 9 of 15 points, rather than zero.
  • Salary (20 points) compares the top of the role's range with your minimum, and every listing has a range.
  • Work type, region and employment type (10 points each) cover the hard constraints from step 1, so a region-locked role you can't take shows zero region points in the breakdown instead of surprising you after you apply.

The full formula is on how the job match score is worked out. Create a profile and every listing is scored against it, so you can find remote tech jobs that match your skills without running the check by hand. If you're still deciding where to look, start with where and how to find the best remote tech jobs in 2026. When a role passes the check, the next step is getting past the filters described above; what makes a remote-ready resume different covers that.

Limits of the evidence

Most of the data here comes from employer surveys from 2019 to 2021 that cover all industries. None of it is specific to software roles, and it predates both the post-2022 hiring slowdown and the arrival of AI-assisted screening and AI-written mass applications. The Burning Glass study is the strongest source, and it describes large employers in every sector up to 2023. No verified research ranks which tech-specific mismatches (stack, seniority, time zone, employment type) end an application, which is why the five steps above are presented as reasoning rather than findings.

Sources

For candidates

See your match score on every open role.

Build your profile in 5 minutes and get scored against every active role.

Create free account →