Two Indian startup colleagues discuss hiring in a warmly lit office for a job description article.

Startup Job Descriptions That Attract A-Players

16 min read

A startup job description template in India should do one job: make the right candidate understand the mission, the work, the standard, the money, and the first 90-day outcome before they apply. Most founders publish bloated wish lists instead. That attracts desperate applicants, scares away strong operators, and wastes your runway in interviews.

Your job description is not HR paperwork. It is your first sales document to a potential employee. If it is vague, inflated, or dishonest, good candidates assume the company is the same.

What a startup job description template in India must contain

Use this structure for almost any early-stage role:

  1. Role title: Use a title candidates actually search for. “Founding Engineer” is clearer than “Technology Ninja”.
  2. Location and work model: State the city, remote policy, travel requirement, and expected working hours.
  3. Company context: Explain what you sell, to whom, and what proof you have.
  4. Why this role exists now: Tie the hire to a business problem, not a vague growth plan.
  5. Outcomes: Describe what the person must achieve in 30, 60, and 90 days.
  6. Responsibilities: List the five to seven highest-value activities. Do not dump every possible task.
  7. Must-have evidence: Ask for proof of capability, not a decorative degree list.
  8. Compensation: Give a realistic salary range and explain equity honestly.
  9. Hiring process: State the stages, expected timeline, and who the candidate will meet.
  10. Application request: Ask for something that helps you assess the work.

That is your template. The writing matters, but the decisions behind it matter more. A polished job description for a role you have not defined is still a bad hire waiting to happen.

Why most Indian startup job descriptions fail

Founders usually make one of four mistakes.

They describe a person, not an outcome

“We need a passionate, hardworking, self-motivated individual who can wear many hats” says nothing. Every applicant claims these traits. None of them tell you whether the person can reduce onboarding time, close enterprise accounts, ship a payments flow, or build a reliable supply chain.

Write the business problem instead:

  • “Our first 40 customers come through founder-led sales. You will build a repeatable outbound process and close the next 15 mid-market accounts.”
  • “Our app has 8% weekly crash-free sessions below target. You will own release quality and bring the crash rate below 1% within 90 days.”
  • “Our procurement team spends two days reconciling vendor invoices. You will automate the workflow for our top 50 suppliers.”

They advertise a fantasy role

One hire cannot be head of growth, product manager, content writer, data analyst, and customer support lead. Early employees will do different kinds of work. That is normal. Pretending the role has no boundaries is not.

Strong candidates want to know where they will spend their time. State the split. For example:

  • 60% enterprise sales and account expansion
  • 25% sales process and CRM discipline
  • 15% customer feedback and product input

This also exposes whether you are hiring one person or quietly trying to avoid hiring three.

They hide the difficult parts

If the role involves six days of travel each month, night calls with US customers, field visits in industrial areas, or selling to government buyers, say so. Do not wait until the final interview.

Indian startup candidates are not allergic to hard work. They are allergic to bait-and-switch hiring.

They copy a large-company specification

A seed-stage startup does not need a five-page list of competencies. It needs someone who can produce a measurable result with limited support.

Do not write “experience in cross-functional stakeholder management” when you mean “can get sales, product, and operations to agree on a launch date”. Use plain language. It filters better.

Startup job description template India: the version we would publish

Use the following as a working template. Replace the bracketed sections. Then cut anything you cannot defend in an interview.

[Role title], [City / remote]

Company: [Company name] helps [specific customer] solve [specific problem]. We currently have [proof: revenue, customers, pilots, retention, or distribution]. We raised [stage, if useful] and are building the next phase of the business.

Why we are hiring: [Explain the business bottleneck]. The founder currently owns [current workaround]. This hire will take ownership of [clear area] so the company can achieve [business outcome].

What you will own:

  • [Outcome or responsibility one]
  • [Outcome or responsibility two]
  • [Outcome or responsibility three]
  • [Outcome or responsibility four]
  • [Outcome or responsibility five]

Your first 30 days:

  • Learn [customers, product, process, or market].
  • Meet [specific internal and external stakeholders].
  • Audit [relevant funnel, codebase, operations, or sales pipeline].
  • Present a written plan for [measurable area].

