Job description templates

Job Description Templates for Indian Employers

Six complete, role-specific job descriptions you can copy and adapt — each with its own screening signals, its own failure modes, and notes on how the wording changes your ATS matching.

A job description does three jobs at once, and most postings only do the first. It has to describe the work accurately enough that the right people recognise themselves in it. It has to disclose enough about pay structure, location and process that the wrong people stop reading. And it has to give your screening — human or automated — something specific to match against. A JD that fails the second and third jobs still fills your inbox; it just fills it with applications you will spend weeks rejecting.

The anatomy of a job description that works

Every template in this set follows the same structure, because the structure is what makes a JD usable by candidates, by your interview panel and by your screening tools. The content inside each block is entirely role-specific.

A one-line company description that says what you do and who buys it — not your values, and not your funding.
A role summary in plain prose: what this person owns, who they work with, and what success looks like in the first quarter.
Responsibilities written as the actual work, in the order the person will encounter it. Six to ten lines. If you cannot get under ten, the role is two roles.
Must-have requirements, separated from nice-to-haves and kept genuinely short. Every line here should be something you would reject an otherwise strong candidate for lacking.
Nice-to-have requirements, which is where everything you were about to over-specify belongs.
Qualifications, stated honestly — including where you would accept demonstrated ability instead.
Experience band as a range, with a line about what you will do with a candidate slightly outside it.
Location and work model, with the actual expectation. "Hybrid" without a number of days is not a disclosure.
Compensation structure — the mechanics if not the figures — plus notice period and anything like a bond or service agreement.
The process: how many rounds, what happens in them, and roughly how long the whole thing takes.

Pick your role

Each page below contains a complete template plus guidance you cannot get from a template alone: how to adapt it for your organisation, the screening signals that actually separate strong applications for that role, the JD wording that repels good candidates in that specific market, and how the phrasing changes keyword matching.

Software Engineer

Stack depth over stack breadth. The JD that attracts engineers who ship and filters out keyword collectors.

Open the template

Data Analyst

The role most often mis-scoped as a data scientist. Fix the scope and the pipeline fixes itself.

Open the template

HR Manager

Lifecycle ownership, not talent acquisition with a bigger title. Scope it by headcount supported.

Open the template

Sales Executive

Early attrition is a JD problem. Disclose field-vs-inside and lead source up front.

Open the template

Business Analyst

Requirements and process ownership, with domain as the real filter. Not a data analyst.

Open the template

Digital Marketing Manager

Scope the channel mix and the budget authority, or you will hire a generalist by default.

Open the template

The four mistakes that repeat across every role

The role-specific pages cover role-specific problems. These four appear everywhere.

Requirement inflation. The band says three to five years and the must-have list describes someone with eight. This happens during drafting, when everyone adds a requirement and nobody removes one. Read the must-haves back against the band before publishing and cut anything a person at the bottom of the band could not hold.
Undisclosed terms. Bond or service agreements, variable-heavy pay, mandatory shift patterns, a location that will change — all of it surfaces eventually. Disclosing it in the JD loses you applicants you were going to lose anyway, at the cheapest possible point in the process.
Boilerplate where the specifics should be. "Fast-paced environment", "self-starter", "wear many hats" and "rockstar" appear on so many Indian postings that they now carry a negative signal: candidates read them as a posting nobody thought about. Every one of those lines is a sentence you could have spent describing the actual work.
Two roles in one posting. If the responsibilities span two crafts — analysis and engineering, HR and recruiting, performance marketing and brand — you will get applications from people who do one of them and interview them against a standard nobody meets. Split the posting or narrow the scope.

How your job description changes your ATS matching

If you screen with any kind of matching tool, your job description is not just a candidate-facing document — it is the query. Everything you put in it is weighted, which means padding the requirements list actively degrades your shortlist by raising the score of candidates who list many things and lowering the relative score of the specialist you actually want.

Two general rules apply to every role. First, name things the way candidates name them, including old and alternate forms — parsers are more string-sensitive than vendors admit, and a resume that says "Google Analytics" will not automatically match "GA4". Second, do not list anything you do not need, because every unnecessary requirement produces high-scoring false matches that you then pay to reject by hand. The role pages carry the specific vocabulary for each function.

Frequently asked questions

