A job description is not a specification. It is a wish list written by several people with different agendas, and reading it well means separating the two or three requirements that genuinely decide the hire from the dozen that were added because they sounded good. The structure gives it away once you know where to look.
Get this right and tailoring becomes easy, because you are no longer guessing what to emphasise.
Who Actually Wrote It?
Most descriptions are assembled rather than written. A hiring manager supplies what the team needs. A recruiter adds the framing and the boilerplate. Someone in HR appends the legal and benefits sections. An old posting for a similar role often supplies the skeleton.
That explains the two things that confuse candidates most, the internal contradictions and the length. Nobody sat down and decided this role requires all fourteen bullets. The list accreted.
Three Signals to Read
Position. Requirements written by the person who needs the work done tend to appear first. Boilerplate drifts to the bottom. The first three bullets of the responsibilities section are usually the job.
Repetition. If a concept appears in the summary, again in responsibilities, and again in requirements, someone cares about it. Repetition across sections is the strongest single signal in a posting, because it means it survived multiple people editing the same document.
Specificity. "Experience with distributed systems" is a category. "Experience operating Kafka in production" is somebody remembering a problem they have. The more specific the line, the more likely it came from the team and the more it matters.
Run those three filters and a fourteen-bullet posting usually collapses to three things that decide it.
The bullets nobody could have written from a template are the bullets that came from the actual team.
Must-Have or Nice-to-Have
The words are not reliable. "Required" sections routinely list things the team would happily waive; "preferred" sections sometimes contain the thing they will not move on.
A few heuristics work better.
Anything legal or licensing is genuinely hard, such as work authorisation, a required certification, or a clearance. These are the closest thing to an automatic filter that exists, and they are usually asked as questions in the applicant tracking system rather than assessed from your resume.
Years of experience are soft almost everywhere. They are a proxy for scope, and evidence of scope beats the number. If a posting says eight years and you have five with clearly relevant depth, apply.
A long technology list is usually a stack description, not a checklist. Nobody expects one person to have all of it. What they expect is the two or three items that appear more than once.
What Does Language Say?
Some phrases carry reliable information, though not the information they claim.
"Wears many hats" and "fast-paced" usually mean under-resourced, which can be an opportunity if you want scope and a problem if you want focus. "Rockstar" and "ninja" tell you about the writer more than the role. A long list of perks and a short description of the work tells you where the effort went.
"Ownership" and "autonomy" are worth taking seriously in both directions. They are real if the team is small and functioning, and a warning if it means nobody will help you.
None of this decides whether to apply. It decides what to ask on the screening call, which is the right place to spend that curiosity.
Putting It to Work
Once you have the three things, the tailoring is mechanical.
Write the three things down. For each, find the strongest evidence you actually have. Put that evidence where a six-second scan will find it, which means the top third of the page, not the fourth bullet of your second role. Use the posting's own words for the thing, where the words are honestly interchangeable with yours. That is what keyword matching is really for, and it is how you appear in the search a recruiter runs later.
If you cannot find evidence for two of the three, that is useful information delivered cheaply. You are not the candidate this posting is describing, and the twenty minutes you just spent saved you an hour.
What Does Nobody Do?
Read the descriptions for the same role at three different companies before applying to any of them.
The overlap is the job. The differences are each company's actual situation. That comparison tells you more about what the market wants from the role than any single posting can, and it makes the requirements you keep seeing impossible to dismiss.
It also makes the cover letter easy, because you now know what this employer asked for that the others did not, and that difference is precisely what a letter should be about.
For what happens after you send it, see what happens to your resume after you hit send.
