Most application effort is wasted before a word gets written — on postings that were never winnable, or on requirements that were never real. Reading the document properly is the cheapest possible improvement to a job search.
The four kinds of text in a posting
A job description is not one document. It's four, stapled together, and only two of them matter to you.
| Section | What it is | Worth your attention? |
|---|---|---|
| Company blurb | Marketing. Mission, culture, "we're a family" | No |
| Responsibilities | What the job does day to day | Yes — this is the real role |
| Requirements / qualifications | What they're screening on | Yes — this is what gets scored |
| Benefits, EEO, legal | Boilerplate | No |
When you pull keywords, you're working from rows two and three only. Deleting the other two first makes the posting about a third of its original length and much easier to read accurately.
Hard requirement or wish?
The single most useful skill here. Postings routinely list far more than any real candidate has, and treating every line as mandatory means disqualifying yourself from roles you'd get.
Usually a real gate
- Licences, certifications and clearances named specifically ('active RN licence')
- Legal requirements — work authorization, right to work, statutory qualifications
- A degree named as required in a regulated field
- Anything repeated in both the requirements list and the responsibilities
- The one or two technologies the whole role is built around
Usually negotiable
- '5+ years of experience' on an otherwise mid-level role
- Long tool lists where half overlap in function
- 'Bachelor's degree or equivalent experience'
- Anything under 'Nice to have', 'Bonus points' or 'Preferred'
- Soft-skill lines: 'excellent communicator', 'thrives in ambiguity'
Reading the level, not the title
Job titles are unreliable across companies — one firm's Senior Analyst is another's Analyst II. The posting tells you the real level in three places:
- Years asked for, discounted by about a third for the usual inflation.
- Scope language — "own", "define", "set the roadmap" is senior; "support", "assist", "contribute to" is not.
- Who you'd report to and whether anyone reports to you. A "Manager" title with no direct reports is an individual contributor role.
If the level is well above yours, that's a seniority gap no rewrite closes. If it's well below, expect to be screened out as overqualified — that filter runs in both directions.
Signs a posting isn't really open
Not every listed job is a job. Worth spotting before you spend twenty minutes:
- Reposted repeatedly over months with the same text — often filled, stalled, or a permanently open pipeline requisition.
- Extremely broad requirements covering three distinct roles — the team hasn't decided what they want, and screening will be arbitrary.
- No salary range in a jurisdiction that requires one — worth a raised eyebrow about how carefully the posting was written.
- Listed only on aggregators, with nothing on the company's own careers page. Sometimes a scraped listing that no longer exists.
- A "confidential" employer with a generic description — could be legitimate executive search, could be a resume-collection exercise.
None of these is proof. All of them are reasons to spend your tailoring time somewhere else first.
Where to actually apply
When a posting exists on both an aggregator and the company's own site, apply through the company's site. Aggregator submissions sometimes arrive with fields missing or a converted resume file, and the company's own portal is the record that recruiter actually works from.
The go / no-go decision
- 1
Do I clear the hard gates?
Licences, authorization, statutory requirements. If not, stop — nothing else matters.
- 2
Can I evidence the top three requirements?
Not 'have I heard of them' — can I point at a dated bullet that proves each one?
- 3
Is the level within one notch of mine?
Two notches up is a lottery ticket; two notches down gets filtered as overqualified.
- 4
Would I actually take this job?
If lukewarm, don't spend the twenty minutes. Volume without intent produces noise, not offers.
Four yeses earn a twenty-minute tailoring pass. Anything less and your time is better spent on the next posting.
Let the engine do the reading
Once you've decided a posting is worth it, paste the whole thing into the free checker alongside your resume: it extracts the weighted requirements, ranks them the way a matching engine does, and shows you which ones your resume already proves. That turns "read the posting carefully" from a judgment call into a list.
Frequently asked questions
- How do I know which job requirements are actually mandatory?
- Licences, work authorization and statutory qualifications are real gates. "5+ years", long overlapping tool lists, "or equivalent experience" and anything under "nice to have" usually aren't. A skill repeated across the summary, responsibilities and requirements is the job.
- Should I apply if I don't meet all the requirements?
- Yes, provided you clear the hard gates and can evidence the top two or three requirements. Postings routinely list more than any real candidate has. The exception is licensure, clearances and legal eligibility — no application gets past those.
Written by
MeritSlate Team
The team building MeritSlate's deterministic scoring engine — nine evidence-anchored axes, a nine-vendor ATS parse simulation, and every point backed by receipts.