Job Description Template Guide for Indian Startups

Every founder and HR lead in India has lived this: you post a vacancy on a Monday, and by Friday your inbox holds three hundred applications, of which perhaps five are worth a phone call. Or the opposite happens, and nobody applies at all. In both cases the problem usually starts with one document. A well-built job description template gives you a repeatable way to write roles that attract people who can actually do the work, and politely filter out those who cannot. This guide walks through the whole process for Indian startups and SMBs in 2026, with ready-to-use templates, examples and checklists you can adapt today.

You do not need a dedicated recruitment team to do this well. You need a clear understanding of the role, an honest description of your company, and a structure that candidates can scan in two minutes on their phone. Let us build that, step by step.

Why your job description matters more than you think

A job description (JD) is not an administrative formality. It is the first piece of marketing your company puts in front of a candidate, and it is also the first piece of documentation for the employment relationship. It does several jobs at once:

• It attracts. Good candidates compare several openings at the same time. A vague or bloated JD loses to a clear one.
• It filters. A JD that states real requirements saves your team from screening hundreds of mismatched profiles.
• It aligns. Hiring managers, founders and HR often discover they disagree about the role only when writing it down. Better to find out before interviews begin.
• It sets expectations. Many early resignations come from a gap between what was promised and what the job turned out to be. The JD is where that gap starts or is prevented.
• It supports fairness. Documented, role-related criteria make it easier to evaluate candidates consistently and defend your decisions later.

For a startup or a small business, a bad hire is expensive in a way larger companies can absorb. One wrong sales executive or one wrong accountant can drain months of management attention. Spending an extra hour on the JD is among the cheapest risk controls you have.

What a JD is not

It helps to be clear about what a JD should not become:

• Not a wish list. Listing every skill you would love in an ideal candidate guarantees that nobody matches and many qualified people self-reject.
• Not a copy-paste of a competitor's posting. Their role, team, stack and pay are different from yours. Copying also tends to import their vague phrases.
• Not an appointment letter. The JD describes the role and the opportunity. Terms such as notice period, probation and compensation structure belong in the offer letter, though you can mention the broad ones.
• Not a legal shield. A JD supports good practice, but it does not replace proper employment documentation.

The anatomy of an effective job description template

Before looking at specific roles, here is the skeleton that works for almost every position. Treat it as your master job description template and customise from it.

Keep the entire posting between 400 and 700 words. Anything longer tends to lose readers, particularly those browsing on mobile, which is how a large share of job seekers in India browse. Treat that last point as a reasonable working assumption about your own audience, and check your own application analytics to see what your candidates actually use.

Step 1: Start with the role, not the template

The most common mistake is opening a blank document and typing "Responsibilities". Do the thinking first. Spend thirty minutes on these questions with the hiring manager.

Ask why the role exists

Complete this sentence: "We are hiring this person so that ______." The answer might be "our customer onboarding no longer slips by two weeks" or "payroll closes on the 28th without the founder checking every sheet". That sentence becomes the heart of your summary.

Define outcomes for the first 90 days

Candidates respond strongly to outcomes. Instead of listing duties, think about what a successful person will have achieved by day 30, day 60 and day 90. For example, for a payroll executive:

• Day 30: Shadows one full payroll cycle and takes over attendance data collection.
• Day 60: Prepares the payroll input and variance checks with review.
• Day 90: Runs a cycle independently and handles employee queries on payslips.

You do not have to publish this exact schedule, but it forces clarity and gives you strong interview questions later.

Separate must-haves from nice-to-haves

Take your draft requirements and sort each one into one of three buckets:

1. Cannot start without it. Without this, the person fails in the first month.
2. Can learn within three months. Training or mentoring can close the gap.
3. Would be a bonus. Helpful but not decisive.

Only bucket one belongs in must-haves. Bucket two goes into good-to-have or is left out entirely. Bucket three should be used sparingly. This one exercise often cuts a requirement list in half and widens your candidate pool significantly.

Talk to someone doing the job today

