How to Write a Job Description: Guide & Templates

How to Write a Job Description: Templates & Guide (2026)

The job description is the most underrated document in hiring. It is the first impression a candidate forms of your company, the brief that aligns the hiring manager and recruiter, the yardstick against which applicants are screened, and, later, the reference point for setting expectations and evaluating performance. Get it right and you attract the right people and repel the wrong ones efficiently. Get it wrong, with a vague wishlist of impossible requirements or a copy-pasted template nobody read, and you drown in irrelevant applications, deter great candidates, and start the relationship on a foundation of confusion.

Most job descriptions are bad. They are written in a rush, padded with boilerplate, list a dozen "must-have" requirements that no real person possesses, and tell the candidate nothing about what the job is actually like or why anyone would want it. In a competitive talent market, a lazy job description is a self-inflicted wound. A well-crafted one, by contrast, is one of the highest-return investments a hiring team can make, because it improves the quality of applications before a single interview happens.

This guide explains how to write job descriptions that work: what they are for, the anatomy of an effective one, how to write each section so it attracts the right people, the language and inclusion choices that matter, the mistakes that quietly sabotage your pipeline, and ready-to-adapt templates. It is written for HR professionals, recruiters, founders, and hiring managers in India and similar markets who want to hire better and faster. The principles are evergreen; the examples are illustrative and meant to be adapted to your own roles and context.

What a job description is for

Before writing, it helps to be clear about the jobs a job description does, because they pull in slightly different directions and a good description balances them.

It is a marketing document. Hiring is a two-way sale; the best candidates have options, and the description must give them a reason to apply. This means conveying not just what you need but what is in it for them, the work, the growth, the team, the impact.

It is a filter. A good description attracts the right people and discourages the wrong ones, reducing the volume of unsuitable applications that waste everyone's time. Clarity about what the role genuinely requires does more filtering than any screening question.

It is an alignment tool. Writing it forces the hiring manager and recruiter to agree on what the role actually is, what success looks like, and which requirements are real. Many bad hires trace back to a hiring manager and recruiter who never agreed on the brief.

It is a legal and fairness artefact. The description sets out role-relevant criteria, which supports fair, defensible hiring decisions and reduces the room for bias. It also becomes a reference for the employment relationship that follows.

Holding these four purposes in mind while writing keeps you from producing a document that serves none of them, which is what a thoughtless template does.

The anatomy of an effective job description

A strong job description generally contains the following elements, in roughly this order. The exact structure can flex by role and company, but these are the load-bearing parts.

Job title. Clear, conventional, and searchable. This is not the place for clever internal jargon or inflated titles. Candidates search for standard terms, so a "Customer Success Manager" will be found where a "Client Happiness Ninja" will not. The title should accurately reflect the level and nature of the role.

A short hook or summary. One or two sentences at the top that capture what the role is and why it matters. This is your chance to earn the candidate's attention before they scroll. A flat "We are seeking a candidate to fill the position of..." wastes it; a crisp statement of the role's purpose and impact earns the next thirty seconds.

About the company and team. A brief, honest description of what the company does, the team the role sits in, and what makes it a worthwhile place to work. Candidates are evaluating you; tell them who you are without resorting to clichés about being a "rockstar family."

What you will do (responsibilities). The core duties of the role, written as concrete activities and outcomes rather than a vague list. This is the heart of the description and deserves the most care.

What success looks like. Increasingly common and highly effective: a short statement of what the person will achieve or be measured on in the first six to twelve months. This clarifies expectations and attracts outcome-oriented candidates.

What we are looking for (requirements). The skills, experience, and qualifications genuinely needed, ideally separated into true must-haves and nice-to-haves. This section, done badly, is where most descriptions go wrong.

Compensation and benefits. Transparency here is increasingly expected and pays off in application quality. At minimum, indicate the benefits and, where possible, a salary range, which saves everyone time and signals fairness.

