How to decode a job posting
before you apply

A job description is a negotiation document pretending to be a list of requirements. It was written in a rush by someone who was not the person you'd actually work for, approved by someone from HR whose job is to prevent legal risk, and edited one more time by a recruiter who needed the ticket closed. The finished product reads like it came from a template. Because it mostly did.

Underneath that template, though, there's usually quite a lot of signal, if you know where the signal actually lives. This is how to extract it before you spend forty minutes tailoring a letter for a role that was a mirage.

The signal isn't in the requirements list

The "5+ years experience with X, familiarity with Y, strong communication skills" section is the part most candidates read and the part that carries the least information. Those bullets were written by merging three template JDs and a resume of whoever last held the role. Treat them as loose guidance, not binding.

The signal lives in four other places: what's oddly specific, what's oddly missing, what's oddly worded, and what's in the benefits / company blurb at the bottom.

Oddly specific: the tells of what's actually broken

When a JD gets unusually specific about one thing, it's usually because the team had a bad experience last time.

• "Comfortable with ambiguity." Translation: the role is not yet defined, and the last person hated that. You are being warned. Whether you find this exciting or painful is a fit question.
• "Experience managing distributed teams across timezones." The previous person probably struggled with this, or the team had a painful remote transition. Ask how standups, on-call, and decision-making are actually structured.
• "Strong written communication skills" listed with unusual emphasis. Often means the role involves writing a lot of docs, or a lot of stakeholders are remote, or the last hire couldn't write well and it caused friction.
• "Thrives in a fast-paced environment." Has been diluted almost to meaninglessness, but still a real warning when paired with other pace-related flags (tight deadlines, rapid iteration, high velocity).
• A technology specified at a version level (e.g. "Postgres 14+", "React 18+") means they're either running exactly that version and are particular about it, or they just finished a painful migration and don't want someone who'll rewind them.
• A specific industry named (e.g. "prior experience in regulated healthcare environments") usually means the role has compliance requirements that will eat 20-40% of your time and they want to avoid surprising you later. Good to know before you say yes.

The rule: if a requirement is weirdly particular, ask about it in the first interview. The particular thing is almost always the thing you'd be absorbing every week.

Oddly missing: what the silence tells you

Sometimes the signal is in what should be there and isn't.

• No salary range in a jurisdiction that legally requires one → lazy posting, possibly a dated listing, possibly a role that's been open so long the recruiters aren't updating.
• No manager named, no team named in a senior role → either the hire will report up unusually high (exciting), or the team structure isn't fully settled (less exciting).
• Heavy on "you will" and light on "we have" → the team may be smaller or less established than the branding suggests. Ask what already exists.
• Benefits section is boilerplate at a company you'd expect to have distinctive benefits → maybe not the team's priority. Maybe the role is small in their org chart.
• No remote / hybrid / on-site specification → ambiguous on purpose. Assume they want on-site and haven't said so.

Oddly worded: the hedges and softenings

Good JDs commit. When they hedge, read the hedge.

• "Nice to have" and "bonus" requirements often matter more than they signal, because they're usually the specific skill a particular team member or hiring manager wanted.
• "Equivalent experience" after a degree requirement usually means they'll skip the degree for the right candidate, which means they mostly skip the degree and they know it.
• "Looking for someone who can hit the ground running" paired with a long stack of requirements means: there is no onboarding budget and you will be expected to produce in week one. Confirm this in interviews.
• "Looking for a self-starter" means: management bandwidth is thin. Confirm how often you'd actually see your manager.
• "Reporting structure is flexible" means: it has not been decided. Do not accept a verbal promise; get a written commitment before signing if it matters to you.

The benefits + company blurb: a surprisingly honest section

The bottom third of most JDs is the least-read and among the most useful.

• A long, specific list of benefits (parental leave specifics, mental health stipends, learning budgets, four-week vacations) usually signals a mature people function and a team that has had to compete on retention. That tends to correlate with a healthier workplace.
• A short, vague, "competitive salary and benefits" with nothing specific usually signals either a company that doesn't think about these things, or one that's trying to avoid commitment. Not a strict tell (some great teams are bad at writing JDs) but directionally informative.
• The "about us" paragraph is often copy-pasted across all JDs. Read three JDs from the same company and see if they feel written by the same team. If not, different sub-orgs probably have different cultures. Which one is this role in?
• A paragraph about "our values" that reads specifically ("we write design docs before coding, decisions go in writing") tells you something real. A paragraph that reads abstractly ("we value excellence, integrity, and ownership") tells you only that they hired a consultant.

The listing-age problem

Most candidates never check how long a role has been open. It is one of the most useful signals available.

• Under two weeks: fresh, probably well-funded, team actively engaged, reasonable response times.
• Two to six weeks: normal for most roles. Mid-funnel, the team is getting applications but hasn't made the hire.
• Six to twelve weeks: starting to smell. Either they're being picky (fine, often good), or they've interviewed several candidates who didn't convert (ask why in the interview, politely).
• Twelve weeks plus: something is off. Possible causes: the role keeps getting re-scoped, the hiring manager keeps rejecting everyone, budget is frozen and the post is live for compliance, or the comp is below market. All four are worth knowing before investing weeks of process.

LinkedIn shows posting date. Indeed shows age. Company career pages usually don't, so use the other channels.

The "cross-functional" test

A quick gut-check you can run on any JD: count the number of times the word cross-functional appears. More than twice means the role has a lot of coordination work and the team probably spends more time in meetings than on the craft work the title suggests. Fewer than zero (i.e., the JD never says it) in a role that's obviously cross-functional (PM, design, anything with stakeholders) means the team hasn't thought carefully about the shape of the role. Neither is disqualifying. Both are information.

What to do with all this

Before applying, skim the JD once for the four signals above. Underline the oddly specific phrases. Note the oddly missing pieces. Translate the hedges. Check the post age.

Then ask yourself: is this a job I want, or is this a JD that sounds like a job I want? The two are not always the same, and the answer changes your tailoring. A role you want gets a tailored application. A role that only looks good on the surface gets a generic one or none at all, because writing a custom letter for a role you won't take if offered is just expensive performance.

The ritual before you apply

Every candidate should have a pre-apply ritual. Ours takes about ninety seconds:

1. Find the specific thing this JD reveals they care about (usually an oddly specific bullet).
2. Find the specific thing this JD is hiding (the benefits gap, the missing team name, the listing age).
3. Decide: is the revealed thing attractive and the hidden thing acceptable? If yes, tailor. If not, move on.

Most of the time, this ritual will tell you the role isn't worth the twenty minutes. That's not a failure, that's the ritual doing its job. You want the twenty minutes going into the roles where the match is real.

If the decoding step is where the time goes (reading twenty JDs, figuring out which are real, tailoring for the ones that are), Jobiz does the filtering and the per-role tailoring, so the twenty minutes you do spend goes into the sentences no template can write.