Product Growth Manager | PGM - 2 | RCPL

Fynd is a frontier technology company. We started at the intersection of technology and retail because that is where technology was the least available. Over the years, we became one of India’s largest retail technology platforms. But retail was the entry point, not the boundary. Today, Fynd builds intelligent software that runs business operations. Not tools that help people work faster, but systems that absorb entire functions: manufacturing, marketing, logistics, commerce, quality control. We sit inside our customers’ businesses, harvest deep domain context, and build AI systems that operate autonomously. We are expanding from retail into manufacturing, generative media, physical AI, and healthcare. The role in one line : You own a product, not a backlog. This is the product owner seat on our largest enterprise engagement, an FMCG business running its distribution, field sales and commerce stack on our platform. You take requirements from CXOs, you sit with the people who use the product every day, and you decide what gets built. What you'll own : The whole product, not the next feature. You hold the full picture of the product in your head — how the modules connect, what the platform is becoming, and where today's release sits inside it. Priorities move week to week and that is fine. What does not move is your judgement on whether a request fits the product or bolts on to the side of it. You say no to the ones that bolt on, and you can explain why to the person who asked. The CXO relationship. Requirements and priorities come from senior business leadership on the client side. You run those conversations yourself. You come out of them with a decision, not a list of things to check with someone else. The daily user. The same product is used by field sales officers, distributors and area managers every single day. You spend time with them, in the market, not on a call. What they tell you carries the same weight as what leadership tells you, and reconciling the two is your job. Build to live. You gather the requirement, write the spec, prototype it yourself with AI coding tools, work with engineering through the build, test it, and stay on it through deployment. You are involved at every stage, not at the two ends. Speed. Enterprise timelines on this account are measured in days. You move at that pace and you hold the team to it. Who you are A product owner, not a facilitator. You make calls. You are not running a status meeting between two teams and reporting what they said. When the requirement is unclear or two stakeholders want opposite things, you decide and defend it. Technically hands-on. You read SQL and PRs, follow a system diagram, and build working prototypes with AI coding tools instead of writing a 12-page document about what you want. You can run a QA pass yourself, walk a deployment, and check a log when something breaks at 9 PM. Comfortable in the room and in the field. You hold your own with a…