DECODE A
JOB DESCRIPTION.

JDs hide the things that matter most. Title vs scope. Real comp band. Red flag phrases that signal trouble. Here's how to read one in five minutes — before you spend Sunday tailoring your resume to the wrong role.

Most candidates read a job description top-down: title, summary, responsibilities, requirements. They scan for fit, then start tailoring.

This is the wrong read. By the time you've decided to apply, you've already accepted everything the JD says about the role. Including the parts that aren't true.

The right read is forensic. You're looking for the gap between what the JD says and what the role actually is. Once you can see that gap, you decide whether to apply, what to lead with if you do, and what to ask in the first conversation.

Step 1 — Test the title against the scope

Title inflation is the most common JD lie. The posting says "Director of Engineering." The responsibilities describe a team of three engineers and a product roadmap that one IC could own. That's not a Director job. That's a Senior IC with people-management aspirations.

Test by reading the responsibilities first, with the title hidden. Ask yourself: at what level have I seen people do this work? If the answer is "Senior IC" but the title says "Director," there's a gap. The role is title-inflated.

The reverse happens too — title-deflated roles where the title says "Senior Manager" but the scope reads like a VP role. Common at flat startups. Less common, but worth catching: it usually means high autonomy and high upside if you can deliver.

The verdict matters because:

Step 2 — Estimate the real comp band

A growing fraction of JDs include a comp band. Most don't, or list a range so wide it's meaningless ("$180K–$300K"). When the band is missing or padded, you have to estimate it before applying — otherwise you're walking into a negotiation blind.

The estimate comes from four signals:

  1. Title and level. A Senior PM at a Series B is a different number than a Senior PM at FAANG. Calibrate to the company, not the title in isolation.
  2. Location signals. "Remote, US" usually pays the same nationally. "Bay Area / NYC only" pays a premium. "Hybrid, two days a week" usually means the location-anchored band.
  3. Equity language. "Significant equity" at a Series B means low cash, hopeful equity. "Competitive equity" at a public company means the cash is the real comp.
  4. Comparable peer roles. What did the equivalent role pay at the same stage company last year?

You don't need precision. You need to know whether the band the recruiter quotes you in week two is in the right neighborhood — or whether they're trying to anchor you 25% below the real number.

Step 3 — Scan for red flag phrases

JDs use a specific vocabulary that signals trouble. The phrases sound innocuous — sometimes even positive — but they're load-bearing. Each one means something the company isn't saying out loud.

The translation key:

Two or three of these in one posting is a yellow flag. Four or more is a structural issue with the company, not a one-off awkward phrasing.

Step 4 — Find the buried real requirements

JDs have a fake-requirements section and a real-requirements section. The fake requirements are the ones that read like a checkbox: "BA degree," "5+ years experience," "strong communication skills." Most candidates fit those. They don't predict who gets the offer.

The real requirements are buried lower. They show up in the responsibilities section, in qualifying language ("ideally with experience in..."), and in the "nice to have" list. These are the actual filters the hiring manager cares about.

An example: a JD for a Senior PM role. The fake requirements section says "5+ years of product management experience." The real requirements, scattered through the responsibilities, are: B2B SaaS specifically, multi-tenant architecture exposure, billing systems experience, and "ability to work cross-functionally with engineering and finance." That last one is the tell — finance is in the conversation, which means this role is closer to revenue ops than pure product.

Read for those buried details before you tailor. They tell you what your resume needs to lead with.

Step 5 — Decide before you apply

After the four reads, you have enough to make a real call:

Why this saves your weekends

Most candidates spend 30–60 minutes tailoring a resume per application. If you decode the JD first and pass on the bad ones, you're applying to half as many roles — and the half you do apply to are well-fit. Response rates go up. Sunday afternoons come back.

Ari decodes JDs for you. Paste the posting — Ari extracts the title-vs-scope verdict, estimates the real comp band, surfaces the red flag phrases, and tells you whether to apply or pass. Free. Decode a posting →

JD decoder

Stop applying
to the wrong roles.

Paste any job description. Ari pulls the buried truth in five seconds.

Decode a posting →
← All posts