Milvus India Product Manager Interview: Rounds, Questions and Preparation

What the job involves

As a Product Manager at a fast-growing global tech company, you will define product vision, prioritise features based on user needs and business goals, and work closely with engineering, design, and go-to-market teams to ship impactful solutions. You will spend your days gathering insights from data and customer conversations, writing clear product requirements, and tracking success metrics after launch.

Role and Technical Knowledge

1. 1

   How would you explain the difference between a product manager and a project manager to an engineering intern?

   A strong answer contrasts ownership of 'what' and 'why' (PM) versus 'how' and 'when' (project manager), using a concrete example like prioritising a feature versus tracking its delivery timeline.

2. 2

   What metrics would you track for a new feature that lets users save items to a wishlist in an e-commerce app?

   Cover activation rate (users who add at least one item), retention of wishlist users, conversion from wishlist to purchase, and engagement frequency, while explaining why each matters.

3. 3

   Explain how you would write a product requirement document (PRD) for a mobile app's push notification settings page.

   Mention sections like problem statement, user stories, acceptance criteria, edge cases (e.g., disabling all notifications), and success metrics, keeping it concise and testable.

4. 4

   What is an API and why should a product manager care about it when building a new integration?

   Define API simply as a contract for software to talk to software, then explain how it affects feasibility, third-party dependencies, and rate limits that impact user experience.

Practical Scenarios

1. 5

   You are the PM for a food delivery app. Users complain that delivery time estimates are often wrong. How would you approach fixing this?

   Start by quantifying the problem with data (percentage of wrong estimates, impact on retention), then propose solutions like better ETA models, buffer times, and clear communication, and define a metric to measure improvement.

2. 6

   Your engineering team says a feature you prioritised will take twice as long as estimated. How do you decide whether to cut scope, delay, or cancel?

   Show a structured trade-off: assess business impact, user value, and strategic alignment, then suggest options like a phased rollout or MVP, and communicate transparently with stakeholders.

3. 7

   A competitor launches a feature that your users are requesting. How do you decide whether to build it?

   Avoid copying blindly; evaluate if the feature aligns with your product vision, estimate effort versus impact, and consider if a different solution addresses the underlying user need better.

4. 8

   You have three feature ideas for a fitness app: social challenges, offline mode, and Apple Watch integration. How would you prioritise them for the next quarter?

   Use a framework like RICE (Reach, Impact, Confidence, Effort) and justify assumptions with data or user research, while acknowledging trade-offs and dependencies.

Behavioural and HR

1. 9

   Tell me about a time you had to convince a team to adopt your idea without any formal authority.

   Use STAR format: describe the situation, your approach to building consensus through data and empathy, the outcome, and what you learned about influence.

2. 10

   Why do you want to be a product manager at a fast-growing global tech company rather than a larger, more established firm?

   Show genuine interest in owning end-to-end product decisions, wearing multiple hats, and learning quickly in a dynamic environment, and connect it to your long-term career goals.

3. 11

   Describe a project where you had to make a decision with incomplete information. What did you do?

   Highlight how you identified key unknowns, gathered just enough data, made a reversible decision, and set up a feedback loop to course-correct.

4. 12

   How do you handle feedback from engineers or designers who disagree with your product direction?

   Emphasise active listening, separating opinions from data, and being willing to change your mind if presented with better evidence, while keeping the team aligned on goals.

Product Sense and Strategy

1. 13

   How would you improve the onboarding experience for a new user on a language-learning app?

   Break down the current funnel, identify drop-off points, and propose specific changes like personalised goal setting or a quick win lesson, then define metrics to test the impact.

2. 14

   Pick a product you use daily. What is one thing you would change and why?

   Choose a product you know well, state a clear user problem, propose a specific solution, and explain how you would measure success without overcomplicating.

3. 15

   Imagine you are launching a new product for small businesses in India to manage invoices. What would your go-to-market strategy be?

   Cover target segment, value proposition, pricing, distribution channels (e.g., partnerships with local accountants), and early success metrics like activation and retention.

4. 16

   How would you decide whether to build a feature for power users or for new users when both groups are asking for different things?

   Assess the size and strategic value of each segment, the impact on core metrics like retention or revenue, and consider if a single solution can serve both without compromising either.