How to Write a Job Description That Indian Candidates Actually Answer

The average Indian job description contains eleven bullet points of responsibilities, nine qualifications, one paragraph about a fast-paced dynamic environment, and no salary. Candidates read roughly the first four lines and decide. This is a guide to what belongs in those four lines.

What candidates are actually looking for

Four questions, answered in this order, in the first screen of the posting.

What would I actually do? Not the responsibility list. The real work: what they would build, own, fix or grow.
What does it pay? Skipped in most Indian postings, and it is the second thing every candidate wants to know.
Where do I have to be? Precisely. "Hybrid" is not an answer, it is a category.
Is this company worth leaving mine for? Stage, funding, team, product, whatever is genuinely true.

Lead with the work, in specifics

Compare two openings. "We are looking for a Senior Backend Engineer to join our fast-growing team and build scalable solutions." Versus: "You will own our payments service, which handles about 40,000 transactions a day and currently takes four hours to reconcile. The first project is cutting that to minutes."

The second tells an engineer whether this is interesting, whether they have done it before and whether they would learn something. The first is indistinguishable from every other posting, and indistinguishable postings compete only on brand and salary, which is a bad competition to enter if you are not the biggest name in the market.

Cut requirement inflation

This is the most damaging habit in Indian job postings. A list of twelve requirements, of which three are real, has an asymmetric effect: strong candidates who assess themselves honestly against the list decide they are not qualified and do not apply, while candidates who apply to everything are unaffected. You get fewer applications and worse ones.

Split the list explicitly. Must-have should contain only what cannot be learned in the role, usually two or three items. Everything else goes under nice-to-have, or is deleted. And drop the arbitrary experience floor where it is not real; "5 plus years" excludes the exceptional person with four who would have been your best hire.

Be honest about location, in India especially

Return to office is one of the most contested topics in Indian hiring, and vagueness here wastes everyone's time. "Hybrid" gets read as one or two days by the candidate and four by the employer, and that gap surfaces at offer stage when the candidate has already planned around a different life.

Write the actual expectation. Three days a week in the Bengaluru office, Tuesday to Thursday. Fully remote within India. Onsite in Gurugram five days. Candidates who cannot do it will not apply, which is the correct outcome, and those who do apply are not going to renegotiate it later. See our guide to remote and RTO hiring in India.

Publish a band

Most Indian postings omit compensation, and the usual reasons for this are weak. Candidates find out eventually, and the only question is whether that happens before or after four interview rounds.

Publish a range in LPA, and state the fixed component if the variable portion is significant, because a package that looks strong on CTC can be well below expectation on guaranteed cash. Our CTC guide explains why that distinction matters so much here.

Delete these

"Fast-paced, dynamic environment." Read by candidates as disorganised and understaffed.
"Rockstar", "ninja", "guru". Signals that the posting was not written by anyone who does the work.
"We are like a family." Read as a warning about boundaries.
Any responsibility that is simply the definition of the job title.
Three paragraphs about the company before anything about the role. Candidates scroll past them.

The posting is downstream of the brief

A job description is a public rendering of an internal document, and if the internal document does not exist, no amount of copywriting will save the posting. Write the brief first: the three things this person must deliver in a year, the genuine must-haves, the band, the location. The posting then writes itself in twenty minutes, and it also gives you something to source and screen against. Format in our hiring brief guide.

Turn a JD into a shortlist

Upload your job description and Talia turns it into a search, sources candidates and scores every one against the brief with the reasoning shown. Two free searches, no card.

Start a free search →

Frequently asked questions

What should a job description include?

Four things, in this order: what the person will actually work on in the first year in concrete terms, the compensation range, the location and office expectation stated precisely, and the genuine must-have requirements limited to those that cannot be learned on the job. Everything else, including boilerplate about company culture and long responsibility lists, is optional and mostly unread.

Should I include salary in a job description in India?

Yes, or at least a range. Indian postings frequently omit it, which means candidates self-select out through uncertainty or waste several rounds before discovering a mismatch. Publishing a band filters honestly on both sides, and in a market where candidates run several processes at once, the posting that answers the question first gets the application.

How long should a job description be?

Short enough that a candidate reads it on a phone between meetings, which realistically means under 400 words for the substantive part. Long descriptions are usually long because they list every task rather than describing the job. If you cannot explain the role in 400 words, the role is not defined yet, which is a bigger problem than the posting.

Why do qualified candidates not apply to my job posting?

Most often requirement inflation. Listing twelve must-haves when three are real suppresses applications from strong candidates who self-assess conservatively, while doing nothing to deter candidates who apply to everything regardless. The result is a smaller and worse applicant pool. Cut the list to what genuinely cannot be learned in the role.

Does a job description matter if I am sourcing candidates directly?

Yes, but differently. A passive candidate reads it after your outreach message interested them, so it functions as the proof rather than the hook. It has to answer, quickly, why this role would be better than their current one. A generic description at that moment loses a candidate your message had already won.