If a colleague already performs a similar role, ask them what a typical week looks like. Ask what surprised them and what they wish had been explained before joining. Their answers contain the details that make a JD feel real rather than generic.

Step 2: Choose a job title that people actually search for

Candidates search by recognisable titles. Creative titles such as "Growth Ninja", "Happiness Hero" or "Numbers Wizard" may feel on brand, but they hurt discoverability on job boards and confuse candidates about seniority.

Follow these rules:

• Use the market-standard title such as "Sales Executive", "Payroll Executive" or "Backend Engineer".
• Signal seniority clearly with words like Associate, Executive, Senior or Lead, and keep these consistent with your internal levels.
• Avoid stuffing several titles together, for example "HR Manager / Recruiter / Admin / Office Coordinator". That reads as a role that has not been thought through.
• Add the specialisation after a dash or in brackets if needed, for example "Software Engineer (Backend, Python)".
• Do not put salary or urgency in the title. "Urgent opening" and "Immediate joiner" add noise. If speed matters, say so in the body.

Consider that titles also carry meaning for the person's career. An honest, standard title helps the hire in their next job search, and good candidates notice when a company respects that.

Step 3: Write a summary that earns the next ten seconds

Most readers decide within the first few lines whether to continue. Open with the role's purpose and the impact, not with a paragraph about how fast you are growing.

Compare these two openings.

Weak: "We are a fast-paced, dynamic, rapidly growing organisation looking for a rockstar sales professional to join our passionate family."

Stronger: "You will be the first point of contact for small businesses exploring our HR software. You will run demos, answer questions and help owners decide if we fit, working closely with a team of three product specialists."

The second version is specific, tells the reader who they will talk to, and signals the working environment. It also avoids empty words. Phrases like "rockstar", "ninja", "fast-paced", "dynamic" and "self-starter" are so overused that they carry almost no information. Replace each with a concrete detail: how many projects, which tools, how many stakeholders, what pace in real terms.

Include a short, honest company paragraph

Candidates want context before applying. Include:

• What the company does, in one sentence a stranger would understand.
• Stage and size, for instance "a 40-person team" or "a bootstrapped company".
• Location and working style.
• One true thing about the culture, such as "we write decisions down" or "everyone joins a weekly customer call".

Avoid claims you cannot support. If you describe a flat hierarchy but every decision goes through the founder, new hires will notice in week one.

Step 4: Write responsibilities that describe real work

The responsibilities section is where many JDs fall apart. Common problems are bullets that are too generic ("handle day-to-day tasks"), too many (fifteen or more), or a hidden second job stuffed in at the end ("and any other work assigned by management").

Use this simple formula for each bullet: action verb + what + for whom or with what + why it matters.

• Weak: "Responsible for sales."
• Better: "Run product demos for small business owners and follow up within 24 hours to answer pricing and setup questions."

Practical rules for responsibility bullets

• Keep to five to eight bullets, ordered by importance and time spent.
• Start each with a strong verb: build, run, reconcile, review, coordinate, analyse, maintain.
• Mention tools, volumes and stakeholders when you know them, such as "process payroll for around 150 employees across two states".
• Include one bullet about collaboration, so candidates see who they work with.
• If the role truly includes unrelated admin or support work, say so plainly. Surprises damage trust.
• Skip phrases such as "other duties as assigned". If the role really is flexible, say "you will occasionally support X during peak weeks".

Step 5: Set requirements that are fair and defensible

Requirements are the part of a JD that most strongly shapes who applies. Overly strict or poorly chosen requirements shrink your pool and can exclude capable people for no good reason.

Be careful with degrees and years of experience

Ask yourself honestly whether a particular degree is needed to perform the work. For many roles in sales, operations, support and even software, demonstrable skills matter more than a specific qualification. Where a qualification is genuinely required, for instance a professional accounting credential for certain finance tasks, state it clearly and explain why.

Similarly, be sceptical of rigid experience numbers. "5 to 7 years" is often a stand-in for "someone who can work independently", which you can describe directly. Consider using ranges, or stating the level of independence expected.