Your first 60 days:

  • Ship or implement [specific deliverable].
  • Improve [metric] from [current state] towards [target].
  • Build the operating rhythm for [process].

Your first 90 days:

  • Own [business area] without daily founder intervention.
  • Deliver [specific result].
  • Show a repeatable method for improving [metric].

What we need:

  • Evidence that you have [must-have capability].
  • Experience with [relevant customer, channel, technology, or operating environment].
  • Comfort working with incomplete information and direct feedback.
  • Ability to make decisions without waiting for a large team.

What is useful but not required: [List only two or three items].

Compensation: ₹[range] fixed salary, plus [variable/equity details if applicable]. We will discuss the exact package based on relevant evidence and seniority. If equity is part of the offer, we will explain the number of options, vesting schedule, cliff, exercise price, and applicable company documents.

Work model: [Office days, location, travel, working-hour expectations].

Hiring process: [Application review] → [work sample] → [functional interview] → [founder discussion] → [references]. We aim to complete the process within [number] working days.

To apply: Send your CV and [one relevant work sample or a short answer to a role-specific question]. Please do not send a generic cover letter.

The most important section: the first 90 days

If you write only one section properly, write this one.

A candidate cannot judge a role from a list of ongoing duties. They can judge it from the first 90 days. This section forces you to answer three questions:

  • What will this person actually do after joining?
  • How will you decide whether they are succeeding?
  • What support will you provide?

It also prevents a common founder error: hiring someone for a problem that has no owner, no data, and no decision rights.

For a business development hire, “build partnerships” is weak. “Sign 10 active channel partners in Maharashtra, with at least five producing qualified opportunities by day 90” is testable.

For a product manager, “own the roadmap” is weak. “Interview 15 paying customers, reduce the backlog to a ranked list, and ship the highest-impact workflow with an agreed adoption metric” is useful.

Do not set targets you have not measured yourself. A founder who cannot explain the current baseline will lose credibility with an experienced candidate.

Rule of thumb: If you cannot write a credible 90-day outcome, you are not ready to hire for the role. You are trying to hire your way out of confusion.

Write outcomes, not a heroic task list

Responsibilities explain the work. Outcomes explain why the work matters.

Weak wording Better wording How to assess it
Manage social media Build a content engine that produces 30 qualified inbound leads per month Review channel data and prior experiments
Improve customer experience Reduce first-response time from 12 hours to under 2 hours Ask for an operating plan and sample dashboard
Work with the engineering team Turn customer problems into a prioritised weekly product queue Use a product case based on your actual backlog
Drive sales growth Close ₹25 lakh of new annual contract value in six months Test pipeline creation, qualification, and forecasting
Handle operations Cut order failure rate below 2% across the top three cities Ask for a root-cause and measurement plan

Use metrics where the metric is real. Do not manufacture precision to sound sophisticated. “Improve activation for new users” is acceptable if you explain how activation is defined and what data exists today.

Show candidates the actual startup, not the pitch deck

Your job description should answer the questions a sensible candidate will ask before leaving a stable job:

  • How much runway does the company have?
  • Who are the customers?
  • What has been built?
  • What is still broken?
  • Who will I report to?
  • What decisions can I make?
  • Why does this role matter now?
  • What happens if the next fundraise takes longer than expected?

You do not need to publish your bank balance. But do not write “backed by leading investors” as a substitute for business facts. If you have raised a seed round, say the stage. If you are bootstrapped, say so. If you have paying customers, name the category or give a count where confidentiality permits.

Strong candidates can handle risk. They cannot evaluate hidden risk.

Compensation: stop hiding behind “competitive salary”

“Competitive compensation” is lazy. It tells candidates that you want market information from them before revealing your own position.

For Indian seed-stage hiring, publish a range you can afford. For example, “₹18-24 lakh fixed, plus ESOPs” is useful. “Salary as per market standards” is not.

Your range should reflect:

  • Cash runway and planned burn
  • Role seniority and decision rights
  • City and office requirement
  • Scarcity of the skill
  • Whether the person is an early employee or a functional leader
  • Variable pay tied to controllable outcomes

Do not offer a senior title with a junior salary and expect equity to repair the gap. Equity is uncertain. Candidates price it accordingly.

