Product Manager job description template (India, 2026)
A Product Manager job description written for Indian companies: responsibilities, requirements, CTC and notice-period framing, five screening questions, and the full text to copy or post on ofper.
Last updated 3 September 2026. Competitor pricing and plan limits are re-verified against each vendor’s own pages.
What does a Product Manager do?
A startup hires its first Product Manager when the founder can no longer be the one writing every spec, answering every engineer's question and talking to every customer. The PM owns the roadmap and the backlog, does the customer research, writes clear specifications with the edge cases, works with the designer and engineers daily, decides trade-offs when the deadline and the scope collide, and measures whether what shipped worked.
In an SME the PM is hands-on: writing specs, testing builds, answering support escalations, sometimes doing the analytics. The posting should be honest about that, state the product and its stage, the team size, how decisions are made with the founder, and what the PM is measured on. Candidates from large product companies with layers of PMs need to understand the breadth and the founder relationship.
Product Manager responsibilities
Written as work the person does, not qualities they have. A responsibility a candidate can picture is one they can decide about.
- Own the product roadmap and backlog for [product / area], aligned to the company's goals and revisited monthly with the founder and the team.
- Talk to customers and users every week — calls, support tickets, sales conversations, usage data — and turn what you learn into prioritised problems.
- Write specifications the team can build from: the problem, the user, the flows, the edge cases, the acceptance criteria and what is out of scope.
- Work daily with the designer and engineers: answer questions, make trade-off decisions, unblock, and test builds before release.
- Define success metrics for each release, instrument them with the analyst or engineers, and report whether shipped work moved them.
- Run the release process from the product side: release notes, support and sales enablement, and the follow-up on feedback.
- Handle escalations and feature requests from sales, support and customers with a clear yes, no or not yet, and the reason.
- Keep the product's documentation and the team's understanding of the user current.
Product Manager requirements and qualifications
Keep the required list to what you would actually reject a candidate for. Everything else goes under nice to have — a long required list mostly filters out the people you wanted.
- 3 to 6 years in product management, or a strong engineer, designer or founder with at least 1 to 2 years owning product decisions and outcomes.
- Evidence of shipping features that moved a metric — and of killing or cutting things that would not.
- Writes clearly: specs with edge cases and acceptance criteria that engineers rarely have to come back on.
- Comfortable with data — SQL or an analytics tool — enough to answer your own questions about usage.
- Talks to customers regularly and can show how a conversation changed a decision.
- Willing to work [from our office / hybrid] and to be hands-on: testing builds, handling escalations, writing release notes.
Nice to have
- Experience in our domain — payments, logistics, healthcare, education — or with our user type.
- Technical background sufficient to read code or discuss architecture trade-offs with engineers.
- Experience as the first PM in a startup, working directly with a founder.
Salary, CTC and terms for a Product Manager in India
State a CTC range. Postings without one get fewer and worse-matched applications, and the range is the first thing an Indian candidate looks for. Say how the CTC is made up — fixed, variable, and any statutory components — so the in-hand figure is not a surprise at offer stage.
- State the CTC range with fixed and variable and the ESOP grant and vesting — for a first PM the equity is part of the decision and the conversation.
- State the product stage, team size and how decisions are made with the founder; scope and autonomy define the seniority more than the title.
- State the work-from-office policy and whether notice buyout is offered.
- State the interview process, including any case exercise and its length.
Product Manager job description template
Replace every [placeholder]. Cut anything that is not true of your company — a generic paragraph is worse than no paragraph.
Product Manager — [Company name], [City] Employment type: Full-time | Location: [City] / [On-site, hybrid or remote] | CTC: [range] per annum | Experience: [years] About the role A startup hires its first Product Manager when the founder can no longer be the one writing every spec, answering every engineer's question and talking to every customer. The PM owns the roadmap and the backlog, does the customer research, writes clear specifications with the edge cases, works with the designer and engineers daily, decides trade-offs when the deadline and the scope collide, and measures whether what shipped worked. In an SME the PM is hands-on: writing specs, testing builds, answering support escalations, sometimes doing the analytics. The posting should be honest about that, state the product and its stage, the team size, how decisions are made with the founder, and what the PM is measured on. Candidates from large product companies with layers of PMs need to understand the breadth and the founder relationship. What you will do - Own the product roadmap and backlog for [product / area], aligned to the company's goals and revisited monthly with the founder and the team. - Talk to customers and users every week — calls, support tickets, sales conversations, usage data — and turn what you learn into prioritised problems. - Write specifications the team can build from: the problem, the user, the flows, the edge cases, the acceptance criteria and what is out of scope. - Work daily with the designer and engineers: answer questions, make trade-off decisions, unblock, and test builds before release. - Define success metrics for each release, instrument them with the analyst or engineers, and report whether shipped work moved them. - Run the release process from the product side: release notes, support and sales enablement, and the follow-up on feedback. - Handle escalations and feature requests from sales, support and customers with a clear yes, no or not yet, and the reason. - Keep the product's documentation and the team's understanding of the user current. What we are looking for - 3 to 6 years in product management, or a strong engineer, designer or founder with at least 1 to 2 years owning product decisions and outcomes. - Evidence of shipping features that moved a metric — and of killing or cutting things that would not. - Writes clearly: specs with edge cases and acceptance criteria that engineers rarely have to come back on. - Comfortable with data — SQL or an analytics tool — enough to answer your own questions about usage. - Talks to customers regularly and can show how a conversation changed a decision. - Willing to work [from our office / hybrid] and to be hands-on: testing builds, handling escalations, writing release notes. Nice to have - Experience in our domain — payments, logistics, healthcare, education — or with our user type. - Technical background sufficient to read code or discuss architecture trade-offs with engineers. - Experience as the first PM in a startup, working directly with a founder. Compensation and terms - State the CTC range with fixed and variable and the ESOP grant and vesting — for a first PM the equity is part of the decision and the conversation. - State the product stage, team size and how decisions are made with the founder; scope and autonomy define the seniority more than the title. - State the work-from-office policy and whether notice buyout is offered. - State the interview process, including any case exercise and its length. How to apply Apply with your resume through this page. We reply to every application, and shortlisted candidates hear from us within [number] working days.
Opens a free ofper workspace with the title, description and screening questions filled in.
Screening questions for Product Manager applicants
Five questions is the ceiling on ofper, and it is the right ceiling: a form that asks more than that costs applications. Use them for the things that decide a shortlist, not for anything the resume already says.
| Question | Type | Knockout | Why it earns a slot |
|---|---|---|---|
| Have you owned product decisions and their outcomes — roadmap, specs, metrics — for at least 2 years? | Yes / No (pass: Yes) | Yes | Ownership of outcomes separates PMs from project coordinators and analysts. |
| How many years of product management experience do you have? | Number (pass: 2+) | No | Not a knockout — strong engineers and founders transition — but it calibrates the interview. |
| Are you able to work [from our City office X days a week / hybrid]? | Yes / No (pass: Yes) | Yes | PMs in a small team need to be with the team; settle it first. |
| What is your current notice period, in days? | Number (pass: 0 to 90) | No | Timeline and buyout planning. |
Questions, answered straight
What should a Product Manager job description include for a startup?
The product and its stage, the team size, how decisions are made with the founder, what the PM is measured on, the hands-on reality (testing builds, escalations, release notes), the work-from-office policy, the interview process and the CTC range with ESOP. First-PM candidates decide on autonomy and equity.
When does a startup need a Product Manager?
When the founder is the bottleneck for every spec and every engineer's question, and customer conversations are no longer reaching the people who build. Usually between five and ten engineers, or earlier if the founder's time is the scarcest resource.
Should the first PM be a former engineer?
Not necessarily, but technical fluency helps in a small team where the PM discusses trade-offs with engineers daily. Judgement, writing and customer contact matter more than a coding background. Ask for evidence of outcomes owned, whatever the background.