Avoid biased filters

Requirements that have no connection to the work, such as a specific age bracket, a particular marital status, or a preferred gender for a role that does not require it, should not appear in a JD. They narrow your pool and create risk. See the inclusive language section below for more.

Distinguish skills from tools

Say "comfortable with spreadsheets and basic reconciliation" rather than naming one specific software package, unless your stack makes that package truly mandatory. Candidates who know one tool can usually pick up another.

Use this requirements checklist

Step 6: Be honest about work mode, location and hours

In 2026, candidates expect clarity on where and how they will work. Many applicants drop out when they find a hidden condition late in the process. State these plainly:

• Work mode: on-site, hybrid or remote, with the actual in-office days if hybrid.
• Location: city and, if relevant, the area or office. Commute matters in cities like Bengaluru, Mumbai, Pune and Delhi NCR.
• Working days and hours: including any shift or Saturday expectations.
• Travel: how often and to where, especially for field sales or implementation roles.
• Employment type: full-time, contract, internship or part-time. If it is a fixed-term contract, say so.
• Joining timeline: the notice period you can accommodate, or whether you are flexible.

If something is non-negotiable, such as a customer-facing role that requires presence at a client site, say it up front. Candidates respect this far more than a surprise during the final round.

Step 7: Compensation and pay transparency

Pay is the single most important detail for most job seekers, and the one most often hidden. Indian law does not currently require employers to publish a salary range in a job posting in the same way that some jurisdictions elsewhere do, but requirements can change, and expectations among candidates are moving quickly. Please verify the current rules for your state and sector, and consult a labour law professional where needed.

Regardless of legal minimums, publishing a range has practical advantages:

• It saves time for both sides. People outside your budget do not apply, and people inside it apply with confidence.
• It reduces negotiation friction and the awkward late-stage offer rejection.
• It supports internal fairness, because you must first decide what the role is worth.
• It builds trust with candidates who have been frustrated by "competitive salary" and "best in industry".

How to present pay in a JD

Be specific and use the language Indian candidates recognise:

• Fixed pay: state the annual CTC range, for example "6 to 8 LPA fixed", or the monthly range for junior roles.
• Variable pay: say what share is variable, how it is earned and when it is paid. For sales roles, explain the incentive structure briefly.
• Benefits: health insurance, provident fund, gratuity as applicable, leave policy, learning budget, flexible hours.
• Payment cadence: the usual salary date, which tells candidates you are organised.

If you cannot publish an exact range, a wide-but-honest band is still better than nothing. Avoid "negotiable based on experience" as the only line, since it communicates nothing.

Make sure your range is internally consistent

Before publishing, check the range against your current employees in similar roles. If a new hire will earn noticeably more than a peer doing the same work for the same time, you may create resentment and, in some cases, pay equity problems. A simple salary band per role and level, maintained in your HR system, prevents this. Remember too that Indian equal remuneration rules exist regarding men and women doing the same work, so confirm the current provisions that apply to you.

Step 8: Use inclusive language and fair criteria

Inclusive writing is not only about doing the right thing, although it is that. It also widens your talent pool, which matters when you are competing with larger employers.

Language to review and replace

Practical inclusion steps

• State your equal opportunity commitment at the end of the JD in plain words. Avoid hollow boilerplate; one sincere sentence is enough.
• Offer accommodations. Add a line inviting candidates with disabilities or specific needs to tell you what adjustments would help during the process.
• Welcome returners. Many skilled professionals return to work after career breaks, often women after caregiving. A line such as "We welcome applicants returning after a career break" signals that you will assess the skills, not the gap.
• Avoid unnecessary personal requirements. Do not ask for marital status, religion, caste, or photographs in a JD or at the application stage. These add risk and no value.
• Check the readability. Use plain English or offer a Hindi or regional language version for roles where it helps, such as plant, field or retail positions.
• Review the whole page, including the application form, for the same issues.

Employment law touching on non-discrimination, disability rights and equal pay can be detailed and updated over time. Verify the current provisions and any state-level rules with a qualified advisor rather than relying on a blog post, including this one.

