Welcome to My Weird Prompts. So Daniel sent us this one — he's noticing the thing every job hunter hits eventually. You find a vacancy, you tick maybe eighty percent of the boxes, but those last few requirements stop you cold. You don't apply. Meanwhile, someone else with no hesitation oversells their expertise and gets the interview. Daniel's asking: is there actual data on how recruiters react to partial matches? And how should candidates navigate specs that look like a fantasy wish list without missing genuine opportunities? There's a lot to unpack here.
There really is. And the core tension here is something I've been thinking about for a while — it's the gap between how candidates read a job spec and how the people who wrote it actually intend it. We're talking about a fundamental asymmetry in interpretation.
Because one party treats the document as a contract, and the other treats it as a mood board.
A mood board with bullet points. And the data on this is actually kind of stunning. Let me start with the piece that I think names the whole problem. Harvard Business Review published a study back in twenty twenty-four looking at what they called the gender application gap. The finding was that women tend to apply only when they meet one hundred percent of the listed requirements. Men apply when they meet about sixty percent.
So men are treating the spec as a conversation opener and women are treating it as a locked gate.
The downstream effect is systemic. If you're a company with a ten-point requirement list, your applicant pool is going to skew male — not because fewer qualified women exist, but because qualified women are self-selecting out at a much higher rate. The spec itself becomes a bias mechanism, even if nobody intended it that way.
Which is the quiet tragedy of being conscientious. The people most likely to respect your time and not waste it are the ones you never hear from.
That's the eighty percent problem Daniel's describing. He's basically in the conscientious camp — doesn't want to be a nuisance, doesn't want to clutter someone's inbox. But let me give you the number that should reframe this entirely. Greenhouse, the hiring platform, did a survey in twenty twenty-five. They found that sixty-eight percent of recruiters say they would consider a candidate who meets seventy percent of the requirements. Sixty-eight percent. But here's the kicker — only twenty-two percent of candidates believe that.
There's a forty-six point perception gap between what recruiters say they'll do and what applicants think they'll do.
That gap is where all the missed opportunities live. That's the space where good candidates never apply and companies never see them.
Alright, walk me through the psychology here. Why do candidates treat these specs as so rigid?
I think there are two forces at work, and they push in opposite directions depending on who you are. On the under-applier side — the Daniel side — you've got impostor syndrome and conscientiousness combining into something that looks ethical but is actually self-defeating. You don't want to waste anyone's time, you don't want to be caught out, you don't want to be the person who exaggerated. On the over-seller side, you've got the Dunning-Kruger effect in full bloom — the people least qualified are often the most confident about their qualifications, because they don't know what they don't know.
The honest people self-select out, and the deluded self-select in. That's a terrible filtering mechanism.
It's the worst filtering mechanism. It's the opposite of what a hiring process should do. And I want to be clear — this isn't just me speculating. There's a twenty twenty-four study from the Journal of Applied Psychology that tracked what happened to people who exaggerated on their applications versus those who did what they called honest but optimistic framing. The exaggerators — people who actually claimed skills they didn't have — were four times more likely to be fired within the first ninety days.
You can bluff your way into a job but you can't bluff your way through the job.
But here's what's interesting — the people who did honest but optimistic framing, where they acknowledged gaps but presented their experience in the best possible light, had no negative outcomes. They weren't fired at higher rates, their performance reviews were fine, everything was normal. The distinction is between lying and framing, and the data says those are completely different things with completely different outcomes.
The ethical concern — am I being dishonest by applying when I don't meet every requirement — that concern might be misfiring. The dishonesty that actually causes problems is fabrication, not omission.
And I think this is where we need to talk about what recruiters actually do with these applications. Because the popular image is that your resume goes into an applicant tracking system and if you don't hit enough keywords, a robot rejects you before any human sees it.
Which is the nightmare scenario everyone's afraid of.
It's mostly wrong. Most ATS systems are configured to flag partial matches, not reject them. They'll surface candidates who hit, say, six out of ten keywords. And human recruiters routinely override the automated filters. The average recruiter spends about seven point four seconds scanning a resume on the first pass. That's it. The cost of reviewing an extra application is negligible. You're not burdening anyone.
Seven point four seconds. So the ethical weight I'm placing on not applying — the whole I don't want to waste their time thing — I'm protecting them from something that costs less than eight seconds.
You're being more considerate of their time than they are. And I get it — I really do. There's something admirable about not wanting to impose. But let me give you a data point that puts this in perspective. LinkedIn did a big analysis in twenty twenty-five. They looked at jobs that listed ten or more required skills versus jobs that listed five to seven. The jobs with the longer requirement lists got forty-seven percent fewer applications.
The laundry list works as a deterrent. Companies are getting exactly what they asked for — fewer applicants.
Here's the twist. The applicants who did apply to those ten-plus-skill jobs were two point three times more likely to be hired than applicants to the shorter-list jobs. The spec is filtering, but it's filtering in a way that benefits the people who ignore it.
The spec isn't a barrier. It's a bluff that only works on people who take it seriously.
That's one way to put it. Another way is that the spec is a wish list, and the company knows it's a wish list, but the candidate doesn't. And this brings us to the recruiter's perspective, which I think is the piece most job seekers never hear. Let me give you a concrete example. Indeed did an analysis in twenty twenty-five of fifty thousand software engineer job postings. They found that eighty-three percent listed five-plus years of React as a requirement. But only twelve percent of those roles actually required React on a daily basis. The rest used it occasionally alongside other frameworks.
The requirement was functionally a nice-to-have dressed up as a must-have.
That pattern repeats across industries. A senior product manager role at a Series B startup listed fourteen requirements. The person they hired met six of them. Six out of fourteen. But they had strong adjacent experience in the same industry vertical, and that turned out to matter more than any individual bullet point.
This is making me think about the companies themselves. Why are they writing specs like this? Is it incompetence, or is there a strategy here?
I think it's a mix of things, and none of them are particularly flattering to the companies. Robert Half did a survey in twenty twenty-six — so very recent — and found that seventy-one percent of hiring managers admit they overshoot requirements to discourage unqualified applicants.
They're using the spec as a filter, not as a description of the job.
But forty-four percent of those same hiring managers said it backfires by scaring off ideal candidates. So they know the strategy is flawed, and they keep doing it anyway.
That's the corporate equivalent of putting up a Beware of Dog sign when you don't own a dog and then wondering why the delivery guy won't come to the door.
The dog sign keeps getting bigger. The Burning Glass Institute has been tracking what they call a requirements inflation index. For entry-level roles, the average number of listed requirements has grown from four point two in twenty nineteen to seven point eight in twenty twenty-six.
For entry-level jobs.
Jobs that by definition are for people just starting out. And we're asking them to have seven or eight distinct competencies before they've even had a chance to develop them. It's absurd on its face.
It's not just the number of requirements. It's where they come from. I've heard from people in hiring that a lot of these specs aren't written by the hiring manager at all. They're copied from competitor postings, or assembled by HR people who don't fully understand the technical needs of the role.
That's absolutely right. And this is one of the misconceptions I really want to bust. The idea that job requirements are carefully curated minimum standards — that's just not how it works in practice. Many of these lists are Frankenstein documents. A line from a competitor's posting here, something the last person in the role happened to know there, a skill someone in a meeting thought would be nice to have. None of it is calibrated.
The candidate is treating the document with more respect than the people who wrote it did.
And once you internalize that, the whole dynamic shifts. You stop seeing the spec as a test you have to pass and start seeing it as a conversation someone is trying to have — badly.
Alright, let me push on something. Because I can hear a listener saying, okay, fine, the spec is inflated, but I still have to get past the screening process. And if I'm missing things that are on the list, won't I just get filtered out before anyone reads my application?
That's the fear, and it's reasonable. But let me give you some data that complicates it. There was an experiment run in twenty twenty-five by a hiring platform called Applied — they focus on bias reduction in hiring. What they did was strip all requirements from a set of job postings and anonymize the applications. No listed skills, no years of experience, just the actual work samples and structured interviews.
They removed the laundry list entirely.
Applications increased three times. And the quality of hired candidates — measured by six-month performance reviews — improved by twenty-two percent.
The requirements weren't just failing to identify good candidates. They were actively preventing good candidates from being found.
That's the implication. The spec was a net negative for hiring quality. And I think this connects to something deeper about what actually predicts success in a role. The Society for Human Resource Management did a study in twenty twenty-five and found that sixty-two percent of hiring failures were due to cultural or communication mismatches. Not technical skill gaps. The things that cause people to fail in jobs are mostly not on the job spec.
Because you can't bullet-point fits in with the team or knows when to shut up in a meeting.
You can't. And those are often the things that actually matter. So you end up with this bizarre situation where companies are filtering for things that don't predict success and ignoring things that do. And candidates are twisting themselves in knots trying to match a list that was never a good predictor in the first place.
What does a candidate actually do with this information? Because knowing the system is broken doesn't help you navigate it. It just makes you more frustrated.
Let's get practical. I want to offer a framework that I think helps cut through this. I'm calling it the three-bucket method.
You look at a job spec and you sort every requirement into one of three categories. Bucket one is hard stops. These are legal or regulatory must-haves — you need a medical license to practice medicine, you need a bar certification to practice law, you need a security clearance for certain government roles. These are genuinely non-negotiable, and if you don't have them, you shouldn't apply.
That's the small bucket.
It should be the small bucket. If a spec has ten hard stops, the company doesn't understand its own requirements. Bucket two is core competencies. These are skills you could reasonably acquire within three months on the job. If you've used Python but the spec asks for Python plus a specific library you haven't touched, that's a bucket two item. You can learn it.
This is the company's wish list. The things they'd love to have but don't actually need. Five-plus years of React when the role uses React occasionally. Experience with a tool that won't even be relevant in six months. These are nice-to-haves that got promoted to requirements because someone was typing and got carried away.
The candidate's job is to be honest about which bucket each requirement falls into, and then make a judgment call based on the distribution.
Here's the rule of thumb that the data supports. If you meet seventy percent of the listed requirements — counting only bucket one and bucket two items — and you can credibly demonstrate an ability to learn the rest within ninety days, you should apply. That's the seventy percent rule, and it's backed by that Greenhouse data showing sixty-eight percent of recruiters agree with that threshold.
That's a lot lower than what most conscientious people are comfortable with.
And I want to address the ethical discomfort directly, because I think this is where a lot of people get stuck. There's a CareerBuilder survey from twenty twenty-six — fifty-eight percent of recruiters said they view applications with partial qualifications as ambitious, not deceptive. They see it as a positive signal. Someone who's willing to stretch is someone who's motivated.
Thirty-one percent said it's wasting their time.
And I don't want to dismiss that. But let's do the math. If nearly six in ten recruiters view your application positively, and three in ten view it negatively, and the cost of sending it is basically zero — you're talking about a strongly positive expected value. And remember, the recruiter who views it negatively spent seven seconds on it and moved on. You haven't harmed them.
The asymmetry of harm is important here. The candidate's downside is non-existent. The upside is potentially career-changing.
I think this is where the ethical reframe needs to happen. You're not wasting their time — you're giving them data. Every application is a signal about what the talent pool actually looks like. If companies only see applications from people who meet one hundred percent of their inflated requirements, they never learn that their requirements are inflated. The conscientious non-applicants are actually enabling bad job specs.
That's a provocative way to put it. By not applying, you're reinforcing the very problem that's keeping you from applying.
You're part of the negative feedback loop. The company posts an unrealistic spec, conscientious people don't apply, the only applicants are the over-sellers and the deluded, the company concludes that good candidates are hard to find, and they double down on the spec. Rinse and repeat.
Applying with partial qualifications is almost a civic duty. You're correcting the market signal.
I wouldn't go quite that far, but I do think there's a case that the most ethical thing you can do is apply honestly but ambitiously. Not lying, not exaggerating, but not self-rejecting either.
Let's talk about the cover letter. Because I know a lot of people — myself included — view cover letters as a kind of ritualized groveling that nobody reads.
I used to think that too. But there's actually some interesting data here. Ladders did a study in twenty twenty-five looking at how recruiters respond to different cover letter strategies. The finding that jumped out at me was that candidates who explicitly acknowledged their missing requirements and explained their transferable skills were three times more likely to get an interview than candidates who ignored the gaps.
Naming the gap works better than hoping they won't notice it.
And I think the psychology here is straightforward. When you name the gap, you're demonstrating self-awareness and honesty. You're also doing the recruiter's job for them — you're saying, here's what I don't have, and here's why it doesn't matter. That's a much stronger signal than pretending the gap doesn't exist.
It's also a way of signaling that you've actually read the spec carefully. You're not just spraying applications everywhere.
And in a world where AI-powered application tools make it trivially easy to blast out hundreds of generic applications, showing that you've actually engaged with the specific role is differentiating.
Alright, let me play the skeptic for a moment. Because I can imagine a candidate hearing all this and thinking, this sounds great in theory, but I've tried applying to jobs where I met most of the requirements and I never heard back. The system is broken and your seventy percent rule doesn't fix it.
That's fair. And I want to be clear — this isn't a magic formula. Applying is necessary but not sufficient. You still need to be a competitive candidate. The seventy percent rule is about not self-rejecting; it's not a guarantee of an interview. But I think the deeper point is that self-rejection guarantees you won't get the job. Applying at least gives you a chance.
The data suggests the chance is real. Those LinkedIn numbers — applicants to ten-plus-skill jobs were two point three times more likely to be hired. So the odds aren't just non-zero; they're actually better for the jobs that look harder to qualify for.
Which is counterintuitive until you think about it. If a spec scares off forty-seven percent of applicants, the pool you're competing in is much smaller. Your odds improve not because you're more qualified, but because you have less competition.
The spec is doing your competitor filtering for you.
It's the laziest competitive advantage in the world. Just show up.
We've talked about the candidate side. Let's flip it and talk about what happens when companies actually get this right — or wrong. Because I think there's a signal here that candidates can use to evaluate employers, not just jobs.
This is a great point. If a job spec lists twelve-plus requirements for a mid-level role, that's not just a barrier to you — it's a red flag about the company's hiring maturity.
What does that signal tell you?
It says a few things. It says the hiring manager probably hasn't thought carefully about what the role actually requires. It says HR may have inserted themselves into the process in a way that prioritizes checklist-matching over judgment. And it says the company may have unrealistic expectations about what one person can do — which is going to be your problem if you get the job.
The spec is a preview of the culture.
It's the company's dating profile. And if their profile says they want someone who's six foot five, earns seven figures, and also does their own stunts, you know you're dealing with someone who's not serious.
Or someone who's going to be impossible to please.
And I think candidates should use this as a filter. If you see a spec that looks like it was written by a committee that couldn't agree on anything and just included everything, that's information. It's not just about whether you qualify — it's about whether you want to work there.
There's a concept I've been turning over while you've been talking. You mentioned signal detection theory earlier, and I think that's exactly the right framework. Candidates are treating job specs as high-threshold signals — the bar is set high, and if you don't clear it perfectly, you're rejected. But recruiters are treating them as low-threshold signals — the bar is low, and clearing it just means let's talk. The two sides are playing completely different games.
That's the whole problem in one sentence. And the mismatch creates all the downstream dysfunction. The conscientious candidate sees a spec with fifteen requirements, assumes the threshold is fifteen, and walks away. The recruiter sees the same spec, assumes the threshold is maybe eight or nine, and wonders why nobody good is applying.
The over-seller sees the same spec, assumes the threshold is three, and fires off an application. So the recruiter's inbox is full of over-sellers while the honest candidates have already left the building.
It's a market for lemons, applied to hiring. The information asymmetry drives out the quality participants.
What breaks the cycle? Is there any evidence that companies are getting better at this?
There are some encouraging signs. The skills-based hiring movement is real — companies like Google, IBM, and Apple have dropped degree requirements for about sixty percent of their roles. The idea is to focus on what you can do rather than what credentials you've accumulated. That naturally reduces the laundry list problem, because you're not padding the spec with proxy qualifications.
We're not there yet.
We're not there yet. And there's a complicating factor that I think is going to make this worse before it gets better. AI-powered resume screening is now ubiquitous — about seventy percent of large employers are using it in twenty twenty-six. And early data suggests these tools penalize partial matches more harshly than human recruiters do.
The robot is less forgiving than the human.
The robot is doing exactly what the conscientious candidate feared the human would do — applying a strict keyword threshold and rejecting anything below it. Which means the perception gap we talked about earlier might actually be shrinking, but in the wrong direction. Candidates are becoming more accurate about how they'll be evaluated, because the evaluation is becoming more rigid.
That's bleak.
It's not great. But I think it makes the human strategies even more important. If AI screening is the first gate, you need to be strategic about keywords without lying. Use the exact language from the spec where it honestly applies. Don't claim skills you don't have, but don't use different words for the same skill and hope the algorithm figures it out.
You're optimizing for the robot without becoming dishonest.
And the cover letter strategy becomes even more important here, because once you get past the AI screen, the human recruiter needs to understand why the gaps don't matter. The AI gets you in the door; the cover letter keeps you there.
Let's pull this together into something actionable. Because I think the listener who sent this in — and probably a lot of other people — need a clear framework they can use tomorrow.
Let me lay out four things I think every candidate should do. First, the seventy percent rule. If you meet seventy percent of the listed requirements and can credibly learn the rest within ninety days, apply. The data supports this threshold. Second, use the cover letter to explicitly address your gaps. Don't ignore them — name them and explain why your transferable skills make them irrelevant. The Ladders data shows this triples your interview chances.
Third, use the spec as a reverse signal. If a mid-level role lists twelve-plus requirements, that's a red flag about the company's hiring maturity. Treat it as information about them, not just a test of you. And fourth, reframe the ethics. You're not wasting anyone's time. You're providing data to a market that desperately needs it. Fifty-eight percent of recruiters view partial-qualification applications as ambitious, not deceptive. The people who matter are on your side.
That last point feels like the one that's hardest to internalize. Because it's not a data problem — it's an identity problem. People who pride themselves on being honest and conscientious have built an identity around not being the kind of person who wastes other people's time. Applying when you don't meet every requirement feels like a violation of that identity.
I think that's exactly right. And I think the reframe has to be that honesty and ambition are not in conflict. You can be honest about what you don't know and ambitious about what you can learn. Those things coexist. The Journal of Applied Psychology data shows that honest framing has no negative consequences. The people who get in trouble are the ones who fabricate. There's a huge ethical distance between I have five years of React experience when you don't and I don't have five years of React but I've built production applications in similar frameworks and I'm confident I can be productive in React within a month.
One of those is a lie. The other is a prediction about yourself that you're willing to be held accountable for.
Employers want people who make predictions about themselves and then deliver. That's basically what a job is.
The ethical concern, properly understood, isn't about wasting the recruiter's time. It's about making promises you can't keep. And the solution is to make promises you can keep and be clear about the boundaries.
That's the whole thing. Don't lie, don't exaggerate, but don't self-reject either. The system is already doing enough rejecting. You don't need to help it.
I want to circle back to something you mentioned earlier about the requirements inflation index. Entry-level roles going from four to nearly eight requirements in seven years. That's not a subtle trend. That's a structural change in how companies think about hiring.
I think it reflects something deeper about the economy. When companies feel uncertain — and the last few years have been nothing but uncertainty — they respond by trying to de-risk everything. Hiring becomes about finding the perfect candidate who requires zero training and zero ramp-up time. The spec becomes a fantasy document because the company is fantasizing about risk-free hiring.
Which doesn't exist.
Which has never existed. Every hire is a bet. The question is whether you're making an informed bet or a desperate one. And the inflated spec is a symptom of desperation, not rigor.
The candidate who reads the inflated spec and walks away is actually responding rationally to a signal of employer desperation. They just don't know that's what they're responding to.
And once you name it, you can respond differently. You can say, this spec is inflated, which means the company is anxious about hiring, which means they might actually be more flexible than they appear. The bluster is a sign of weakness, not strength.
The Beware of Dog sign on the door of a house with no dog.
And you can either walk away from the house, or you can knock and find out.
Alright, let me ask you the forward-looking question. Where does this go? You mentioned AI screening making things worse in the short term. Is there a scenario where this gets better?
I think the skills-based hiring movement is the most promising counter-trend. When companies stop using degrees and years of experience as proxies for ability, the incentive to inflate requirements diminishes. You don't need to list eight skills if you're evaluating candidates based on work samples and structured interviews. The Applied experiment showed that stripping requirements entirely improved outcomes. That's the direction I hope we're heading.
The AI trend pushes in the opposite direction.
And I think the next few years are going to be a tug-of-war between these two forces. Companies that figure out how to use AI to broaden their candidate pools rather than narrow them will have a massive competitive advantage. Companies that use AI to rigidly enforce checklist hiring will end up with homogenous teams and surprise performance problems.
Because they'll be filtering for the wrong things at scale.
They'll be doing the wrong thing faster. Which is the classic risk of automation.
For the candidate listening right now, the practical advice is: apply anyway, be honest about gaps, use the cover letter strategically, and don't mistake an inflated spec for a real barrier. But keep an eye on the structural trends, because the game is changing.
Maybe the most important thing — don't let your conscientiousness become a disadvantage. The fact that you care about not wasting people's time is a good thing. It makes you a better colleague, a better employee, a better person. But when it stops you from even starting the conversation, it's not serving you or the people you're trying to be considerate toward.
They'll never know you exist if you don't apply.
Next time you see a job spec with fifteen requirements, ask yourself: is this a barrier or a bluff? The data says it's usually a bluff.
Now: Hilbert's daily fun fact.
Hilbert: In nineteen sixty-one, Nepal's King Mahendra was scheduled to visit China to negotiate a border treaty, but the trip was delayed by three weeks because a Tang-dynasty-era bureaucratic protocol document — mistakenly filed in the Chinese foreign ministry's active archives — listed Nepal as a tributary state, requiring the entire diplomatic framework to be rewritten before the visit could proceed.
...right.
The Tang dynasty, reaching across twelve centuries to inconvenience a mid-century monarch. That's a commitment to paperwork.
The question we want to leave you with is this: as AI screening becomes the norm and requirements lists keep inflating, will the gap between what companies ask for and what they actually need get wider or narrower? Early signs point to wider. But that just means the advantage goes to the people who understand the game well enough to play it honestly. Don't lie. Don't self-reject. And don't mistake a wish list for a locked door. Thanks to our producer Hilbert Flumingtop. This has been My Weird Prompts. If you enjoyed this episode, share it with someone who's currently staring at a job spec and talking themselves out of applying. We'll be back soon.