Logistics. Location, work model (on-site, hybrid, remote), employment type, and how to apply. Candidates need these basics to self-select.

Equal opportunity and inclusion statement. A genuine commitment to fair, inclusive hiring, which both reflects your values and widens your applicant pool.

Writing the responsibilities section

The responsibilities section fails most often by being either a vague abstraction or an exhaustive, unreadable list. The fix is to describe a manageable number of meaningful responsibilities, typically five to eight, each expressed as a concrete activity tied to an outcome.

Compare two versions. The weak one says: "Responsible for marketing activities and supporting the team as needed." This tells the candidate nothing. The strong one says: "Plan and run monthly demand-generation campaigns across email and paid channels, owning the pipeline target for the segment" and "Partner with the sales team to define and report on the metrics that matter to revenue." The second version conveys scope, ownership, and what the work actually involves.

Lead each responsibility with an action verb (plan, build, own, lead, analyse, partner) and, where you can, attach the why or the outcome. Avoid the trap of listing every conceivable task; a description that lists twenty responsibilities reads as either an unrealistic role or a company that has not thought clearly about the job. Prioritise the responsibilities that define the role and group or omit the trivial ones.

Be honest about the real work. If the role is 60% execution and 40% strategy, say so, rather than dressing up a heavily operational role as a strategic one. Candidates who arrive expecting one thing and find another leave quickly, and the description is where that mismatch is either created or prevented.

Writing the requirements section: the must-have trap

If there is one section that quietly destroys hiring pipelines, it is requirements. The classic failure is the wishlist: a long roster of "essential" skills, years of experience, and qualifications that, taken together, describe a person who does not exist or would never apply for this role. The damage is twofold. It deters strong candidates who meet most but not all criteria (and research consistently shows some groups, including many women, are more likely to self-select out when they do not meet every listed requirement), and it gives screeners a pretext to reject good applicants on technicalities.

The discipline is to separate genuine must-haves from nice-to-haves, and to be ruthless about what is truly essential. Ask, for each requirement: would I actually reject an otherwise excellent candidate who lacked this? If not, it is not a must-have. Most descriptions can cut their "essential" list by half without losing anything real.

Be especially careful with proxies. "Degree from a top institution" and "X years of experience" are proxies for capability, and often poor ones. A rigid experience requirement screens out capable people who developed skills faster or differently, and pedigree requirements narrow your pool along lines that have little to do with performance. Where you can, describe the capability you need ("can independently manage a product roadmap and ship features") rather than the proxy ("5+ years as a product manager at a funded startup"). This shift toward skills-based requirements widens and strengthens your pool.

Frame requirements inclusively. Phrasing like "we would love for you to have, but do not require" around nice-to-haves, and an explicit note encouraging people who meet most (not all) criteria to apply, measurably increases the breadth and quality of applications.

Compensation transparency

For years, Indian job descriptions almost never mentioned salary, and many still do not. That is changing, and for good reason. Including a salary range, or at least a clear indication, improves application quality dramatically: candidates self-select based on whether the role fits their expectations, which saves both sides from advancing through multiple rounds only to part ways over pay. It also signals fairness and confidence, and aligns with the growing expectation of pay transparency.

If a precise range is not feasible, indicate the band, the benefits, and the components of the package. The worst option is total silence, which leads to mismatched expectations, wasted interviews, and the perception that the company is being cagey. Transparency is not just candidate-friendly; it is efficient, and efficiency in hiring is money.

Language, tone, and inclusion

The words you choose shape who applies. A few principles consistently help:

Write to the candidate, in plain language. Address the reader as "you," avoid corporate jargon and internal acronyms, and write the way you would speak. A description that reads like a legal contract repels; one that reads like a clear, respectful conversation attracts.

Check for biased or exclusionary language. Certain words skew applicant pools. Aggressively "masculine-coded" language (dominate, aggressive, rockstar, ninja) can deter women and others; overly narrow cultural references can exclude. Tools exist to flag gendered language, but a careful read with inclusion in mind catches most of it. The goal is language that invites the widest pool of capable people.