Ready-to-use job description template examples

Below are three sample JDs you can copy and adapt. Replace the bracketed items with your own details, and revise the numbers to match your budget and market. The figures shown are placeholders for illustration, not benchmarks.

Template 1: Sales Executive (B2B SaaS, inside sales)

Job title: Sales Executive, Inside Sales

About the role You will be the first conversation small business owners have with [Company]. You will understand their hiring and HR needs, run demos of our product and help them decide whether we are a good fit. You will report to the Sales Lead and work closely with our customer success team.

About [Company] We build [product description] for small and mid-sized businesses across India. We are a team of [number], based in [city], and we speak to customers every week.

What you will do - Contact inbound leads within one working day and qualify their needs. - Run product demos, online or by phone, tailored to the prospect's business size. - Prepare and send quotes, and follow up until a decision is made. - Update every conversation in the CRM so the team has an accurate pipeline. - Share customer feedback and recurring objections with the product team each month. - Work with customer success for a smooth handover after the sale.

What you need - 1 to 3 years of experience in inside sales, preferably in software or services. (Strong freshers with a sales internship are welcome to apply.) - Clear spoken and written communication in English and Hindi, or another regional language used in your territory. - Comfort with CRM tools and spreadsheets. - A habit of following up and keeping accurate records.

Good to have - Experience selling to business owners or finance and HR teams. - Familiarity with subscription pricing.

Work details - Location: [City], [on-site or hybrid, with days]. - Hours: [Monday to Friday, 10 am to 7 pm], with no routine weekend work. - Compensation: [X to Y] LPA fixed plus [Z] LPA target incentive. Incentives are paid [monthly or quarterly] on closed revenue; the plan is shared in writing before you join. - Benefits: [health insurance, leave policy, learning budget].

Hiring process Intro call, a short role-play demo, a conversation with the Sales Lead, and an offer discussion. We aim to complete this within [two weeks].

Why this note matters: The example states the incentive mechanics and the process. Sales candidates in particular worry about opaque targets, so explaining how variable pay works reduces drop-offs.

Template 2: Payroll Executive

Job title: Payroll Executive

About the role You will make sure around [number] employees are paid accurately and on time every month. You will own the monthly input cycle, from attendance and leave data to payslips, and be the person employees trust for payroll queries. You will report to the HR and Finance Manager.

About [Company] [One or two lines on the business, size and locations.]

What you will do - Collect and verify attendance, leave, overtime and joining or exit data before each cycle. - Prepare payroll inputs, run the cycle and check variances against the previous month. - Process salary components, reimbursements, advances and deductions as per company policy. - Prepare statutory data for provident fund, ESI, professional tax and TDS, as applicable, and support timely filing with your manager and external advisors. - Maintain employee payroll records and respond to payslip queries within an agreed turnaround. - Support full and final settlements and year-end tax declaration collection. - Flag errors, process gaps and repeat queries so we can fix the cause.

What you need - 2 to 4 years of payroll processing experience, or a strong foundation in accounting with payroll exposure. - Working knowledge of Indian payroll components and statutory compliances (verify current rates and rules with your advisor; we will train you on our specific setup). - Strong accuracy and comfort with spreadsheets. - Ability to handle confidential data with discipline.

Good to have - Experience with an HRMS or payroll software. - Exposure to multi-state compliance.

Work details - Location: [City], [work mode]. - Peak workload: the last week and first week of each month. [Describe flexibility.] - Compensation: [X to Y] per month fixed. [Benefits.]

Hiring process HR conversation, a short practical exercise using sample payroll data, a discussion with the Finance Manager, and an offer.

Why this note matters: Payroll candidates are cautious about compliance liability. Saying who owns the filing, and that you will train on your setup, makes expectations realistic. It also tells candidates you view payroll as a controlled process rather than a one-person burden.

Template 3: Software Engineer (Backend)

Job title: Software Engineer, Backend

