How to tell which job postings are worth your time

Applying to fewer jobs only helps if you pick the right ones. Here’s how to read a posting before you spend an hour on it: what the requirements list is really telling you, how to spot a repost, and when to stop reading.

---

The question “apply to fewer” leaves open

Two weeks ago we made the case for sending fewer, better applications. The fair response to that is a question we didn’t answer: fine, which ones?

That question is harder than the advice makes it sound. Cutting your application count doesn’t help if you cut the wrong half. And the usual guidance here is close to useless, because it tells you to apply to jobs you’re excited about and qualified for, which you already knew and which describes far more listings than you have hours for.

So here’s the version that’s actually operational. A job posting is a document. A person sat down and wrote it, usually quickly, usually under pressure to get the req live. What they wrote leaks a lot about how well-defined the role is, how far along the hiring process already is, and whether the thing on your screen is an opening at all. You can read most of that in about two minutes, before you commit to the hour it takes to apply properly.

Somebody wrote the posting, and you can usually tell who

Listings come from a few different places, and they read differently.

Some are written by the hiring manager, the person whose team has a hole in it. Those postings tend to name a specific problem, because the problem is the reason the req exists and it’s the thing on that manager’s mind.

Some are assembled by a recruiter from an internal template, often by copying the last posting for a similar title and editing the parts that changed. Those read generic in the responsibilities section and oddly specific in the requirements section, because the requirements got carried over from a role that isn’t quite this one.

And some are posted by a staffing agency that doesn’t name the client, sometimes for a role they don’t have exclusively, sometimes for a role that’s already down to final candidates. Those read like a category rather than a job.

Which of these you’re looking at matters more than any individual line in the list, because it tells you what your application is walking into.

The specificity test

Here’s the fastest filter we know. Ask whether the posting describes work or describes a person.

A posting that describes work says things like: you’ll own the migration off the legacy billing system, the team is four engineers and you’d be the second hire on the backend side, the first six months are about getting the reporting pipeline off nightly batches. Someone who understands the job wrote that. They have a defined problem, they know what the first months look like, and the interviews will be about whether you can do that specific thing.

A posting that describes a person says you’re a self-starter who thrives in a fast-paced environment and collaborates cross-functionally. Nothing in that sentence tells you what you’d do on a Tuesday.

The second kind isn’t automatically a bad job. Plenty of good roles have a lazy posting in front of them. But it’s a worse use of your hour, for a practical reason: you can’t tailor an application to a posting that doesn’t say anything. You’ll write something general, it’ll read general, and it’ll land in a pile where a recruiter is scanning for fit with this exact role. Vagueness in the posting raises your effort and lowers your return at the same time.

When you have 20 open tabs and time for four applications, sort them by this. The specific ones first.

Requirements lists tilt in one direction

Treat the requirements section as a wish list that survived a committee, because that’s usually what it is. It gets padded during approval, it inherits lines from older reqs, and often nobody who currently does the job reads it before it goes live.

The tells are easy to spot once you look for them. A list that asks for more years of a technology than the technology has existed was not proofread. A list that wants two backend languages, a frontend framework, a cloud certification, and design experience is describing three jobs that got merged to fit one headcount. Neither is a reason to skip the posting. Both are a reason to weight that section lightly and read the responsibilities section instead, which is harder to pad because it has to describe work someone actually needs done.

There is one exception worth knowing. When a requirement appears in both sections, or appears again in the “about you” paragraph, they mean it. A licence, a clearance, a specific certification, or physical location stated twice is a real filter, and applying without it is the one case where you’re genuinely wasting the hour.

Reposts, evergreen listings, and the careers page check

Posting age gets treated as a strong signal and it isn’t one. A listing that’s been up for six weeks might be a stalled search, a slow approval chain, or a role that’s simply hard to fill. Any of those can still hire you.

Reposting is more interesting. If the same title at the same company keeps resetting to “posted three days ago” month after month, one of a few things is happening: the search is genuinely stuck, the team is churning through candidates and rejecting them, or the listing is evergreen and exists to collect resumes rather than to fill a seat this quarter. A stuck search can be good news, because a team that hasn’t found anyone in three months is more open to a candidate who doesn’t match the list exactly.

The check that resolves most of this takes 30 seconds: find the role on the company’s own careers site. If it’s there with a req ID and a recent date, it’s a real opening someone is accountable for. If it exists only on aggregators, you may be looking at a scrape of a listing that closed, or an agency posting a role they’re hoping to win. The gap between what’s on a job board and what’s on the employer’s site is one of the most reliable signals available to you, and almost nobody checks it.

The same goes for postings that never name a team, never name a manager, use a title with no level attached, or quote a salary band wide enough to cover two career stages. Those are pipeline listings. They aren’t a scam and there’s no harm in a resume drop, but give them 10 minutes and no tailored cover letter. Save the hour for a posting that has a person behind it.

What a missing salary range costs you

A posting with no pay range isn’t necessarily hiding something. In plenty of places it’s still the default, and in some it’s a legal question the company hasn’t sorted out.

What it does is move a cost onto you. You’ll write the application, prepare for the screen, and take the call before you learn whether the number works. That’s fine when the rest of the posting is strong and the role is one you want. It’s a bad trade when the posting was already vague, because now you have two unknowns and the same finite hour.

The practical move is to ask in the first conversation, early and plainly, rather than treating it as an awkward end-of-process topic. If a recruiter can’t or won’t give you a band on a screen call, you’ve learned something useful about how the rest of the process will go.

What the ones that pass deserve

Stop reading when you can’t say in one sentence what problem you’d be solving. Stop when a hard requirement appears twice and you don’t have it. Stop when the posting names no team, no manager, and no work, and you’ve already got better tabs open.

For the ones that make it through, the whole point of screening this hard is that you now have time to do the application properly. Read the posting again. Use its words for the things you’ve actually done. Note why this one is on your list, because that note is the answer to the first question of the screen call. And keep track of what happens, so that after a month you can look back and see which titles and sources actually converted rather than guessing.

That’s the loop JobHawk is built around. It surfaces a focused set of matches a day instead of a fire hose, tracks what you sent and what came back, and preps you for the interviews that come out of it. The screening still happens in your head. We just make it cheaper to act on what you decide.

Try JobHawk free →