Avoid age, gender, and other discriminatory signals. Phrases like "young and energetic team" or "recent graduate preferred" can signal age bias; gendered pronouns for a role can signal gender preference. Keep criteria role-relevant and neutral.

Be honest, not hyperbolic. Overselling ("unlimited growth," "world-changing impact" for a routine role) breeds cynicism and sets up disappointment. Authenticity, including naming the genuine challenges of the role, attracts people who will actually thrive in it.

Common mistakes that sabotage your pipeline

Beyond the must-have trap, several recurring errors undermine job descriptions:

Copy-pasting a generic template. Reusing a stale description without tailoring it to the actual role produces a document that fits no one. Templates are starting points, not finished products.

Title inflation or obscurity. Inflated or quirky titles confuse candidates and hurt searchability. Use standard, accurate titles.

Burying the lead. Front-loading paragraphs of company boilerplate before getting to the role loses readers. Lead with what the role is and why it matters.

Listing tasks, not outcomes. A wall of duties with no sense of purpose or success criteria fails to engage. Tie responsibilities to outcomes.

No information on pay, location, or work model. Omitting the practical facts candidates need forces them to guess or skip, reducing relevant applications.

Ignoring the candidate's perspective entirely. A description written only as a list of what the company wants, with nothing about what the candidate gains, treats hiring as one-directional. The best candidates have choices; give them reasons.

Letting it go stale. Roles evolve. A description written two years ago and reused unchanged misrepresents the job. Refresh descriptions when you reopen a role.

A reusable job description template

Here is a structure you can adapt for most roles. Replace the bracketed prompts with role-specific content.

[Job Title] [One-line statement of the role and its impact, e.g., "Own and grow our customer onboarding so every new client succeeds from day one."]

About [Company] [Two or three honest sentences on what the company does, its stage and mission, and what makes the team a good place to work. Avoid clichés.]

About the role [A short paragraph framing where the role sits, who it works with, and why it exists now.]

What you will do - [Concrete responsibility tied to an outcome] - [Concrete responsibility tied to an outcome] - [Concrete responsibility tied to an outcome] - [Concrete responsibility tied to an outcome] - [Concrete responsibility tied to an outcome]

What success looks like in your first year - [A clear, measurable outcome for the first 6–12 months] - [Another outcome that signals the role is working]

What we are looking for (must-haves) - [Genuinely essential capability, described as a capability not a proxy where possible] - [Genuinely essential capability] - [Genuinely essential capability]

Nice to have (not required) - [Bonus skill or experience] - [Bonus skill or experience]

Compensation and benefits [Salary range or band, key benefits such as health insurance and retirement contributions, leave, flexibility, and any standout perks.]

Logistics [Location and work model (on-site / hybrid / remote), employment type, and how to apply.]

Our commitment to inclusion [A genuine equal-opportunity statement, plus an explicit note encouraging candidates who meet most, not all, of the criteria to apply.]

A worked example

To show the template in action, here is a condensed example for a mid-level role.

Customer Success Manager Help our customers get real value from our product, and turn them into long-term advocates.

About us: We build payroll and HR software used by hundreds of growing Indian businesses. We are a small, hands-on team that cares about our customers and about doing the work well.

About the role: As our customer base grows, we need someone to own the post-sale relationship for a portfolio of accounts, making sure customers onboard smoothly, adopt the product, and renew.

What you will do: Own onboarding for new customers so they are live and confident within their first month; build relationships across your portfolio and become their trusted point of contact; track adoption and proactively address risks before they become churn; gather product feedback and channel it to the team; and own renewal and expansion for your accounts.

What success looks like: Within a year, your portfolio renews at a healthy rate, onboarding time has shortened, and customers in your book are referenceable advocates.

Must-haves: You can build trust with business customers and communicate clearly; you are organised enough to manage many accounts without dropping the ball; and you can understand a software product well enough to guide customers through it.

