SS
Key Takeaways
- A posting is usually written by three or four people - hiring manager, HR, a reused template, sometimes legal - and each contributes different weight.
- The title and first paragraph are the hiring manager's; the long bullet list is often accumulated and unedited.
- Requirements framed as "must have" with specific detail are real; vague categories near the bottom rarely are.
- Clustered similar tools almost always mean "one of these," not all of them.
- Five minutes of reading this way saves an hour of mis-targeted tailoring.
Job postings read like unified documents written by one person. They almost never are — and once you can see the seams, you can tell which requirements decide the shortlist and which are decoration.
Who Writes Which Part
The hiring manager writes the title and the opening paragraph. This is the part closest to what they actually need, because it is the part they care about and usually draft themselves. It is the highest-signal text in the posting.
HR or a recruiter writes the structure and the boilerplate. Section headings, the culture paragraph, benefits, the equal-opportunity statement. Necessary, and irrelevant to whether you are qualified.
The bullet list is usually inherited and extended. Most requisitions start from a similar prior role. Each contributor adds items; almost nobody removes them. This is why lists reach twenty items that no single person expects.
Legal or compliance adds the constraints. Work authorisation, licensing, background-check requirements. These are genuinely non-negotiable, unlike much of the bullet list.
What This Tells You
Weight the top of the posting far more than the bottom. A skill in the title and opening paragraph is central. The same skill appearing only as bullet fourteen is likely inherited.
Repetition is the strongest signal. If something appears in the title, the summary and the bullets, three different contributors all thought it mattered. That is the job.
Specificity beats generality. "Snowflake" is a real, checkable requirement someone chose deliberately. "Familiarity with modern data tooling" is a category hedge covering whatever the candidate happens to know.
Length signals process, not expectation. A twenty-item list is evidence of an unedited requisition, not evidence that they expect twenty matches.
The Patterns Worth Recognising
The cluster. Several similar tools listed together — "Tableau, Power BI, or Looker," "AWS, Azure, GCP." This almost always means one is sufficient. Listing all three because you saw them flagged is transparent padding.
The wish list tail. The last four or five bullets are frequently "nice to haves" that migrated into the main list. They read as requirements and function as preferences.
The duplicated soft skill. "Communication," "stakeholder management," "cross-functional collaboration" and "presentation skills" as four separate bullets is one requirement written four times by different contributors.
The impossible combination. Requirements that rarely co-occur in one person — deep ML research plus production infrastructure plus stakeholder-facing consulting. Usually two roles merged, or an aspirational composite. Apply if you have a strong subset.
The copied template. Bullets referencing tools or processes that do not match the rest of the posting, or a seniority level inconsistent with the title. Leftovers from the role the requisition was cloned from.
Working Example
Senior Analytics Engineer — Reporting Platform
We're looking for a senior analytics engineer to own our dbt models and reporting layer as we scale from 40 to 200 tables...
Requirements: dbt, SQL, Snowflake, Python, Looker, Tableau, Power BI, Airflow, Git, data modelling, stakeholder management, communication, cross-functional collaboration, Agile, Jira, bachelor's degree, fast-paced environment, attention to detail.
Reading it by source:
- Title and opening paragraph: dbt, SQL, reporting layer, scale. This is the job.
- Cluster: Looker / Tableau / Power BI — one of these is fine.
- Duplicated soft skill: stakeholder management, communication, cross-functional collaboration — one requirement, three phrasings.
- Process tail: Agile, Jira, attention to detail, fast-paced — noise.
- Real constraint: bachelor's degree, if stated firmly.
Eighteen items reduce to four that matter: dbt, SQL, Snowflake, and one BI tool. Tailor to those and you have addressed the posting properly.
What to Do With the Reading
If you match the top-signal items, apply and tailor to them specifically. Your summary and first bullets should speak to the title and opening paragraph, not the bullet list.
If you match the bullet list but not the opening paragraph, reconsider. You match the accumulated preferences and miss the actual job.
If you miss one top-signal item, decide whether it is adjacent to something you have. If yes, apply and make the adjacency explicit. If it is genuinely the whole role, move on.
If the posting is entirely vague, there is little to tailor to. Apply lightly and spend your effort on clearer postings — vagueness often signals an unclear internal brief, which tends to produce a difficult process.
Frequently Asked Questions
Should I still apply if I miss several listed requirements? Depends which. Missing several tail-end items is normal. Missing what is in the title and opening paragraph is not.
How do I tell a real "must have" from a wish? Position, repetition and specificity. Something in the title, repeated, and named precisely is real. Something appearing once in the bullet tail usually is not.
Do recruiters expect candidates to match everything? No. Recruiters know their own postings are inflated, and shortlists routinely include people missing several listed items.
What about postings that list years of experience? Treat it as a band rather than a threshold. One or two years short with strong relevant evidence is often fine; five years short rarely is.
Is a very long requirements list a red flag? Not usually about the company — more often it reflects an unedited requisition process. It is a signal about how to read the list, not whether to apply.
Turn the Reading Into a Worklist
Once you know the four things that matter, the tailoring question becomes narrow: does your resume evidence those four, in the employer's words?
Scan your resume against the posting and check the flagged terms against your own reading — the items that are both high-signal in the posting and missing from your resume are your entire worklist.
Related: finding the requirements that decide the shortlist and tailoring in ten minutes.
What is your resume scoring right now?
Scan it against a job description and get your ATS match score in about a minute.
Drop your resume here or choose a file
PDF only. Max 2 MB.
We never share your data or use it to train AI models.
Templates that keep this structure intact
This template is ATS-tested — start from it and the formatting rules in this guide are already handled.
Was this guide useful?
Be the first to rate it.
