How to read a job description critically

A job description is a marketing document. Companies write them to attract candidates, not to describe the job accurately. If you treat the JD as ground truth, you'll over-filter yourself out of roles you'd be great at and waste time on roles you'd hate. Here's how to read between the lines.

Signal 1: How many "must-haves" are there?

A short list (3–5 hard requirements) usually means the team knows what they need and will hire someone who hits those points. A long list (10+ "must-haves") usually means the JD was written by committee and HR copy-pasted bullet points from three different intake forms. The hiring manager probably cares about 3 of those 10. Apply if you hit most of them.

The tell: scan for phrases like "experience with X, Y, Z, and ideally A, B, C." That "ideally" is the recruiter's way of admitting the second list is wishlist, not requirement.

Signal 2: Does the JD describe outcomes or activities?

Outcome-focused JDs ("you'll own the latency budget for our checkout flow", "you'll bring our deploy time below 10 minutes") signal a team that thinks about impact. They'll evaluate you on whether you've delivered comparable outcomes elsewhere — the specific tech stack matters less.

Activity-focused JDs ("you'll write unit tests, attend stand-ups, and document your code") signal a team that's filling a seat. Compensation tends to be lower and the work less interesting. Doesn't mean don't apply — just calibrate your expectations.

Signal 3: Vague comp, ambiguous title

Roles labeled "Software Engineer (Full-Stack)" with no level qualifier and a salary range like "competitive" are red flags in disguise. Either the company is hoping to underpay a senior or hire a junior they'll lean on heavily. Ask for the level (II, III, Senior, Staff) and the band on the recruiter screen. If they can't answer, the role isn't well-defined and you're being scoped during the loop.

Signal 4: The "we're a family" tax

Flowery culture sections that talk about family, hustle, ownership of "your impact" — without ever mentioning compensation, promotion paths, or how decisions get made — usually indicate companies where soft benefits are doing heavy lifting because hard benefits are below market. There's no rule that says skip these; just notice the trade you're being offered.

How to use the signals during application

For each role you're seriously considering, before you tailor a CV:

1. Highlight the must-haves vs. wishlist. Tailor to must-haves.
2. Note the outcomes (or absence of them). Mirror the language in your bullet points where you can — recruiters are scanning for it.
3. Identify the 1–2 must-haves you don't fully meet. Decide your narrative for them on the spot, before the recruiter screen.

The goal isn't to game the system. It's to spend your application energy on roles where the JD is honest, and to walk into the recruiter call already knowing which questions you need to ask.