A mid-sized SaaS company in Bengaluru posted an AI Engineer role last year. Within 48 hours they had 1,200 applications.
They hired nobody.
Every resume looked impressive on the surface. Almost none had the hands-on experience the team actually needed. The role stayed open for three months. The hiring manager lost faith in the process. The recruiter burned out screening applications that were never going to work.
The job board was not the problem. The sourcing was not the problem. The job description was the problem, and it was the one thing nobody questioned.
Why Most Job Descriptions Attract the Wrong People
A job description has one job: make the right candidates want to apply and give everyone else a reason not to.
Most JDs do the opposite. They attract volume instead of fit, because they are written to cover every possibility rather than describe one specific opportunity clearly.
According to ManpowerGroup’s 2026 Global Talent Shortage Survey, 82% of Indian employers report difficulty filling roles despite record application volumes. The problem is not a shortage of candidates. It is a shortage of signal in the hiring process, and the JD is where signal breaks down first.
Here are the three mistakes that turn a job description into a volume generator instead of a fit filter.
Mistake 1 – Writing a wish list instead of a success brief
Most JDs are written by someone listing everything they could possibly want in a candidate. Eight years of experience. Five different frameworks. A degree from a top institution. Proficiency in tools the team has not even decided to use yet.
The result is a document that filters out strong candidates who do not tick every box, while attracting candidates who have learned to match keywords regardless of actual ability.
The fix is simple. Replace the wish list with a success brief. Instead of listing requirements, answer one question: what does this person need to accomplish in their first 90 days for this hire to be considered a success?
That answer becomes the core of your JD. Everything else is secondary.
Mistake 2 – Copying last year’s JD
This is the most common JD mistake in Indian mid-market companies, and the hardest to catch because it looks like efficiency.
The role has changed. The team has changed. The market has changed. But the JD still says what the last person in this seat was supposed to do two years ago. Candidates read it and self-select based on a role that no longer exists.
Before posting any role, read the existing JD and ask: does this describe what we actually need right now, or what we needed when we last hired for this? If the answer is the latter, rewrite from scratch.
Mistake 3 – Writing for HR compliance, not for candidates
JDs written for compliance purposes, to cover legal requirements, satisfy internal job-levelling frameworks, or match a salary band, read like policy documents. They describe the company’s needs in the company’s language.
Strong candidates, especially passive ones who are not actively looking, read a JD to answer one question: is this worth leaving my current job for? A document full of corporate language and generic responsibilities does not answer that question. It gets closed.
Research from 2026 hiring data shows that AI-generated JDs have made generic descriptions even more common, the differentiation now sits entirely in the human edit. The companies attracting the strongest candidates are writing JDs that feel like they were written by someone who actually understands the role, not generated from a template.
What a Right-Fit Job Description Looks Like
A JD that filters for fit rather than volume has four components:
A specific role title that matches what candidates actually search for, not an internal job level. “Senior Product Manager, Growth” performs better than “Product Manager III.”
Three to five must-have requirements, not ten to fifteen. Every requirement you add filters out a set of candidates. Be precise about what is genuinely non-negotiable and cut everything else.
A clear 90-day success statement, what will this person have achieved by the end of their first quarter for both sides to feel good about the hire? This single addition does more to attract the right candidates than any other change.
Honest compensation and context, average time-to-hire in India for senior roles runs 44 to 60 days. Candidates are evaluating multiple opportunities simultaneously. A JD that hides compensation or is vague about remote versus on-site expectations loses strong candidates at the first read.
How AI Helps You Write Better Job Descriptions
Writing a JD from scratch with all four components takes time most TA leaders and founders do not have, especially when managing ten open roles at once.
Talismatic’s AI job description generator does the first draft in minutes, structured around the role requirements, calibrated for the specific seniority level, and written in language that attracts the right candidates rather than every candidate. The output is not a template with blanks to fill in. It is a working JD built around what the role actually needs.
From there, the human edit brings in the company-specific context and the 90-day success statement that no AI can write for you. That combination, AI draft plus specific human edit, produces JDs that attract fit-first candidates and filter out noise before a single application arrives.
Sanju L, Global Head of Talent Acquisition at Zycus, found that improving JD quality upstream reduced the noise in the application pipeline significantly, which meant less screening time and stronger shortlists for hiring managers to review.
Fix the JD First. Everything Else Gets Easier.
Sourcing channels, screening tools, and interview processes all depend on having the right candidates in the pipeline. If the JD is attracting the wrong people, every step after it is working harder than it needs to.
Fixing the job description is the highest-leverage change a TA leader or founder can make to their hiring process — and it costs nothing except the time to write it properly.
See how Talismatic’s AI job description generator helps you attract the right candidates from day one. Book a 20-minute demo →
- Your Job Description Might Be Attracting the Wrong Candidates. Here’s How to Fix It.
- How to Hire Your First 10 People Without a TA Team, The Founder’s Practical Guide
A job description attracts the right candidates when it focuses on what success looks like rather than listing every possible requirement. Start with three to five must-have qualifications — not ten to fifteen. Include a clear statement of what the person should accomplish in their first 90 days. Use the role title candidates actually search for, not an internal job level. Be specific about compensation, location, and working model. Every vague or generic element is a signal to strong candidates that the role is not worth pursuing.
Too many irrelevant applications usually means the JD is written too broadly — listing too many requirements, using generic language, or failing to describe what specifically makes someone right for this role at this company. Candidates who are a poor fit apply when the description does not give them enough information to self-select out. Tightening the must-have requirements, adding a 90-day success statement, and removing generic language significantly reduces irrelevant volume.
AI is useful for generating the first draft of a job description quickly — especially for common role types. The limitation is that AI cannot know what success looks like in your specific team, culture, and context. The most effective approach is to use AI for the structural draft and then edit specifically for the 90-day success criteria, the team context, and the honest description of the opportunity. The human edit is where differentiation lives.
An effective job description for most roles is 300 to 500 words. Long enough to give candidates the information they need to make a decision. Short enough that a strong passive candidate — who is not actively searching — will read it in full. JDs longer than 700 words lose passive candidates at the scroll. Lists of more than five requirements signal a wish list rather than a clear brief, which reduces application quality.
