41% of Job Descriptions Ask for Too Much

Every job description scored through ShouldApply gets a complexity classification. The scoring engine counts distinct requirements, measures how many unrelated skill domains a single posting spans, flags seniority conflicts, and tallies years of experience requested. The result is one of four tiers.

Across all scored postings, roughly 41% land in the Overloaded or Unrealistic tiers. That means nearly half of what you're scrolling through on job boards was written by someone who doesn't have a clear picture of what the role actually needs.

The four tiers break down like this:

The sweet spot for a well-written posting is 6 to 8 distinct requirements. That's enough to describe the core of a role without drifting into fantasy.

Once you pass 12, you're in Overloaded territory. The scoring engine flags this because 12+ requirements almost always signal that the posting covers multiple jobs stitched together. A "Marketing Manager" who also needs advanced SQL, paid media buying experience, team leadership, and HTML/CSS proficiency isn't one role. It's three roles crammed into one headcount.

Unrealistic postings average 15+ distinct requirements. Some go as high as 20. At that point, the company is describing a fictional person. You could have 10 years of experience in the exact field and still only match 60% of what they're asking for.

The domain span signal matters just as much as raw count. A posting asking for Python, data modeling, and SQL is one domain (data). A posting asking for Python, Figma, cold outreach, and GAAP accounting is four domains. The more domains a single role spans, the less likely any one person covers all of them.

Tech and financial services consistently produce the most overloaded postings. Both industries tend toward large, bureaucratic hiring processes where multiple teams contribute to a single job description. The result reads like a grocery list instead of a role.

Trades, healthcare support, and retail tend toward Realistic or Ambitious tiers. These industries hire for specific, well-defined tasks. An electrician posting lists what certifications you need and what kind of work you'll do. There's no room for wish-list padding because the requirements are binary: you either have the license or you don't.

The root cause in overloaded industries is committee writing. A hiring manager drafts the core requirements. Then engineering adds their preferred tech stack. Then a VP adds "strategic thinking" and "cross-functional leadership." Then HR adds boilerplate about "fast-paced environments" and "wearing many hats." By the time it goes live, nobody owns the document and it describes nobody real.

Startups are a mixed bag. Some write tight, focused descriptions because they know exactly what gap they're filling. Others write Unrealistic postings because they genuinely want one person to do everything. The difference usually comes down to whether the founder has hired before.

The complexity scorer doesn't just count bullet points. It looks for specific patterns that indicate a disconnected or inflated job description. Here are the most common signals that push a posting into Overloaded or Unrealistic territory.

Yes, but not in the way you'd think. When a posting asks for everything, nobody scores well against it. That's the whole point of the complexity tier: it tells you whether a low score is about your gaps or about the posting being broken.

A 48 against an Unrealistic posting is normal. It doesn't mean you're unqualified. It means the posting was written to describe a person who doesn't exist. If you scored the same posting against 100 experienced professionals in that field, the average would still land somewhere in the 40s or 50s.

Compare that to scoring a 48 against a Realistic posting. That's a real signal. It means you're genuinely missing core requirements, and you should look at the fit score breakdown to understand what's costing you points.

This is why ShouldApply shows the complexity tier alongside your score. A high score against a Realistic posting is the strongest signal that a job is worth your time. A mediocre score against an Unrealistic posting is noise.

The honest answer: the data is still accumulating. ShouldApply has been scoring job descriptions for complexity since early 2026, and we don't have enough months of data to identify a clear trend with confidence.

Early signals aren't encouraging. Requirement inflation looks like it's continuing, particularly in tech and knowledge-work roles. Remote job postings tend to be more overloaded than on-site equivalents, possibly because companies feel they can demand more when the location barrier is gone.

We'll publish a proper analysis once we have 6+ months of longitudinal data. For now, the best thing you can do is check the complexity tier on any posting before you invest time in an application.

Overloaded and Unrealistic postings aren't automatic skips. They just change how you approach the application.

If the posting is Overloaded (12-14 requirements), treat the requirements as a wish list. Focus on the top 3-4 bullet points. Those are the ones the hiring manager actually cares about. The rest got added by other stakeholders and will probably never come up in an interview. Apply if you cover those core requirements, even if your overall match percentage looks low.

If the posting is Unrealistic (15+ requirements), check the company first. Some organizations post these out of bureaucratic habit. Government agencies, large banks, and enterprise software companies are repeat offenders. The actual interview bar is often much lower than the posting suggests. Other times, an Unrealistic posting means the role is genuinely confused and the hiring process will reflect that.

Use your fit score as a tiebreaker. If two postings interest you equally and one is Realistic with a 72 while the other is Unrealistic with a 51, spend your energy on the first one. The Realistic posting is more likely to result in an interview because the company knows what they want.

And if you're wondering whether you should apply when underqualified, the complexity tier adds useful context. Being "underqualified" for an Unrealistic posting is a very different situation than being underqualified for a Realistic one.

Frequently Asked Questions

Free Tools

Related Posts