Product Growth Manager | PGM - 2 | JCP
Fynd (company site, opens in a new tab)5–7 yrsMumbaiOn-siteDirect career pageEst. 18–30 LPA
Posted 2d ago
Reach people at Fynd
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Fynd you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own platform initiatives end to end: turn business goals into scope, milestones, success metrics, and executable plans.
- Resolve trade-offs between platform and channel teams, anticipate technical dependencies, and drive internal adoption—not just delivery.
- Measure program performance, analyse results, and iterate based on data.
Minimum Requirements
- Work Experience Required: 5–7 years in technical program management, product management, or product ownership; the JD says a strong AI-native candidate with 4 years may outweigh a 7-year coordinator.
- Bachelor’s degree in Business, Computer Science, or a related field.
- Experience in SaaS, platform ecosystems, or e-commerce technology, with proven delivery across multiple teams and internal/external stakeholders.
- AI fluency is required: use AI tools in day-to-day work and discuss APIs, retrieval, evaluations, tokens, and latency-versus-cost trade-offs; also bring strong data analysis skills and working knowledge of Agile, Lean, or Kanban.
Ideal Candidate Profile
- A product-owner operator who can align platform capabilities with channel needs and make trade-offs using evidence.
- Technically fluent enough to read SQL and PRs, understand system diagrams, and work credibly with engineering and AI teams without owning implementation.
- Has independently driven complex programs from ambiguity through adoption, and can explain decisions, metrics, and what they chose not to build.