How to Write a Job Description That Attracts Great Candidates

A job description is the first piece of your company most candidates ever read, and for many roles it is the only thing they read before deciding whether to apply. Yet most JDs are written in twenty minutes by a hiring manager copying last year’s version, padded with a wish-list nobody actually possesses, and posted without a salary. The result is predictable: a hundred applications, four of them relevant, and a hiring manager complaining that “there is no talent in the market.”

There usually is talent. The JD simply failed to reach it or failed to convince it. This guide covers what goes wrong, what a strong job description actually contains, how to write titles that match what candidates search for, and how the JD shapes your shortlist downstream. As a recruitment agency in Mumbai that has run more than 5,000 placements since 2001, we see the difference a well-built JD makes within the first week of sourcing.

Why most job descriptions fail

• Generic to the point of anonymity. “A leading organisation seeking a dynamic professional” describes every company in India. If you deleted your logo, could a candidate tell your ad apart from a competitor’s?
• Internal jargon. Grade codes, product codenames and function names that mean nothing outside your building. Candidates cannot self-assess against language they do not understand, so they either skip the role or apply blind.
• The twenty-requirement wish-list. Ten years, four tools, three certifications, a specific domain. Hiring research has consistently reported that many strong candidates will not apply unless they meet nearly all listed criteria, while others apply regardless — so you filter out the careful and keep the ones who ignored the list.
• No salary, no location detail. Where a candidate is weighing a 30% hike against a 90-day notice period, an unstated CTC is a reason to deprioritise your role, not a reason to call and ask.

The anatomy of a job description that works

A strong JD is short, concrete and answers what candidates are actually asking: a two-line role summary, what success looks like in year one, four to six genuine must-haves, a separate nice-to-have list, a realistic experience band, a salary range, office location and hybrid policy, reporting line and team, growth path, and a clear process. Note what is missing — a values paragraph that could apply to anyone, and nineteen bulleted daily tasks. Those belong in an internal role charter, not a hiring advertisement.

Write outcomes, not a task list

The single biggest upgrade is replacing “responsibilities” with outcomes. Tasks describe motion; outcomes describe why the role exists — and they give your interview panel something concrete to assess against.

Must-have versus nice-to-have — and an honest experience band

Split requirements into two explicit lists and cap the must-haves at six. A must-have is something you would genuinely reject an otherwise excellent candidate for lacking on day one. Everything else — a specific tool, a certification, an MBA — goes into nice-to-have, where it signals preference without gatekeeping.

On experience, resist a single number. “8 years” reads as a hard filter to candidates and to search tools. Write “typically 6-10 years”, then add what those years must have contained: team size managed, deal sizes handled, scale of systems owned, P&L responsibility. Those tell you far more than a year count.

Pay, location and the details candidates screen on

Publish a range. The Indian objections are familiar — internal parity, existing staff reading the ad, negotiating leverage — but withholding costs you relevant applications, wasted interview hours and offers that collapse at the last stage. A published ₹18-26 LPA band filters your pipeline before you spend an hour on it.

Alongside pay, state the office micro-location (Lower Parel and Vikhroli are very different commutes), the hybrid policy in days rather than adjectives, the reporting line, team size and any travel. For confidential leadership mandates run through executive search some of this is deliberately withheld — but for mid-level permanent staffing roles, vagueness costs applications with no offsetting benefit.

Titles, search behaviour and inclusive language

Candidates search boards with conventional titles: “Java Developer”, “Business Development Manager”, “DevOps Engineer”. They do not search “Growth Ninja”, “Sales Rockstar” or your internal designation “Officer Grade M3”. If your internal title is non-standard, publish the market-standard one and keep the internal version for the offer letter. One qualifier is fine — “Senior Java Developer (Payments)” — but avoid stacking three.

On inclusive language, a few cuts do most of the work. Drop age and marital-status markers (“young and energetic”), gendered defaults (“he will manage”), unrelated physical requirements, and “aggressive”, “dominant” and “cultural fit” — the last of which invites unstructured bias. Replace each with the behaviour you actually want observed. Where the role genuinely involves travel or shift work, say so plainly; that is information, not exclusion.

A copy-ready job description skeleton

Keep the whole thing to 350-600 words. Most candidates read it on a phone, in under 90 seconds. Short paragraphs, bullets over prose, no wall of text above the fold.

1. Job title — market-standard, one qualifier maximum.
2. One-line hook — what the team does and why the role exists now.
3. Role summary — two or three sentences, no jargon.
4. Success in 12 months — three to five measurable outcomes.
5. Must-haves — four to six, each genuinely disqualifying if absent.
6. Nice-to-haves — clearly labelled as preferences.
7. Experience — a band, plus what those years must have contained.
8. Compensation — fixed CTC range, variable structure, ESOPs or allowances.
9. Location and working pattern — micro-location, days in office, travel.
10. Team and reporting line — manager, team size, key partners.
11. Growth path — the realistic next step and typical timeframe.
12. Process — rounds, format, turnaround, who to contact.

Frequently asked questions

Turning a better JD into better hires

A sharp job description is leverage: it improves who applies, gives your sourcing team something specific to pitch, and gives your panel a scorecard. It will not, on its own, reach passive candidates who are not browsing job boards — that needs targeted talent sourcing and a recruiter who can make the call. But without a clear JD, even the best sourcing is guesswork.

If you are hiring in Mumbai and want a second opinion on a role you are struggling to fill, we are happy to look at it. Ace Corporate Services has worked with over 500 client companies across 15+ industries, from IT recruitment to engineering and pharma. Call +91-22-67554705, email info@acecorpsers.com, or get in touch and we will tell you honestly whether the role is written to be filled.