1. No Salary Range — The Instant Dealbreaker
You've written what you think is a perfect job description. Clear responsibilities. Tight copy. Great team culture. Then you post it and wait... and wait... and get nothing but spam from staffing agencies.
There's a good chance your salary field says "Competitive." That single word is doing more damage than you realize.
Over 40 US states now legally require salary ranges on job postings. But even where it's not required, candidates treat a missing salary as a red flag — because it usually means one of three things: the company lowballs, the range is embarrassingly wide, or the compensation depends on the candidate's desperation level. None of those signal "great employer."
The fix is simple. Add a range. Even a wide one ($90k–$130k) tells candidates whether to bother.
Compensation: Competitive salary and benefits, to be discussed during the interview process.
Salary: $110,000–$135,000/year depending on experience, plus annual performance bonus up to 15%.
Salary transparency isn't just good practice — it attracts better candidates who know their worth and aren't wasting your time. Transparent postings receive 30% more qualified applications according to recent hiring research.
2. The Requirements List That Never Ends
You want the perfect candidate. We get it. But when your requirements section reads like a rejection letter, you're not being thorough — you're being exclusionary.
A job description with 15+ requirements is a cry for help. It signals the company hasn't figured out what this role actually needs on day one, so they just listed everything they've ever thought of. Candidates read that list, realize they can't tick every box, and move on.
The math is brutal: each additional requirement eliminates 5–10% of your pool. That "nice to have" for 8 years of Python experience? It filters out every strong candidate who has 5 years of Python and 3 years of Go.
A job posting with more than 8 requirements typically sees a 40% drop in qualified applications. Candidates assume the company is disorganized or has unrealistic expectations.
The fix: split into "must-haves" (3–5) and "nice-to-haves" (2–3). Be honest about what you can train. Removing unnecessary requirements is one of the fastest ways to improve your candidate pool quality and diversity simultaneously.
Requirements: 5+ years React, 3+ years Node.js, AWS certified, PostgreSQL mastery, experience with microservices, agile experience, degree in CS or equivalent, excellent communication, detail-oriented, team player, self-starter, experience in fintech preferred.
Must-have: 3+ years React, basic Node.js, experience with relational databases.
Nice-to-have: AWS, fintech background, AWS certification.
What you can learn on the job: Our codebase, microservices patterns, internal tooling.
3. Responsibilities Written in Corporate Gobbledygook
"Lead cross-functional initiatives to drive strategic alignment and deliver value."
What does that actually mean? Nobody knows. Not you, not the candidate. These kinds of phrases are the hallmark of a job description written by committee, reviewed by legal, and approved by nobody who actually does this job.
When candidates see buzzword salad, they assume the company is either out of touch or deliberately vague — maybe to hide that the role is chaotic, the team is dysfunctional, or the job is nothing like what they're promising.
Specific, outcome-based responsibilities signal clarity and confidence. Vague phrases signal the opposite.
Replace every responsibility with the formula: Verb + Outcome + Context.
"Build and maintain REST APIs in Node.js that serve 500k+ daily requests, working with a team of 4 backend engineers." That's a real job. "Drive strategic initiatives" is not.
4. Job Titles That Mean Nothing
"Wizard Ninja Rockstar Wanted." We've all seen it. But even subtler title inflation kills your search visibility and candidate quality.
When a candidate searches "senior software engineer" and your "Principal Full-Stack Technology Architect" doesn't show up, you've lost them before they've read a word. Title inflation also attracts candidates who are chasing prestige, not fit.
Use standard titles unless you have a genuinely good reason not to. "Senior Product Manager" beats "Strategic Product Evangelist" every time.
Title: Growth Champion / Revenue Driver
Title: Senior Account Executive, Mid-Market SaaS
5. Culture Statements Written by a Bot
"We're a fast-paced, dynamic, innovative startup looking for rockstars who want to make an impact."
This describes literally every tech company founded between 2010 and 2023. It's the corporate equivalent of "I'm fun at parties." And candidates treat it with the same skepticism.
Worse, it often signals the opposite of what it promises: "fast-paced" often means "chaotic and burning people out." "Dynamic" usually means "unclear who does what." "Rockstars" means "we expect you to work 60 hours and call it passion."
Generic culture copy signals a company that hasn't thought about what makes their workplace genuinely different. Candidates read it as noise — and ignore it.
Instead, show how your culture actually works. For remote or hybrid roles especially, culture description is critical — candidates need to understand how collaboration actually happens day-to-day.
We offer a fun, fast-paced work environment with competitive benefits and a great team culture. We value innovation, collaboration, and excellence.
We work in 4-person squads, ship every two weeks, and run async standups — no daily syncs unless something's on fire. We have a $500/year learning budget, quarterly team offsites, and a documented handbook (not a wiki that hasn't been updated since 2021).
6. Formatting That Looks Like It Was Written in 2007
Inconsistent capitalization. Bullets that switch to dashes halfway through. Random bolding. Three font sizes on one page. A requirements section that starts at 14pt and ends at 10pt.
Formatting problems aren't cosmetic — they signal organizational carelessness. If the company can't be bothered to make their job description readable, what does that say about how they treat employees? Candidates draw a direct line.
Formatting is especially important on mobile. Over 60% of job seekers use phones to browse listings. If your description looks like a wall of text on a 375px screen, you're losing that audience entirely.
7. "Competitive Benefits" With Zero Specifics
Your benefits section says "We offer a comprehensive benefits package including health, dental, vision, 401(k), and unlimited PTO."
That sounds generous until the candidate realizes "health" means a $2,000 deductible HSA plan and "unlimited PTO" means their manager gets upset when they take more than 10 days.
Be specific. What does your health plan actually cover? What's your 401(k) match? Do you offer parental leave? Gym stipends? Remote work stipends? Home office setup budgets?
Benefits: Health, dental, vision, 401(k), unlimited PTO, and more.
Benefits: 100% covered health, dental, and vision for employees; 75% for dependents. 401(k) with 4% match, vested immediately. 16 weeks fully paid parental leave. $1,500 home office setup budget. $150/month remote work stipend.
Specific benefits are especially critical for remote and hybrid roles — candidates in different states or countries need to know what's actually available to them before spending time on a full application.
8. An Apply Process Harder Than the Job Itself
Your "easy apply" requires: a resume upload, a cover letter, answers to 12 questions (including "Where do you see yourself in 5 years?"), a LinkedIn profile URL, salary expectations, and availability for a 30-minute screening call before they've even seen the job description.
Every additional friction point in your application process eliminates candidates. The data is consistent: longer application processes see 30–50% higher drop-off rates. Top candidates — who have multiple opportunities — are the first to leave.
Ask only what you genuinely need at the application stage: resume and a 2-sentence cover letter (or 3 short questions). Move culture-fit questions to the interview stage. If your application takes more than 5 minutes, you're filtering out great people who won't bother.
The Data Behind These Red Flags
These numbers compound. A job description with vague language, 12 requirements, no salary, and a 15-minute apply process is effectively self-selecting for candidates with no other options. That's not a hiring strategy — it's a race to the bottom.
The 20-Minute Red Flag Fix
You don't need to rewrite everything from scratch. Here's a focused pass that addresses the highest-impact red flags in under 20 minutes:
The Checklist
- Add a salary range — even a wide one. "Competitive" tells candidates nothing.
- Cut requirements to 5 must-haves and 2 nice-to-haves. Add "what you can learn on the job" to expand your pool.
- Rewrite every responsibility as Verb + Outcome + Context. No buzzwords.
- Fix the job title — make it searchable and honest.
- Replace the culture paragraph with one concrete example of how you actually work.
- Detail your benefits — real numbers, real policies, no euphemisms.
- Test your apply flow — time yourself. If it takes over 5 minutes, simplify.
- Proofread for formatting — consistent bullets, clear sections, scannable headers. (ATS systems parse plain text much more accurately than tables or special characters — see the full ATS scoring guide for format details.)
If that feels like a lot to tackle manually, use JD Generator — it flags all 12 of these red flags automatically and generates a rewritten, bias-checked job description in under 60 seconds. Then you iterate from a clean foundation instead of a blank page.
See how JD Generator plans work — free tier lets you generate 2 job descriptions per month, Core gives you unlimited with bias checking and salary optimization.
Stop Losing Great Candidates to Bad Job Descriptions
JD Generator identifies and fixes every red flag in your job description automatically — salary, bias, formatting, and all.
Generate a Better JD — Free