How long should a job description be?: Most effective postings land somewhere between 400 and 700 words. Length is rarely the problem — padding is. If your JD is long because it describes the product area, the process and the pay structure, that is length doing work. If it is long because of three paragraphs about being a dynamic self-starter, cut those and the document improves in every dimension at once.
Should we publish salary in the job description?: Publishing a band widens your funnel and reduces late-stage drop-off, but many Indian employers prefer not to. The workable middle is to publish the structure without the figures: fixed versus variable, what triggers variable pay, whether equity is part of the package, and what notice period you can accommodate. Candidates need the mechanics to evaluate an opportunity, and withholding them tends to resurface as declined offers.
Can we use these templates as-is?: You can copy them freely, but do not post them unedited. Every template has bracketed placeholders where your specifics belong — the stack, the headcount, the territory, the channels, the process. A template posted with the brackets still in it is worse than no template, and the adaptation guidance on each page is the part that does the real work.
How many requirements should a job description list?: Aim for four to six must-haves and as many nice-to-haves as you like. The discipline is in the must-have list: each line should be something you would genuinely reject an otherwise excellent candidate for lacking. Most lists fail that test on at least half their entries, and each failing line is narrowing your pipeline for nothing.

Once the role is posted

Screening, offers and campus — the rest of the hiring cycle.

Offer letter format

The components a job offer letter usually carries, the difference between an offer letter and an appointment letter, and the omissions that cause offers to be declined or disputed later.

Resume screening guide

A working method for shortlisting at scale: build the scorecard first, run two passes, know which filters are real and which are proxies, and calibrate before you trust anyone's judgement

Campus hiring guide

How campus recruitment actually runs in India

JD Screening

Score applications against your own job description

Profile Analysis

Requirement-level gaps behind every match score

HR Partner Program

Earn a payout on every placement you close

Screen against the JD you just wrote

JD screening scores incoming applications against your own job description and shows the requirement-level gaps behind every score.

Explore JD screening Become an HR partner

All HR & recruiter resources

The anatomy of a job description that works

A one-line company description that says what you do and who buys it — not your values, and not your funding.

A role summary in plain prose: what this person owns, who they work with, and what success looks like in the first quarter.

Responsibilities written as the actual work, in the order the person will encounter it. Six to ten lines. If you cannot get under ten, the role is two roles.

Must-have requirements, separated from nice-to-haves and kept genuinely short. Every line here should be something you would reject an otherwise strong candidate for lacking.

Nice-to-have requirements, which is where everything you were about to over-specify belongs.

Qualifications, stated honestly — including where you would accept demonstrated ability instead.

Experience band as a range, with a line about what you will do with a candidate slightly outside it.

Location and work model, with the actual expectation. "Hybrid" without a number of days is not a disclosure.

Compensation structure — the mechanics if not the figures — plus notice period and anything like a bond or service agreement.

The process: how many rounds, what happens in them, and roughly how long the whole thing takes.

Pick your role

The four mistakes that repeat across every role

The role-specific pages cover role-specific problems. These four appear everywhere.

Requirement inflation. The band says three to five years and the must-have list describes someone with eight. This happens during drafting, when everyone adds a requirement and nobody removes one. Read the must-haves back against the band before publishing and cut anything a person at the bottom of the band could not hold.

Undisclosed terms. Bond or service agreements, variable-heavy pay, mandatory shift patterns, a location that will change — all of it surfaces eventually. Disclosing it in the JD loses you applicants you were going to lose anyway, at the cheapest possible point in the process.

Boilerplate where the specifics should be. "Fast-paced environment", "self-starter", "wear many hats" and "rockstar" appear on so many Indian postings that they now carry a negative signal: candidates read them as a posting nobody thought about. Every one of those lines is a sentence you could have spent describing the actual work.

Two roles in one posting. If the responsibilities span two crafts — analysis and engineering, HR and recruiting, performance marketing and brand — you will get applications from people who do one of them and interview them against a standard nobody meets. Split the posting or narrow the scope.

How your job description changes your ATS matching

Frequently asked questions

How long should a job description be?

Most effective postings land somewhere between 400 and 700 words. Length is rarely the problem — padding is. If your JD is long because it describes the product area, the process and the pay structure, that is length doing work. If it is long because of three paragraphs about being a dynamic self-starter, cut those and the document improves in every dimension at once.

Should we publish salary in the job description?

Publishing a band widens your funnel and reduces late-stage drop-off, but many Indian employers prefer not to. The workable middle is to publish the structure without the figures: fixed versus variable, what triggers variable pay, whether equity is part of the package, and what notice period you can accommodate. Candidates need the mechanics to evaluate an opportunity, and withholding them tends to resurface as declined offers.

Can we use these templates as-is?

You can copy them freely, but do not post them unedited. Every template has bracketed placeholders where your specifics belong — the stack, the headcount, the territory, the channels, the process. A template posted with the brackets still in it is worse than no template, and the adaptation guidance on each page is the part that does the real work.

How many requirements should a job description list?

Aim for four to six must-haves and as many nice-to-haves as you like. The discipline is in the must-have list: each line should be something you would genuinely reject an otherwise excellent candidate for lacking. Most lists fail that test on at least half their entries, and each failing line is narrowing your pipeline for nothing.