Nice to have: Prior customer success or account management experience, and familiarity with HR or payroll.

Compensation: [Range], plus health insurance, retirement contributions, and flexible working.

Logistics: Hybrid, [city]. Full-time. Apply with a short note on why this role interests you.

Inclusion: We hire for capability and potential, and we welcome applicants from all backgrounds. If you meet most of the above but not every point, please apply anyway.

Notice that the example leads with purpose, describes outcomes rather than tasks, keeps must-haves to genuine capabilities rather than rigid proxies, and addresses the candidate directly. That is the difference between a description that works and one that merely exists.

Tailoring descriptions for different types of roles

A single template works as a backbone, but different role types reward different emphases, and good hiring teams adjust accordingly.

For technical roles, candidates are quick to spot vagueness and exaggeration. Be specific and honest about the stack, the kind of problems they will work on, the scale and stage of the systems, and the engineering culture (how decisions are made, how code ships, how much autonomy they will have). Strong technical candidates care about the substance of the work and the people they will learn from far more than about generic perks. Resist listing every technology your company has ever touched as a requirement; specify what truly matters and treat the rest as nice-to-have.

For sales and customer-facing roles, clarity on targets, territory or segment, the sales motion, compensation structure (including the variable component), and the support around the role matters enormously, because these candidates evaluate earning potential and whether they can succeed. Hiding the variable-pay structure or being coy about targets attracts the wrong people and loses the right ones.

For leadership roles, the description should speak to scope, mandate, the team they will inherit or build, the challenges the role exists to solve, and the autonomy and support they can expect. Senior candidates are assessing whether the role is real and resourced; a thin, generic leadership description signals an unserious or poorly defined mandate.

For entry-level and early-career roles, lower the barriers deliberately. Avoid demanding experience that contradicts the level, emphasise potential and learning, and be welcoming to candidates from varied backgrounds and institutions. Over-specifying requirements for a junior role is self-defeating, it screens out exactly the diverse, high-potential talent these roles should attract.

The underlying point is that the candidate's decision criteria differ by role, and the description should foreground what that audience actually cares about.

Job descriptions for remote and hybrid roles

As remote and hybrid work has become common, descriptions need to address it head-on rather than leaving it ambiguous. State the work model clearly: fully remote, hybrid with a specified number of office days, or on-site, and any location constraints (for example, whether a remote role is open across India or limited to certain time zones or cities). Ambiguity here wastes everyone's time, as candidates either assume the wrong thing or skip the role.

For remote roles especially, candidates also want to understand how the company makes remote work effective: communication norms, expectations around availability and overlap hours, and how a distributed team stays connected. A description that simply says "remote" without addressing how remote work functions leaves strong, experienced remote workers uncertain. A little detail here signals that the company has actually thought about distributed work rather than tolerating it reluctantly.

Measuring whether your description works

Like any document with a job to do, a job description can be evaluated and improved. The signals are readily available if you look. A high volume of clearly unsuitable applications suggests the requirements or framing are not filtering well. Very few applications, despite good distribution, may mean the requirements are too narrow or the role is undersold. A high drop-off when candidates learn about pay or location late in the process points to missing transparency in the description. And patterns in who applies, or does not, can reveal language that is narrowing your pool.

Treat the description as iterative. If a role attracts the wrong mix, revise the description before blaming the market or the sourcing channels. Small changes, sharpening the must-haves, adding a salary range, rewriting the hook, removing biased language, often shift application quality noticeably. Over time, a team that pays attention to these signals builds a library of descriptions that genuinely work, which compounds into faster, better hiring across every search.

From job description to the rest of hiring

A good job description does not end at the careers page. It feeds the rest of the process. The responsibilities and success criteria become the basis for structured interview questions, so you assess what the role actually needs rather than improvising. The must-haves become the screening criteria, applied consistently to every candidate, which supports fair and defensible decisions. And the same clarity carries into onboarding and the first performance conversations, where the description sets shared expectations.

