After building a database that tracks every open role at 8,000+ startups, we've developed a pretty good sense of the patterns. Not just what JDs say — but what the gaps, the phrasing choices, and the structural decisions reveal about the actual job.

Here's the decoder ring.

Red Flag #1: "Wear Many Hats" Means There's No Team

When a JD says "you'll wear many hats," it sounds exciting. Cross-functional! Diverse challenges! Entrepreneurial!

What it usually means: you're the only person doing this function. "Wear many hats" in a marketing role means you're the entire marketing department. "Wear many hats" in an engineering role means there's no DevOps, no QA, no dedicated frontend — just you and maybe one other person.

This isn't necessarily bad. Some people thrive as generalists building from zero. But you should know what you're signing up for. The JD won't tell you the team size. Here's how to find out: check LinkedIn for the company's employees, filter by department. If the "Engineering" team has 3 people and they're hiring for a "Senior Software Engineer," you're employee #4, not joining a team of 20.

Red Flag #2: The Salary Range Is Suspiciously Wide

When you see "Compensation: $120K - $220K," that's not a range. That's two completely different jobs.

Wide salary ranges usually mean one of three things: the company hasn't decided on the seniority level (they'll hire junior or senior depending on who applies), the range is legally required and they've made it as broad as possible to avoid commitment, or the role's scope is genuinely undefined and will be shaped by whoever they hire.

In all three cases, the actual offer will cluster around the lower third of the range unless you're a perfect fit at the senior end. The $220K in a "$120K-$220K" range is the aspirational ceiling, not the expected midpoint.

How to decode: if the range spans more than 40%, treat the lower number as the real salary and the upper number as what you'd make after 2 years of promotions.

Red Flag #3: "Fast-Paced Environment" Is a Stress Warning

This phrase appears in roughly 15% of startup JDs. It's so common that most people skim past it. Don't.

"Fast-paced" is startup code for one of two things: either the company is genuinely growing quickly and the work is intense but rewarding, or the company is chaotic, understaffed, and burning through employees. The JD won't tell you which.

Here's the tell: look at the rest of the JD. If "fast-paced" appears alongside specific growth metrics ("we've grown 3x in the last year," "serving 2M users"), it probably means genuine momentum. If it appears alongside vague phrases like "dynamic team" and "passionate individuals," it's more likely chaos dressed up as culture.

Also check Glassdoor — not for the star rating (those are gamed), but for the specific phrases in negative reviews. "No work-life balance," "constantly shifting priorities," and "leadership changes direction weekly" are the translations of "fast-paced" that the JD won't give you.

Red Flag #4: The Role Has Been Open for 3+ Months

This one isn't in the JD at all — you have to look for it. But it's one of the most informative signals.

A role that's been posted for 3+ months means one of several things: the hiring bar is unrealistically high, the compensation is below market, the hiring manager can't make a decision, or the role is a "nice to have" that keeps getting deprioritized.

In our data, the median time a startup job stays posted is about 30 days. Roles that stay open for 60+ days have a significantly lower fill rate. They're not necessarily bad jobs — sometimes the company is being genuinely selective. But they're worth approaching with extra diligence.

How to check: many job boards show the posting date. If they don't, use the Wayback Machine or Google's cache to see when the listing first appeared. If it's been 90+ days, ask directly in the interview: "I noticed this role has been open for a while. What's made it challenging to fill?" The answer will tell you everything.

Red Flag #5: No Salary Listed (In 2026)

64% of startup jobs in our database don't list a salary. In 2026, with salary transparency laws in effect across Colorado, New York, California, Washington, and several other states, this is a deliberate choice.

Companies that don't list salaries are either: based in states without transparency requirements and prefer to negotiate from a position of information asymmetry, or technically compliant but listing ranges so wide they're meaningless (see Red Flag #2).

The absence of salary information correlates with lower-than-market compensation. This isn't always true — some well-paying companies omit salaries for competitive reasons. But statistically, companies that are proud of their compensation are more likely to advertise it.

What to do: use the salary data that does exist to calibrate. In our dataset, engineering roles with listed salaries have a median of $210K. If a company won't tell you the range, assume it's below that median until proven otherwise.

Green Flag #1: Specific Technical Challenges in the JD

The best JDs read like mini engineering blog posts. "We're migrating from a monolithic Rails app to microservices on Kubernetes, and we need someone to lead the database sharding strategy" tells you exactly what you'd be doing in month one.

Vague JDs ("build scalable systems in a collaborative environment") tell you the hiring manager either doesn't know what they need or doesn't respect your time enough to be specific.

Specific JDs also signal organizational maturity. A company that can articulate its technical challenges clearly has probably thought about them clearly. That's a good sign for your day-to-day experience.

Green Flag #2: The JD Mentions What's Hard

"This role is challenging because our data pipeline processes 2TB daily and our current architecture can't scale past 5TB" — this kind of honesty is rare and valuable. It means the company understands its problems, isn't trying to hide them, and trusts that the right candidate will be attracted to the challenge rather than scared off by it.

Companies that only list the exciting parts of the job are either naive or deliberately misleading. Every job has hard parts. The ones that acknowledge them upfront tend to be better places to work.

Green Flag #3: Clear Reporting Structure

"You'll report to the VP of Engineering and manage a team of 4" is infinitely more useful than "you'll work closely with cross-functional stakeholders." The first tells you your exact position in the org chart. The second tells you nothing.

Reporting structure matters enormously at startups because it determines your influence, your growth path, and your daily experience. Reporting to the CTO at a 50-person company is a completely different job than reporting to a team lead, even if the title and JD are identical.

The Meta-Pattern: JDs Reveal Company Culture

After reading thousands of JDs, the single most reliable signal isn't any specific phrase — it's the overall quality of the writing.

JDs that are well-written, specific, and honest tend to come from companies that are well-run, specific about their goals, and honest with their employees. JDs that are generic, buzzword-heavy, and vague tend to come from companies that are... exactly what you'd expect.

The JD is the first piece of content a company produces for you. If they can't be bothered to make it good, what does that tell you about the onboarding docs, the internal wiki, or the product itself?

Read the JD like a product review. The five-star reviews are useless. The three-star reviews — the ones that mention both pros and cons — are where the truth lives.