If you offer ESOPs, explain the basics in writing:

  • Number of options or the percentage on a fully diluted basis
  • Vesting period and cliff
  • Exercise price
  • What happens when the employee resigns
  • Whether the grant is approved or subject to board approval
  • Tax implications, without pretending to give tax advice

Indian startup employees have seen promises disappear during funding rounds, exits, and departures. Clarity is part of compensation.

Requirements: ask for evidence, not pedigree

A degree from a famous college is not a proxy for startup performance. Nor is a decade of experience. Ask what the person has done.

Replace these filters

  • “IIT/IIM preferred”
  • “Excellent communication skills”
  • “Must be a team player”
  • “Minimum five years of experience”
  • “Entrepreneurial mindset”

With evidence such as

  • “Share a product, sales, or operations problem you owned from diagnosis to result.”
  • “Describe a time you changed a process without having formal authority.”
  • “Show one dashboard, memo, campaign, or code sample you are allowed to share.”
  • “Tell us the baseline, the action you took, and the measured result.”

Be precise about must-haves. A must-have should disqualify someone who lacks it. If you list 14 requirements, most are not must-haves.

Separate the posting into “must have” and “useful but not required”. This widens the pool without lowering the bar.

Do not confuse culture with obedience

“Culture fit” often means “will this person agree with me?” That is dangerous in a seed-stage company. You need people who can disagree, act, and recover from a wrong call.

Describe behaviours instead:

  • We write down decisions when they affect other teams.
  • We speak to customers before arguing from opinions.
  • We raise bad news early.
  • We prefer a small shipped test to a large internal debate.
  • We do not expect midnight availability unless the role explicitly requires it.

Do not claim “flat hierarchy” if every decision returns to you. Do not claim “ownership” if the employee cannot access data or approve a budget. Candidates notice the contradiction during interviews. The best ones withdraw.

Choose the right distribution channel

A job description cannot rescue a role nobody relevant sees. But posting everywhere is not a hiring strategy.

Role Best first channel Why
Founding engineer Founder network, technical communities, referrals Trust and technical signal matter more than application volume
Sales or business development Targeted referrals, LinkedIn outbound, industry networks Relevant customer access matters more than generic startup interest
Operations Employee referrals, local networks, specialist recruiters Reliability and context often beat polished CVs
Entry-level roles College networks, internships, job platforms Volume is useful if the screening task is clear
Specialist compliance or finance Professional networks and referrals Domain judgement is hard to assess from keywords

Use LinkedIn, company career pages, referrals, and relevant communities. Do not assume a job board creates quality by itself. It creates reach. Your screening process must create signal.

The application should test the job

Do not ask a growth candidate for a generic cover letter. Ask for a short teardown of your landing page. Do not ask a product candidate to describe their passion. Give them a real prioritisation problem. Do not ask a sales candidate to “sell themselves”. Ask them to write the first outreach message to a target customer.

Keep the task short. Thirty to ninety minutes is enough for most early screens. Never use candidate work to ship your product or run your business for free.

A good work sample tests three things:

  • Can the candidate understand an unfamiliar problem?
  • Can they make trade-offs?
  • Can they communicate a decision clearly?

Score the work before reviewing names and colleges. Use a simple rubric: problem framing, judgement, clarity, speed, and relevance. This reduces founder bias.

How to make the job description search-friendly

If you want the right applicants to find the role, use the words they search for. Put the actual role title in the headline and first paragraph:

  • Founding Software Engineer, Bengaluru
  • Business Development Manager, B2B SaaS, Mumbai
  • Operations Lead, D2C, Delhi NCR
  • Product Manager, Fintech, Pune

Include relevant terms naturally: startup jobs in India, remote startup jobs, founding engineer, B2B sales, product manager, operations manager, ESOPs, Bengaluru, Mumbai, Delhi, Hyderabad, Pune, or the actual location.

Do not stuff keywords into awkward sentences. Candidates are the audience. Search engines follow clarity.

Put the role on your own website as well as external platforms. A company careers page gives candidates a place to inspect your product, founders, funding, privacy policy, and other open roles.

