Job Summary

Founding Product Manager Own HeyHomie s product, metrics and shipping rhythm - and grow into Head of Product.

Role overview

You are HeyHomie s founding product manager. You own the product, the metrics, and the rhythm of how we ship. You report directly to the founder. You do not have a PM team to back you up - you have engineering, design, customer success, and a founder who will spar with you on every decision. That is the design.

You write the specs. You talk to the sellers. You read the data. You sit in the support escalations and the engineering standups. You QA before launch. You write the in-app copy, the launch note - and then you measure what happened.

If a part of the product is broken, it is yours. If onboarding does not activate, it is yours. If the support tickets keep repeating the same complaint, it is yours. If a dashboard tells a story no one is acting on, it is yours.

The trajectory is Head of Product within 18 to 24 months. You earn it by what shipped, what worked, and what the metrics actually did - not by what you presented in a slide.

Role details

- Location: Bangalore
- Work model: On-site
- Type: Full time (IC)
- Experience: 3-7 years
- Reports to: Founder & CEO
- Trajectory: Head of Product in 18-24 months

Why this role exists now

Product-market fit on referrals doesn t survive without product rigour underneath. HeyHomie earned its product-market fit the hard way - no performance marketing, no paid acquisition. Every seller who joins comes because another seller told them to. That is the rarest signal a young company can buy.

But our sellers run across 22+ categories. Their needs diverge. Their workflows diverge. Their metrics diverge. Right now we hold the shape together with founder instinct, customer-success effort and engineering willpower. That works to a point. We are at the point.

What the next chapter needs is a brain that holds the product together - someone who reads users and dashboards with equal rigour, who decides what we build, what we kill, what we polish and what we delay,



and who ll do it themselves on a Tuesday afternoon and write the spec on Wednesday morning.

This is not a manage the engineering backlog role. This is the role that owns whether HeyHomie s product compounds or stalls.

What you will own

If a seller touches it, it is yours.

Responsibilities

- The roadmap: You decide what gets built, what gets killed, what gets pushed. You hold the line on prioritisation when the team wants to do everything, and on shipping when the team wants to polish forever. You are the tiebreaker the founder relies on - not the messenger between the founder and the team.
- User research: You talk to homepreneurs every week, across categories and stages. You know the cake seller from Mumbai, the saree reseller from Surat, the bakery owner from Pune by their actual problems - not their personas. You bring those conversations into the room. You do not delegate this. Not now, not ever.
- The metrics layer: Activation, retention, time-to-first-value, NRR, churn, expansion revenue, feature adoption, ticket trends, funnel drop-offs, cohort behaviour. You own the dashboards, the reading, and the calls that come out of them. You build the dashboards if they do not exist.
- The full lifecycle, not just the build: Onboarding flows. Activation moments. Support experience. Customer-success enablement. Renewal and upsell triggers. Win-back flows. If a product surface touches a seller, it is in your scope.
- The specs and the polish: You write the PRDs and wireframe when needed. You QA before launch. You write the in-app copy, the empty states, the error messages and the launch note. You do not hand off and walk away.
- The cross-functional glue:



Engineering needs clarity on scope. Design needs clarity on intent. Customer success needs to know what ships and when. Sales needs talking points. Marketing needs positioning. You are the connective tissue across all of it.
- The team s metric, not just yours: You do not optimise your number at the cost of someone else s. If engineering is burning out on bugs, that is your problem too. If customer success is repeating the same answer fifty times a week, that is your problem too. The system wins or the system loses. You own the system.

A quarter in your shoes

Too senior for a week-in-the-life. Here s your first quarter. We re not writing a week-in-the-life - the role is too senior and the work too cyclical. Here is what your first 90 days actually look like.

Weeks 1-4 Listen & read

You talk to twenty sellers across categories. You sit in support shadows for a week. By the end of week four you have a written audit: what is working, what is broken, what is invisible, what we are about to need. Not a slide deck. A document.

Weeks 5-8 Ship one thing that moves a metric

Not a roadmap presentation. Not a vision document. One product change, shipped to real sellers, measured against a real number - a fix to onboarding activation, a rework of the support experience, a new analytics surface for sellers. You decide what wins fastest, ship it, and defend the choice in front of the team.

Weeks 9-12 Set the rhythm

By quarter s end you have set the product rhythm: how we plan, how we ship, how we measure, how we kill features, how we listen to sellers. The team feels the difference. The founder feels the difference. The sellers feel the difference. That is the bar.

Who we re looking for

An operator, not a strategist. Disclaimer: This job posting has been aggregated from external source. Role details, content, and availability are subject to change. Applicants are advised to confirm the latest information directly on the company website before applying.

📌 Founding Product Manager (Bengaluru)
🏢 Heyhomie
📍 Bengaluru