How to read a startup job ad for what it is not saying

A wide range ($140k–$220k) usually means the company hasn't leveled the role precisely yet, or is flexible on seniority. A narrow, specific band suggests they know exactly who they want and where that person sits.

The width of the band is also a rough proxy for how much negotiating room actually exists. A band that spans eighty thousand dollars usually means the eventual number depends heavily on how you interview, not just on the role — which cuts both ways. It's good news if you interview strongly; it means the company hasn't already decided where you'll land before you start.

“Meaningful equity” with no number attached is worth asking about directly — it can mean anything. Startups confident in their numbers tend to state a range or a percentage; vagueness here is worth a direct question, not a guess.

Funding announcements are the least reliable stage signal in a job ad, because they're often stale by the time you're reading them — a “recently raised Series A” line can be eighteen months old. Equity language tends to be fresher, because it's usually written closer to when the role actually opened, and companies that are comfortable with their numbers tend to say so plainly.

A role on a two-person team will look nothing like the same title on a team of fifteen, regardless of what the ad promises. Ask directly how big the team is today and what the hiring plan looks like.

This is where the gap between the ad and the reality shows up most often. “Join our engineering team” can mean joining a team of two where you'll be doing infrastructure, product, and support in the same week, or joining a team of twenty where your scope is genuinely narrow. Neither is wrong, but they're very different jobs, and the ad usually won't tell you which one you're looking at.

We track how candidates describe their experience against the ad language that attracted them, across every search we run. A few patterns hold consistently enough to be worth watching for before you apply.

The requirements section of a job ad is written to filter applicants at scale, which means it's often broader and vaguer than the role actually is — “5+ years of experience” frequently means “we'll consider 3 if everything else is strong,” and a long list of nice-to-have technologies usually reflects the full stack of the team, not what any one person is expected to touch daily.

The description of day-to-day responsibilities is usually more honest, if you read it for what's listed first versus last. Ads tend to lead with what the team is most proud of or most excited about, and bury the less glamorous parts of the role further down — which is worth noticing, since the less glamorous parts are often the bulk of the actual week.

Not every gap in a job ad is worth worrying about, and treating all vagueness as a warning sign leads candidates to talk themselves out of good roles unnecessarily. A young company that hasn't nailed down a precise comp band yet, or hasn't finalized exactly which tools the team will standardize on, is usually just early — that's normal, not concerning.

The pattern worth actually treating as a signal is vagueness specifically on the things that are cheap to be specific about: what the person would work on in month one, who they'd report to, and roughly what success looks like at 90 days. A company that can't answer those three plainly in a first conversation isn't just early-stage, it likely hasn't thought through the role — and that's a meaningfully different, more concerning kind of unclear.

We coach every candidate we work with through the specific ad for a role before they engage, and the same handful of questions come up in almost every conversation, regardless of function or seniority.

None of this is about catching a company out — startups aren't obligated to put everything in a job ad, and most vagueness is a function of an early-stage company genuinely not having settled every detail, not an attempt to mislead. The fix is simply asking directly, early, rather than inferring and hoping.