About the role You will build and maintain the services behind [product area], used by [type of users]. You will join a team of [number] engineers, take features from design through release and help improve reliability. You will report to the Engineering Lead.

About [Company] [Stage, product, team size, working style such as code reviews, release cadence, on-call arrangements.]

What you will do - Design, build and ship backend features and APIs in [language or framework]. - Write tests and take part in code reviews, as author and reviewer. - Investigate production issues, find root causes and fix them. - Improve performance, data models and monitoring for key services. - Document important decisions so teammates can follow them. - Work with product and design colleagues to refine requirements before you build.

What you need - 2 to 4 years building backend systems, or equivalent project experience. - Solid skills in [primary language] and a relational database. - Experience designing and consuming REST APIs. - Comfort with version control, testing and code review practices. - Clear written communication.

Good to have - Experience with cloud services, containers or message queues. - Open-source contributions or personal projects you can discuss.

Work details - Location: [City or remote], [time zone expectations and any overlap hours]. - On-call: [Describe honestly, for example "business-hours support rotation, compensated with time off".] - Compensation: [X to Y] LPA fixed. [ESOPs or bonus if offered, with a brief explanation.]

Hiring process Intro call, a take-home task that takes no more than [two to three] hours (compensated or optional if longer), a technical discussion, a team conversation and an offer. We share feedback with every candidate who completes a task.

Why this note matters: Engineers read JDs critically. Stating the on-call arrangement, task length and feedback policy earns credibility that a long list of frameworks never will.

How to adapt a job description template for any role

You can build a JD for any position, such as customer support, HR generalist, operations coordinator or accounts executive, by following a short routine:

1. Copy the master structure from the anatomy table earlier.
2. Write the one-sentence purpose of the role.
3. List five to eight responsibilities using the verb formula.
4. Sort requirements into the three buckets and keep only must-haves in the main list.
5. Add work details, pay range and process.
6. Read it aloud once, remove jargon, then review for inclusive language.
7. Ask someone outside the team to read it and describe the job back to you. If their summary differs from your intention, revise.

Entry-level versus senior roles: what changes

The same structure works across levels, but the emphasis shifts.

For fresher hiring in particular, describe the training plan. "You will spend your first four weeks shadowing" is more persuasive than "freshers can apply".

Where and how to publish your JD

A strong JD still needs to reach the right people. Practical distribution tips for Indian startups and SMBs:

• Post on a few relevant channels, not everywhere. Choose job boards suited to the role, professional networks, your own careers page and, for some roles, community groups and college placement cells.
• Keep one source of truth. Maintain a single approved version of each JD, and avoid letting edited copies float around WhatsApp groups.
• Make the first screen count. Title, location, work mode and pay range should be visible without scrolling.
• Use plain headings so job search engines can read the page.
• Simplify applying. A long form with ten mandatory fields kills applications. Ask for what you need to shortlist, and collect the rest later.
• Respond promptly. Acknowledge each application automatically and tell candidates when to expect an update.
• Track sources. Note where each hire came from so you can stop paying for channels that do not work.

Doing this by spreadsheet is possible for a handful of roles, but it becomes messy quickly. An applicant tracking system helps you keep JD versions, applications, interview feedback and offers in one place.

Common job description mistakes (and quick fixes)

A quality checklist before you hit publish

Run through this list for every JD.

Clarity - Does the title match what candidates search for? - Can a stranger explain the job after reading the first paragraph? - Are responsibilities limited to what the person will really do?

Fairness - Is every requirement linked to performing the work? - Is the language neutral and free from age, gender or background signals? - Have you offered accommodations and welcomed career returners?

Transparency - Is a pay range included, with fixed and variable parts explained? - Are work mode, location, hours and travel stated? - Is the hiring process and timeline described?

Practicality - Is the length between 400 and 700 words? - Does it read well on a phone? - Does the application link work, and does someone own the replies?

Measuring whether your JD works

A job description is a hypothesis: "if we describe the role this way, the right people will apply." Test that hypothesis using a few simple measures, tracked per role:

