Question 1

How would you improve an existing product? (Pick any product)

Accepted Answer

Framework: 1) Define the product's mission and target user. 2) Identify pain points through data (usage metrics, drop-off funnels) and qualitative research (user interviews, reviews). 3) Prioritize problems by impact × frequency. 4) Generate solutions with constraints (team size, timeline, technical feasibility). 5) Define success metrics. Example (improving Zomato): Pain point: Users abandon orders at payment. Data shows 30% cart abandonment. Solution: Add UPI auto-detect, save payment preferences, show delivery fee upfront (transparency). Success metric: Reduce cart abandonment by 15% in 3 months. Always tie improvements to measurable outcomes.

Question 2

How do you prioritize features on a product roadmap?

Accepted Answer

Frameworks: 1) RICE Score — Reach (how many users) × Impact (how much value) × Confidence (how sure are we) ÷ Effort (dev time). 2) MoSCoW — Must have, Should have, Could have, Won't have. 3) Kano Model — Basic (expected), Performance (more is better), Delight (unexpected joy). 4) Value vs Effort Matrix — 2×2 grid, prioritize high-value/low-effort first. My approach: Start with user pain points and business goals, use RICE for scoring, validate with stakeholders, review quarterly. Always keep 20% capacity for tech debt and bugs. Document decisions and reasoning for transparency.

Question 3

What metrics would you track for a food delivery app?

Accepted Answer

North Star Metric: Orders per active user per month. Acquisition: App downloads, sign-up conversion rate, CAC (Customer Acquisition Cost). Activation: First order within 7 days of sign-up, onboarding completion rate. Engagement: DAU/MAU ratio, average orders/month, session duration, search-to-order conversion. Revenue: AOV (Average Order Value), revenue per user, take rate (commission). Retention: D7/D30 retention, churn rate, repeat order rate. Delivery: Average delivery time, on-time delivery %, driver utilization. Satisfaction: NPS, app store rating, customer support ticket volume. I'd build a daily dashboard for top 5 metrics and monthly deep-dives for the full set.

Question 4

Explain Agile vs Waterfall methodology.

Accepted Answer

Waterfall: Sequential phases (Requirements → Design → Development → Testing → Deployment). Changes are expensive. Full product delivered at end. Best for: Fixed requirements, regulated industries (medical, aerospace), short well-understood projects. Agile: Iterative sprints (2-4 weeks), working software delivered each sprint, embraces change, continuous feedback. Frameworks: Scrum (sprints, daily standup, retrospective), Kanban (continuous flow, WIP limits). Best for: Evolving requirements, user-facing products, innovation. Most modern software teams use Agile. Hybrid approaches exist — Agile development with milestone-based reporting to stakeholders.

Question 5

How do you handle scope creep in a project?

Accepted Answer

Prevention: 1) Clear requirements document with sign-off. 2) Defined MVP with "nice-to-have" separated. 3) Change request process — every new ask goes through impact assessment. Management: 1) When a new request comes, evaluate: Does it align with project goals? What's the impact on timeline/cost/resources? 2) Present trade-offs: "We can add Feature X if we defer Feature Y or extend the deadline by 1 week." 3) Get stakeholder approval for any changes. 4) Maintain a parking lot list for post-launch features. Key: Never say "no" directly — say "yes, and here's what it costs." Document everything.

Question 6

How do you manage stakeholder expectations?

Accepted Answer

Framework: 1) Identify stakeholders and their priorities (power/interest grid). 2) Set clear expectations upfront — define scope, timeline, success criteria in a kick-off doc. 3) Regular communication cadence — weekly status updates for active stakeholders, monthly for informed stakeholders. 4) No surprises — flag risks early with mitigation plans. 5) Use data to tell the story — dashboards > opinions. 6) When saying no: provide rationale, data, and alternatives. Example: "We can't launch Feature X this quarter because it needs 8 more weeks of dev work, but we can ship the MVP version that covers 80% of use cases by the deadline."

Product & Project Management Interview Questions & Answers

Product Strategy & Thinking

Agile & Project Management

Key Tips for Product / PM Interviews