Red flags that repel A-players

  • A salary range that says “₹1-20 lakh depending on candidate”.
  • A “founding” title with no equity, authority, or meaningful ownership.
  • “Unlimited leave” paired with an expectation that nobody takes leave.
  • “Fast-paced” used to excuse poor planning.
  • Four interview rounds followed by two weeks of silence.
  • A job description that never names the manager.
  • Unpaid assignments that resemble billable work.
  • Claims about a large market with no customer proof.
  • Requirements copied from a multinational job posting.
  • “Must be willing to work under pressure” with no description of the pressure.

Every one of these signals tells a good candidate that the founder may be difficult, cash may be tight, or the role may change without warning. Some of those things may be true. Hiding them does not improve hiring. It improves the odds of a bad match.

Use a 48-hour job description audit

Before publishing, ask a current employee, a trusted founder, and one person who does not know your company to read the draft. Ask each person:

  1. What do you think this person will achieve in 90 days?
  2. What do you think will be hardest about the role?
  3. What salary and seniority do you think this role implies?
  4. What question would stop you from applying?
  5. What part sounds like marketing rather than fact?

If their answers differ, the job description is not clear.

Then publish it for seven days and track:

  • Number of relevant applicants
  • Referral share
  • Screen-to-interview conversion
  • Interview-to-offer conversion
  • Offer acceptance rate
  • Reasons strong candidates decline

If 200 people apply and only three meet the must-have criteria, your targeting or wording is broken. If strong candidates reach the final round and decline, the problem may be compensation, founder credibility, decision speed, or the role itself.

Investor test: Treat hiring spend like customer acquisition. Track the funnel from impression to qualified applicant to accepted offer. If you cannot explain where good candidates disappear, you are guessing with payroll.

What to change this week

  1. Pick the one business bottleneck that justifies the hire.
  2. Write a one-sentence outcome for the first 90 days.
  3. Remove every requirement that does not predict that outcome.
  4. Add the salary range, work model, reporting line, and difficult parts.
  5. Create a 60-minute work sample based on a real problem.
  6. Send the draft to three people and ask them to repeat the role back to you.
  7. Publish through one targeted channel and your own website.
  8. Review the applicant funnel after one week, not after three months.

The bottom line

A-players do not apply because your job description says “rockstar”, “ninja”, or “fast-paced”. They apply when they see a serious problem, real authority, credible founders, fair compensation, and a standard they want to meet.

Your job description is a promise. Write the promise you can keep. If the role is still vague, do not publish a better advertisement. Fix the role.

FAQs

What should a startup job description include in India?

Include the role title, location, work model, company context, reason for hiring, responsibilities, first 30/60/90-day outcomes, must-have evidence, salary range, ESOP details if relevant, reporting line, hiring process, and application instructions.

Should Indian startups mention salary in a job description?

Yes. A realistic range reduces wasted interviews and signals respect. It also helps you compete honestly with larger companies. Do not write “competitive salary” without numbers.

How long should a startup job description be?

Aim for 500 to 900 words for most roles. Use enough detail to explain the work and the first 90 days. Cut company history, slogans, and repeated adjectives.

How do I write a job description for a founding engineer?

Explain the product stage, current technical constraints, architecture ownership, expected shipping pace, founder involvement, on-call expectations, salary, equity, and the first product or engineering outcomes. Do not use “founding” merely to justify below-market cash.

Should a startup job description require an IIT or IIM degree?

Only if the role genuinely requires a credential or regulated qualification. For most startup roles, ask for evidence of relevant work instead. A famous college is not proof that someone can operate in ambiguity.

How should startups describe ESOPs in a job posting?

State whether equity is included, and explain the grant structure during the offer process: number of options or fully diluted percentage, vesting, cliff, exercise price, approval status, and departure rules. Never present uncertain equity as guaranteed cash.

Where should Indian startups post job openings?

Start with referrals, founder networks, LinkedIn, your company website, relevant professional communities, and specialist platforms. Choose the channel based on the role. A founding engineer and an entry-level operations executive do not need the same sourcing method.

What is the best way to screen candidates for a startup role?

Use a short work sample based on the actual job, followed by a structured interview. Score problem framing, judgement, communication, and execution. Do not rely only on CVs, college names, or unstructured founder conversations.

If you want a second pair of eyes on a senior early-stage hire, Malpani Ventures works with founders on the decisions that affect runway, including hiring and team design.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top