• Views to applications: a very low rate suggests the title, pay or first lines are not compelling.
• Applications to shortlist: a very low rate suggests the requirements are unclear or attract the wrong audience.
• Shortlist to offer: if many shortlisted candidates fail the same interview step, the JD may be hiding a real requirement.
• Offer acceptance: frequent declines often point to a pay or expectations gap.
• Early attrition: exits within the first few months can signal a mismatch between the JD and the actual job.

You do not need advanced analytics. Even a simple monthly review of these numbers for each role will show where to improve. After each hire, ask the new employee what in the JD was accurate and what was not. Feed the answers back into your master template so that every future posting benefits.

Keeping your JDs organised as you grow

Once you pass ten or twenty employees, role descriptions multiply. A few habits keep this manageable:

• Maintain a role library with a master JD for every position, including level and pay band.
• Version your changes and record who approved them and when.
• Reuse the JD after hiring as the base for the employee's role document, goal setting and performance reviews, so what you promised and what you measure stay linked.
• Review annually or whenever the role changes materially.
• Connect the JD to your HR data. When job titles, departments and levels are consistent across recruitment, payroll and performance, reporting becomes much easier.

This last point is where an integrated system pays off. If your recruitment tool and your payroll and HR records live in different places, every new hire means re-typing details and risking errors. When they connect, the selected candidate's information can flow into onboarding with far less rework.

Frequently asked questions

How long should a job description be?

Aim for roughly 400 to 700 words. That is long enough to cover the role, requirements, pay and process, and short enough to be read on a phone. For junior roles, lean towards the shorter end. For senior roles, you may need more detail about scope and decision-making, but avoid padding.

Should I include the salary range in the job description?

It is a good practice, and candidate expectations are moving that way. A range saves time and builds trust. Legal requirements around pay disclosure can vary and evolve, so verify the current rules that apply to your location and sector. If you cannot share an exact figure, give a realistic band rather than "competitive" or "as per industry standards".

What is the difference between a job description and a job specification?

A job description covers the role itself: purpose, responsibilities, reporting line and conditions. A job specification focuses on the person: qualifications, skills, experience and attributes. In practice, most modern postings combine both into one page, with responsibilities and requirements in separate sections, as in the templates above.

How many requirements should I list?

Keep must-haves to roughly four to six items, and limit good-to-have items to a few. If your list keeps growing, return to the three-bucket exercise: what is needed on day one, what can be learned in three months, and what is merely nice. Long lists discourage capable candidates, particularly those who tend to apply only when they meet nearly every point.

Can I use the same job description for hiring through consultants and for direct postings?

You can share the same core document, but adapt the opening and the application instructions for each channel. Give consultants the full detail, including pay range, must-haves, reasons the role is open and the hiring process, so that they pitch it accurately. Also ensure consultants follow your inclusive hiring standards, and confirm any fee or contract terms separately with them.

How do I make a JD attractive when I cannot match big-company salaries?

Be honest and specific about what you offer: faster ownership, direct access to decision-makers, clear learning plans, flexible working, a transparent growth path and prompt hiring decisions. Combine this with a fair pay range, and avoid exaggeration. Candidates who value those things will respond, and they are often more likely to stay.

How often should I update my job description?

Review it every time you open the role and at least once a year. Update it when your tools, team structure, location policy or pay band changes. After each hire, gather feedback from the new employee about what matched reality and what did not, and apply it to the master template.

Conclusion

A good job description is a small document with a big effect. It forces you to clarify the role, it gives candidates the information they need to decide, and it sets the tone for the working relationship. Start from the purpose of the role, choose a searchable title, write responsibilities that describe real work, keep requirements fair, share a pay range and work details honestly, and use inclusive language throughout. Then measure what happens and refine your job description template after every hire.

If you are tired of managing JDs, applications and interview feedback across spreadsheets and chat threads, it may be time to put the process in one place. CozyHR's recruitment and applicant tracking features are designed to help Indian startups and SMBs publish roles, track candidates and move hires smoothly into HR and payroll. Why not explore CozyHR and see whether it fits the way your team hires?