Fifteen Bullets and No Salary: An Audit of What American Job Listings Get Wrong

The Most-Read Document You Never Edit

Most organizations spend weeks refining a careers page and roughly ten minutes pasting a job description into an applicant tracking system. That description then goes out to Indeed, LinkedIn, and a handful of niche boards, where it competes for attention against hundreds of near-identical listings.

Candidates do not read postings the way hiring managers read them. They scan them on a phone, in a hallway, between other obligations, and they form a judgment in well under a minute. More often than not, that judgment is a quiet rejection — not because the role is unappealing, but because the listing makes it impossible to tell what the role actually is.

What follows is an audit of the failures that recur across retail, logistics, healthcare support, skilled trades, and professional services listings, followed by a framework for rewriting them.

Failure One: The Requirement Pile

Requirement lists grow by accretion. A duty is added, a preferred certification is appended, and no one removes the bullet that stopped mattering two reorganizations ago. The posting ends up asking for a bachelor's degree, five years of experience, and fluency in a software platform the company retired last spring.

Candidates with options read that list as a warning about how the department is managed. Candidates without options apply anyway, which means the pile does not widen the funnel — it simply changes its composition. Researchers have documented degree inflation extensively: requirements creep upward while the actual work stays the same, and the gap between the two is where good applicants quietly disappear.

A useful discipline is to separate what a person genuinely needs on day one from what would merely be pleasant. Four true requirements will outperform fifteen aspirational ones every time.

Failure Two: The Missing Number

A growing list of states — California, Colorado, Washington, New York, and others — now require employers to publish pay ranges. But the expectation has outrun the statute. Listings without a number are read as either underpaid or evasive, and both readings cost applications.

Omitting the range does not preserve negotiating room. It shifts the negotiation to the candidate's imagination, where the assumed figure is usually higher than the offer and the resentment arrives before the first interview. Publishing a defensible band, with a sentence about how the band is determined, does more for credibility than any paragraph of culture language.

Failure Three: The Language of Nobody

Postings are littered with coded phrases that candidates have learned to translate. Each one is a small subtraction from trust.

None of these phrases describe work. They describe an atmosphere the author hopes exists. Replace them with specifics: the size of the team, the volume the department handles, the systems in use, the reporting line, and the cadence of the week.

Failure Four: Terms Buried in Paragraph Six

The details that determine whether a candidate can actually accept a job are frequently scattered or absent: shift patterns, weekend rotation, on-call obligations, hybrid expectations, travel percentage, physical demands, and whether benefits begin on day one or day ninety. A warehouse listing that omits the fact that the second shift runs until midnight has not protected its applicant pool; it has guaranteed that a portion of it will quit in week two.

Practical terms belong near the top, in plain language, not paraphrased into "flexibility required."

Failure Five: No Sense of Sequence

The hiring process itself is a selling point that most employers leave on the table. Candidates want to know how many conversations to expect, whether there is an assessment, whether it is paid, and how long the whole thing takes. Two sentences covering those points reduce withdrawal rates more reliably than a paragraph about mission.

A Four-Block Rewrite Framework

Block one: the reason the role exists. Two sentences. What problem does this position solve, and what does success look like after twelve months? This is the only part of the posting most candidates will read carefully, so it should not be wasted on the company's founding story.

Block two: six responsibilities, ranked. Verbs first, outcomes second. If everything is a priority, the candidate assumes nothing is. Rank them honestly, because the candidate will eventually discover which three actually matter.

Block three: two short lists. "What you need on day one" — no more than four items. "What would help" — no more than three. Everything else belongs in the interview conversation, where it can be discussed rather than enforced.

Block four: the terms. Pay range, work model, schedule, benefits eligibility, location, and the steps of the hiring process with a realistic timeline.

The Test That Matters

Every bullet should survive one question: does this describe the job, or does it describe the person we wish we could afford? If it is the latter, cut it.

There is also an internal check worth running before publishing. The posted range, the posted responsibilities, and the eventual offer must match. A candidate who receives an offer outside the published band does not simply negotiate — they reassess everything else the posting claimed.

If a candidate cannot understand the job on a phone in sixty seconds, the problem is not the talent market. The problem is the document. A posting that reads like a product page will always outperform one that reads like a compliance filing, and the difference shows up in who applies — and, more importantly, in who does not.