This connectedness is why investing in the description pays off downstream. A muddled description produces muddled interviews, inconsistent screening, and confused new hires; a sharp one threads clarity through the entire hiring and onboarding journey. It is also why storing job descriptions in a structured way, linked to the requisition, the interview kit, and eventually the role's goals, beats scattering them across documents and inboxes.

There is also a feedback loop worth closing. When a new hire's early performance diverges sharply from what the description implied, that is information, either the description oversold or misrepresented the role, or the screening did not test for what the job truly needs. Reviewing a handful of recent hires against the descriptions that brought them in is a quick, cheap exercise that surfaces exactly where your descriptions are misleading candidates or your screening is missing the mark, and it makes the next version of each description measurably better.

Frequently asked questions

How long should a job description be? Long enough to be clear, short enough to be read, usually a page or so. The aim is to cover the role, requirements, and what is in it for the candidate without padding. If a candidate has to wade through endless boilerplate to find the substance, it is too long; if they cannot tell what the job involves, it is too short.

How many requirements should I list? Fewer than you think. List only genuine must-haves, typically a handful, and separate them clearly from nice-to-haves. A long "essential" list deters strong candidates and is usually a sign the role has not been thought through. Ask whether you would truly reject an excellent candidate for lacking each item.

Should I include a salary range? Increasingly, yes. A salary range or band improves application quality by letting candidates self-select, signals fairness, and saves everyone time. If you cannot give a precise range, indicate the band and the benefits. Silence on pay tends to produce mismatched expectations and wasted interviews.

What is the difference between a job description and a job posting? A job description is the underlying definition of the role, its purpose, responsibilities, and requirements, often kept internally and used for hiring and performance reference. A job posting (or advert) is the candidate-facing version, which adds marketing, company context, and a call to apply. In practice the two overlap, and a well-written description can serve as the basis for the posting.

How do I make a job description more inclusive? Use plain, neutral language; remove gendered or age-coded terms; describe capabilities rather than rigid proxies like pedigree or exact years of experience; encourage candidates who meet most (not all) criteria to apply; and include a genuine equal-opportunity statement. These changes measurably widen and strengthen the applicant pool.

Should the hiring manager or the recruiter write the job description? Ideally both, together. The hiring manager knows what the role actually requires and what success looks like; the recruiter knows how to frame it to attract the right candidates and where the market is. Co-writing it also forces the alignment that prevents bad hires.

How often should job descriptions be updated? Whenever you reopen a role, and periodically for ongoing roles whose scope has shifted. Reusing a stale description misrepresents the job and attracts the wrong people. A quick refresh before each new search keeps it accurate.

Can I use AI to write job descriptions? AI can help draft and polish, but it should not write the description unsupervised. It tends to produce generic, boilerplate output and can introduce subtle bias. Use it as a starting point, then tailor it to the real role, check the requirements for honesty, and review the language for inclusion.

Conclusion

A job description is far more than an administrative formality. It is your first conversation with a candidate, the alignment between hiring manager and recruiter, the filter that shapes your applicant pool, and the foundation for fair screening and clear expectations. The difference between a thoughtless template and a well-crafted description shows up directly in the quality of people who apply and the speed with which you hire the right one.

The principles are simple to state and worth the discipline to follow: lead with purpose, describe outcomes rather than tasks, separate genuine must-haves from wishes, be transparent about pay, write to the candidate in plain and inclusive language, and keep it honest. Use the template and example here as a starting point, and adapt them to your roles and voice.

If keeping job descriptions consistent, linked to your interview kits and screening criteria, and connected through to onboarding and performance sounds like more than scattered documents can handle, a modern HRMS with an applicant tracking system can hold it all together. If that would help your team hire more clearly and fairly, it may be worth seeing how CozyHR brings job descriptions, hiring, and onboarding into one connected flow.