Product Manager

Role overview

Product Manager at Practo

Responsibilities

• Work closely with engineering, design, business, and external partners to define, scope, and ship integration-heavy features — from API contracts to UX flows.

Required qualifications

• 3–6 years of product management experience, with at least 2 years on a B2B SaaS or platform product involving technical integrations (APIs, webhooks, third-party systems).
• Minimum qualification: Graduate

Employment details

• Location: Bengaluru [Karnataka] [India]

Additional role details

• Experience working on a B2B2C product — you understand both the partner's operational needs and the end consumer's expectations, and know when they conflict.
• Comfortable reading and writing basic technical specs, reviewing API documentation, and participating in architecture discussions — you don't need to code, but you can't be a stranger to engineering conversations.
• Proven ability to ship in a fast-moving environment: you've worked in a startup or a high-velocity team, and you have a track record of making good decisions with incomplete information.
• Strong prioritisation instincts — you can separate signal from noise, say no clearly, and build roadmaps that reflect real tradeoffs.
• Excellent written and verbal communication
• Own end-to-end product strategy and execution for B2B integrations and the consumer-facing products built on top of them.
• Translate partner requirements (SLAs, data needs, workflows) into clear, well-scoped product specs without losing sight of the end consumer experience.
• Define and track metrics that matter across both B2B (activation, integration health, partner retention) and B2C (engagement, conversion, satisfaction) surfaces.
• Drive rapid iteration cycles — prioritise ruthlessly, cut scope intelligently, and get working product in front of users fast.
• Partner with sales, customer success, and business teams to shape GTM strategy and support commercial conversations with technical credibility.
• Anticipate integration failure modes, edge cases, and system dependencies early — and build these into planning, not just post-launch firefighting.