Written by Greg Schneider, Contributor, 2026

How to Read a Job Posting

A job posting looks like a description of a job. It isn’t, quite. It’s a document with an author, an agenda, and usually a committee — and once you learn to read it that way, the whole thing gets less intimidating and more useful.

Every posting is written by several hands. The hiring manager wrote the parts about the actual work. HR added the parts about the company. Someone in legal added the parts at the bottom. A recruiter may have rewritten all of it to match a template. None of those people were trying to describe one single human being. Keep that in mind, and the posting stops being a verdict on you and starts being what it actually is: a rough sketch of a problem a team needs solved.

The requirements list is a wish list

Start with the longest part of most postings, the bulleted list of requirements. Read it as a wish list, because that’s what it is. Several people contributed their “it would be great if they also had…” and almost nobody went back and cut it down to what the job truly needs.

The hiring manager’s real must-haves are usually two or three items, and they’re often near the top of the list — the skills mentioned first, mentioned again in the duties, or named in the first paragraph. Everything after that is a preference wearing a requirement’s clothes.

That’s also why the years-of-experience numbers are softer than they look. “Five years required” usually means “we want someone who won’t need this explained from scratch.” If you’ve done the core work — in a job, in training, on a project you can talk about in detail — you’re closer than the number suggests. The standing guidance from career advisors is consistent on this: if you meet most of the core skills, apply. Job ads describe the perfect candidate. Companies hire real ones.

Read the duties, not the title

The same job wears five different titles at five different companies. “Associate,” “specialist,” “coordinator,” “analyst,” and “technician” can all describe identical work — and sometimes the grander title pays less because a smaller company hands out titles instead of raises. Title inflation and deflation are both real, so compare postings by their duties, not their names.

The duties paragraph is where the actual job hides. The first two or three responsibilities listed are usually what you’ll spend most of your week doing. Anything described with specific tools, specific people, or specific outcomes is probably real. Anything that could be pasted into any company’s posting unchanged — “collaborate with stakeholders,” “wear many hats,” “thrive in a dynamic environment” — is boilerplate, and it tells you nothing except that nobody proofread it with you in mind.

Reading the salary band

Where a range is posted, read it in thirds. Employers generally expect to hire somewhere in the lower-to-middle part of a band for someone growing into the role, and reserve the top for candidates who check nearly every box and can start at full speed. So if your experience honestly matches most of the posting, picture yourself landing around the middle, not the ceiling — and if the bottom of the range is below what you can accept, that’s real information worth having before you invest hours in applying.

Red flags worth respecting

None of these is automatic, but each one deserves a question:

• The unpaid “trial project” that’s really free work. A short skills exercise is normal. Producing something the company can actually use, unpaid, over several days, is not an exercise — it’s an invoice they declined to pay.
• Three jobs in a trench coat. “Fast-paced environment” plus a duty list spanning what are clearly three separate roles usually means the last person quit and they’re hoping one hire absorbs all of it.
• The evergreen posting. The same role re-listed for months on end may mean a team that can’t decide, a budget that isn’t approved, or a listing kept up just to collect résumés. Apply if it fits — but don’t arrange your hopes around it.

Green flags worth noticing

• A named team and real tools. “You’ll join the four-person support team using X and Y” means someone specific is waiting for help.
• A clear first-year outcome. “By month six you’ll own…” tells you the manager has actually pictured the job.
• Duties written in plain language. Clear writing about work usually means clear thinking about it.

Then make your moves

Three things, in order. First, mirror the posting’s honest language: if they say “ticket queue” and you’ve run a ticket queue, use their words — not to game anything, but because the person (or software) scanning your application is matching against this document. Only mirror skills you genuinely have; the interview will find the rest. Second, in your application or cover note, answer the two or three real requirements up top, plainly: here’s the core thing you need, here’s where I’ve done it. Third, save a copy of the posting — a screenshot or a PDF — the day you apply. Postings vanish when the listing closes, and the exact text is gold when you’re preparing for the interview a week later.

The 60-second decode

• ☐ Find the two or three real must-haves (listed first, repeated in the duties)
• ☐ Count the duties honestly — is this one job or three?
• ☐ Ignore the title; compare duties across companies instead
• ☐ Split the salary band in thirds; picture the middle
• ☐ Check the dates — posted last week, or re-listed since spring?
• ☐ Scan for one green flag: named team, named tools, or a first-year outcome
• ☐ Save a copy of the posting before you apply

A posting isn’t a test you pass or fail before you’re allowed to try. It’s a committee’s best guess at what help looks like. Read it for the job underneath — then answer that job, in its own words, with what you’ve actually done.