The Role

This is a generalist PM role, not a specialist one. In the same week you might be writing a PRD, sitting in a sprint planning session, and on a call with a university administrator trying to understand why a feature isn't landing. You'll work closely with Engineering, Design, Customer Success, and Sales, and you're expected to make calls independently and explain your reasoning clearly — whether you're talking to an engineer or a customer who has never used a product roadmap tool in their life.

Key Responsibilities

- Own the product roadmap for your area — weighing what customers are asking for against business priorities and what's actually feasible to build.
- Speak regularly with university administrators, wardens, operations teams, and other stakeholders to gather structured customer feedback.
- Analyse product usage data to identify friction points and recommend product improvements.
- Prioritise features based on customer demand, business impact, and strategic goals.
- Define product requirements and collaborate with Design and Engineering teams to ship impactful features.
- Work closely with Sales and Customer Success to identify expansion opportunities and improve customer outcomes.
- Own delivery end to end — scoping, sprint planning, execution, QA, and getting it live — not just handing off a spec and moving on.
- Make the calls that need making, even with incomplete information, and be ready to walk engineers and customers through your reasoning.
- Sit in on sprint planning and backlog grooming with Engineering and Design, and explicit blockers when the team needs it.
- Keep an eye on product quality after launch — triage what breaks, and push fixes through with Engineering.




- Track the metrics that actually matter (usage, adoption, satisfaction) and let them shape what you prioritise next.

What We're Looking For

- 3–6 years in Product Management, ideally in enterprise or B2B SaaS.
- A real track record of owning a product area start to finish, not just contributing to one someone else owns.
- You write clearly — PRDs make sense to engineers, and you can hold your own explaining a decision to a customer who isn't technical.
- You're comfortable being the person customers talk to directly, and honest with them about what the product can and can't do yet.
- You make decisions. Even without full information, you're willing to call it and own what happens next.
- You know Agile/Scrum well enough to run with it — sprint planning, backlog grooming, release management, the whole cycle.
- You can hold customer requests, business goals, and engineering constraints in your head at once, and explain the trade-offs without getting defensive.
- You're fine with startup pace — less structure, more ownership, figuring things out as you go.
- You'd rather ship something real than keep polishing a deck about it.

Nice to Have

- Experience working in B2B SaaS products.
- EdTech or enterprise software experience.
- Experience with product analytics tools such as Mixpanel, Amplitude, GA4, or similar platforms.
- Familiarity with SQL and data analysis.
- Time spent with enterprise or institutional customers, where sales cycles and rollouts run longer than usual.
- Have run product experiments or A/B tests before — not essential here, but a bonus.
- Spent time at an early-stage startup where resources were tight and you just had to make it work.

📌 Product Manager (Bengaluru)
🏢 Versatile.club
📍 Bengaluru