Product Manager interview questions
13 questions written for Product Manager roles, plus the HR and behavioural questions you'll face everywhere. Each has a model answer and the follow-ups to expect.
49 questions
BehaviouralStakeholdersMediumTwo stakeholders want conflicting things. How do you handle it?
Reported at Deloitte, Accenture
Two stakeholders want conflicting things. How do you handle it?
Reported at Deloitte, Accenture
What they are checking: Facilitation and a focus on business goals.
Model answer
In my internship, the sales head wanted a lead form with only two fields to get more sign-ups, while the operations head wanted eight fields so her team didn't have to call every lead.
I met each separately to understand the goal behind their request: sales cared about the number of leads, operations about the time spent qualifying them. Then I brought data to a joint meeting: our past forms lost about 10% of users for every extra field, and operations spent about 6 minutes calling each lead.
We agreed on a middle path: three fields on the form, and a short optional second step after submission. Sign-ups dropped only slightly and calls per lead fell by half. When stakeholders still can't agree, I take the options and trade-offs to whoever owns the business goal to decide.
TechnicalStatisticsEasyWhen would you report the median instead of the mean?
Reported at Amazon, Flipkart, Deloitte
When would you report the median instead of the mean?
Reported at Amazon, Flipkart, Deloitte
What they are checking: Statistical common sense.
Model answer
When the data is skewed or has outliers. The mean is pulled by extreme values; the median isn't.
Example: if nine people in a team earn ₹5 lakh and the founder earns ₹1 crore, the mean salary is about ₹14.5 lakh, which describes nobody. The median, ₹5 lakh, describes the typical person.
Order values, delivery times and incomes are usually right-skewed, so I report the median, often with the 90th percentile to show the tail. I use the mean when the data is roughly symmetric or when the total matters, such as average revenue per user used to forecast total revenue.
TechnicalStatisticsMediumExplain correlation versus causation with an example.
Reported at Amazon, Google, Flipkart
Explain correlation versus causation with an example.
Reported at Amazon, Google, Flipkart
What they are checking: Whether you will over-claim from data.
Model answer
Correlation means two things move together; causation means one actually causes the other.
Example: users who use the wishlist feature spend 3 times more. That doesn't prove the wishlist makes people spend more. Keen shoppers may simply be more likely to use every feature. This is a confounding variable: shopping intent drives both.
To show causation you need an experiment: randomly show the wishlist to half of new users and compare their spending. If that isn't possible, techniques such as comparing before and after with a control group (difference-in-differences) or matching similar users get closer, but I'd state the limitation clearly.
TechnicalExperimentationMediumHow would you design an A/B test for a new checkout button?
Reported at Amazon, Flipkart, Google, Microsoft
How would you design an A/B test for a new checkout button?
Reported at Amazon, Flipkart, Google, Microsoft
What they are checking: End-to-end experimental thinking.
Model answer
- Hypothesis: a bigger, green "Buy now" button will increase checkout completion.
- Primary metric: checkout conversion rate. Guardrail metrics: refund rate, page load time, average order value, to catch harmful side effects.
- Randomisation: split users (not sessions) randomly 50/50, so the same person always sees the same version.
- Sample size: calculate it before starting from the current conversion rate, the smallest lift worth detecting (say 2%), 95% confidence and 80% power.
- Duration: run whole weeks, usually at least two, to cover weekday and weekend behaviour.
- Analysis: check the split was actually 50/50, then test for significance. Don't stop early just because the result looks significant on day 3; peeking inflates false positives.
- Decision: ship if the primary metric improves significantly and no guardrail gets worse.
Likely follow-ups
- The result is significant but the lift is 0.1%. Ship it?
- What if mobile and desktop show opposite results?
TechnicalAgileEasyWrite a user story with acceptance criteria for a password reset feature.
Reported at Accenture, Cognizant, Capgemini
Write a user story with acceptance criteria for a password reset feature.
Reported at Accenture, Cognizant, Capgemini
What they are checking: Can you write requirements a developer and tester can act on?
Model answer
User story: As a registered user who has forgotten my password, I want to reset it using my email, so that I can get back into my account without contacting support.
Acceptance criteria (Given / When / Then):
- Given I am on the login page, when I click "Forgot password" and enter a registered email, then I receive a reset link within 2 minutes.
- Given I enter an email that is not registered, then I see the same message as for a registered email, so attackers can't find out which emails exist.
- Given I open the link within 30 minutes, then I can set a new password that meets the password rules.
- Given the link is older than 30 minutes or has already been used, then I see "This link has expired" and can request a new one.
- Given I reset my password, then all my other sessions are logged out.
TechnicalPrioritisationEasyHow do you prioritise requirements? Explain MoSCoW.
Reported at Accenture, Deloitte, Capgemini
How do you prioritise requirements? Explain MoSCoW.
Reported at Accenture, Deloitte, Capgemini
What they are checking: Managing scope when everything is "urgent".
Model answer
MoSCoW sorts requirements into four groups for a release:
- Must have: without these the release fails or is illegal. Example: payment for an e-commerce launch.
- Should have: important but there's a workaround. Example: saved cards.
- Could have: nice if time allows. Example: dark mode.
- Won't have (this time): agreed to be out of scope for now, which prevents arguments later. Example: a loyalty programme.
The value is in the conversation: stakeholders must agree what goes in Must. A useful rule is to keep Musts to around 60% of the effort, so there's room if estimates are wrong. For comparing many features by value, I'd use a scoring method such as RICE as well.
TechnicalProduct senseMediumWhat is your favourite product, and how would you improve it?
Reported at Google, Microsoft, Flipkart, Amazon
What is your favourite product, and how would you improve it?
Reported at Google, Microsoft, Flipkart, Amazon
What they are checking: Product thinking: users, problems and trade-offs, not just features you like.
Model answer
My favourite is Google Maps, specifically for commuting in Indian cities.
Why it works: it solves a daily, high-stakes problem (being late) for almost everyone, the live traffic data improves as more people use it, and features like two-wheeler mode show it was designed for Indian users, not just copied from the US.
One improvement: shared autos and local buses in tier-2 cities. In my hometown most people commute by shared auto, and Maps simply has no information on them.
- User: daily commuters in tier-2 cities without metro systems.
- Solution: let users mark shared-auto stands and routes, verified by others, as Maps already does for places.
- Success metric: increase in weekly active transit users in those cities, plus the share of route searches that end in a transit route.
- Risk: data quality. I'd launch in two cities first and only show routes confirmed by several users.
Tips
- Pick a product you actually use.
- Name a specific user segment and how you'd measure success.
TechnicalPrioritisationMediumYou have ten feature requests and capacity for three. How do you decide?
Reported at Flipkart, Microsoft
You have ten feature requests and capacity for three. How do you decide?
Reported at Flipkart, Microsoft
What they are checking: A structured, explainable framework tied to goals.
Model answer
First I check them against the team's current goal. If this quarter is about retention, a feature that brings new users ranks lower however exciting it is.
Then I score them with RICE:
- Reach: how many users it affects per month.
- Impact: how much it moves the goal for each user (3 = big, 2 = medium, 1 = low, 0.5 = minimal).
- Confidence: how sure we are of these estimates, as a percentage.
- Effort: person-months to build.
Score = Reach × Impact × Confidence ÷ Effort.
For example, a feature reaching 20,000 users, with impact 2, 80% confidence and 2 person-months, scores 16,000. Scores start the conversation, they don't end it. I'd also consider dependencies, quick wins and anything that is a legal requirement, and I'd explain to stakeholders why their request didn't make the cut.
TechnicalAnalyticalHardDaily active users of our app fell 10% this week. What do you do?
Reported at Google, Amazon, Flipkart, Microsoft
Daily active users of our app fell 10% this week. What do you do?
Reported at Google, Amazon, Flipkart, Microsoft
What they are checking: The classic root-cause question: calm, structured, hypothesis-driven.
Model answer
- Clarify: is it a sudden drop or gradual? Is it 10% compared with last week or the same week last year? How is a daily active user defined, and did that change?
- Rule out data issues: logging changes, a broken analytics SDK in a new release, delayed data.
- Check external causes: holidays, exams, a competitor launch, an outage at a cloud provider or app store.
- Segment: platform (Android/iOS/web), app version, country or city, new versus existing users, acquisition channel. If the drop is only in the latest Android version, it's probably a bug or crash.
- Walk the user journey: did app opens drop (a notification or marketing issue), or do users open but fail somewhere (a login or loading problem)?
- Check internal changes in the window: releases, experiments, pricing, notification changes.
Then I'd form a hypothesis, confirm it with data (such as crash rates for that version), fix or roll back, and set up an alert so we catch it faster next time.
TechnicalProduct designHardDesign a product that helps elderly people manage their medicines.
Reported at Google, Microsoft, Amazon
Design a product that helps elderly people manage their medicines.
Reported at Google, Microsoft, Amazon
What they are checking: The product design framework: users, needs, solutions, prioritisation, metrics.
Model answer
1. Clarify the goal: I'll assume the goal is fewer missed doses, for elderly people living alone or with working children in India. 2. Users: the elderly person (may have poor eyesight, limited smartphone skills, possibly a basic phone), the family caregiver (often in another city, worried), and the pharmacist or doctor. 3. Pain points: forgetting doses, confusing similar-looking pills, running out of medicine, family not knowing whether medicine was taken. 4. Solutions: - Voice reminders by phone call in their language, which works on any phone. - A pill box with lights for each slot that confirms when opened. - A caregiver app showing taken and missed doses, with an alert after a missed dose. - Automatic refill reminders with pharmacy delivery. 5. Prioritise: for a first version, voice-call reminders plus the caregiver app. They're cheap to build, need no new hardware and address the biggest risk, missed doses. 6. Metrics: dose adherence rate (doses confirmed out of doses scheduled), weekly active caregivers, refill orders, and retention after 90 days. 7. Risks: privacy of health data, and over-reliance; serious missed doses should prompt a call from family, not just an app notification.
TechnicalMetricsMediumHow would you measure the success of a new "Buy Now, Pay Later" option at checkout?
Reported at Amazon, Flipkart, Google
How would you measure the success of a new "Buy Now, Pay Later" option at checkout?
Reported at Amazon, Flipkart, Google
What they are checking: Choosing a north star metric plus guardrails.
Model answer
Goal: increase completed purchases without increasing financial risk.
- Primary metric: checkout conversion rate for users who are shown the option, compared with a control group.
- Supporting metrics: share of orders using pay-later, average order value (it often rises), repeat purchase rate.
- Guardrail metrics: default and late-payment rate, return and cancellation rate on pay-later orders, customer support complaints, and the cost per transaction charged by the lending partner.
I'd run it as an A/B test and segment results by new and existing users and by order value, because pay-later may help mostly on high-value items like phones. Success would be a meaningful lift in conversion while defaults stay within the threshold agreed with the risk team.
TechnicalMetricsMediumExplain the marketing funnel, CAC and LTV.
Explain the marketing funnel, CAC and LTV.
What they are checking: Core marketing math.
Model answer
The funnel describes stages a customer passes through: awareness (they hear about you), consideration (they compare, visit the site), conversion (they buy or sign up), and retention and advocacy (they come back and recommend you). Each stage has its own metrics, such as reach, click-through rate, conversion rate and repeat rate.
CAC (customer acquisition cost) = total sales and marketing spend ÷ new customers acquired. ₹2 lakh spent for 400 customers means a CAC of ₹500.
LTV (lifetime value) = average revenue per customer per month × gross margin × average customer lifetime in months. ₹300 a month × 60% margin × 10 months = ₹1,800.
The LTV to CAC ratio shows whether growth is profitable. A common rule of thumb is at least 3:1; here it's 3.6:1. Below 1:1 you lose money on every customer, however fast you grow. Also watch payback period: how many months until a customer's margin covers their CAC.
TechnicalGuesstimateMediumGuesstimate: how many cups of tea are sold each day in a city of 10 lakh people?
Reported at Deloitte
Guesstimate: how many cups of tea are sold each day in a city of 10 lakh people?
Reported at Deloitte
What they are checking: Structure, sensible assumptions stated out loud, and a sanity check. The final number matters less than the approach.
Model answer
I'll estimate demand from the population, then check it against supply. I'll count tea sold outside the home: stalls, cafés, offices and restaurants.
Demand:
- Population: 10,00,000.
- Tea drinkers: excluding young children and people who don't drink tea, say 60%, which is 6,00,000.
- Cups per drinker per day: about 2, so 12,00,000 cups in total.
- Bought outside the home: most tea is made at home; assume 25% is bought, so 3,00,000 cups a day.
Sanity check from supply:
- A typical tea stall sells about 300 cups a day.
- 3,00,000 ÷ 300 = about 1,000 stalls, or one for every 1,000 people. That seems reasonable for an Indian city when you include office canteens and restaurants.
Answer: roughly 3 lakh cups a day. The biggest uncertainty is the share bought outside, which would be higher in a commercial or student-heavy city.
Tips
- Say your structure before calculating.
- Round numbers so the maths stays easy.
- Always finish with a sanity check.
HRIntroductionEasyTell me about yourself.
Tell me about yourself.
What they are checking: Can you give a short, structured story that connects your background to this job? It sets the agenda for the rest of the interview, so whatever you mention here becomes the next question.
Model answer
I'm [name], a final-year B.Tech Computer Science student at [college], graduating in 2026 with a CGPA of [8.1].
Over the last two years I have focused on backend development. My main project is a hostel complaint tracker built with Node.js and PostgreSQL that 400 students in my hostel now use. I also did a two-month internship at [company], where I wrote REST APIs and cut a slow report query from 9 seconds to under 1 second by adding the right indexes.
Outside class I solve problems on LeetCode, around 300 so far, and I coordinate our college coding club, where I run weekly contests for juniors.
I'm applying here because I want to work on systems that real users depend on, and this role gives me that from day one.
Tips
- Use present, past, future: who you are, what you have done, why this job.
- Keep it under 90 seconds. Mention only things you are happy to be questioned on.
- Do not repeat your resume line by line, and skip family details unless asked.
Likely follow-ups
- Tell me more about the complaint tracker. What was hardest?
- Why did you add indexes rather than caching?
HRSelf-awarenessEasyWhat are your strengths?
What are your strengths?
What they are checking: Whether you know what you are good at and can prove it with an example, rather than listing adjectives.
Model answer
My biggest strength is that I break unfamiliar problems into small pieces and keep going until they work.
In my second year our team had to build an attendance app using face recognition, and none of us had used OpenCV. I split the work into three parts: capturing images, training the model, and matching faces in real time. I took the matching part, read the documentation and two tutorials over a weekend, and had a working version in five days. We demoed it at the department expo and it marked attendance for a class of 60 with about 95% accuracy.
I'd bring the same habit here when I'm handed a codebase or tool I haven't used before.
Tips
- Pick one or two strengths that matter for the role.
- Every strength needs a short story with a result.
Likely follow-ups
- What would your teammates say is your strength?
- What did you do about the 5% the app got wrong?
HRSelf-awarenessMediumWhat is your greatest weakness?
What is your greatest weakness?
What they are checking: Honesty and self-improvement. They want a real weakness that will not stop you doing the job, plus what you are doing about it.
Model answer
I used to find it hard to say no when people asked for help, and I would take on more than I could finish.
In my third year I agreed to help with three club events in the same month as my mid-semester exams, and my marks in one subject dropped. Since then I have started keeping a simple weekly plan in Notion. Before I agree to something new I check it against what is already there, and if it does not fit I offer a smaller piece or a later date.
This semester I managed the coding club contest and my project deadlines without missing either. I still have to watch it, but I catch it much earlier now.
Tips
- Avoid fake weaknesses like "I'm a perfectionist" or "I work too hard".
- Never name a weakness that is core to the job, such as weak coding for a developer role.
- Spend most of the answer on what you changed.
Likely follow-ups
- Give me another weakness.
- How would you handle a manager who keeps adding work?
HRCareer goalsEasyWhere do you see yourself in five years?
Where do you see yourself in five years?
What they are checking: Whether your plans fit this company and whether you are likely to stay long enough to repay the training.
Model answer
In five years I want to be someone my team relies on for a whole area of the product, not just individual tasks.
For the first two years I want to get really good at the technology I'm assigned, earn a certification in it, and understand how our client's business works. After that I'd like to lead a small module, review juniors' code and talk directly with the client.
This company's training and the range of projects here make that path realistic, which is a big reason I applied.
Tips
- Show growth inside the company.
- Do not say you plan to leave for an MBA or a startup.
HRFitMediumWhy should we hire you?
Why should we hire you?
What they are checking: Can you match your skills to what the job needs, in a confident but not arrogant way?
Model answer
From the job description, you need someone who can write clean code in Java, work with databases, and learn new tools quickly.
I have used Java for three years and built two projects with Spring Boot and MySQL, one of which is used by 400 students. During my internship I learned a reporting tool I had never seen, in a week, and shipped a feature with it.
I also communicate clearly. I explain concepts to juniors every week in our coding club, which will help when I work with teammates and clients. I'm ready to start contributing early and keep learning.
Tips
- Read the job description and reuse its words.
- Give three reasons, each with evidence.
HRFlexibilityEasyAre you willing to relocate to any location and work in night shifts if needed?
Reported at TCS, Infosys, Wipro, Accenture, Cognizant, Capgemini
Are you willing to relocate to any location and work in night shifts if needed?
Reported at TCS, Infosys, Wipro, Accenture, Cognizant, Capgemini
What they are checking: Mass recruiters place freshers wherever projects need them. A hesitant answer can end the interview.
Model answer
Yes. I understand that projects are spread across cities and time zones, and as a fresher I want the widest set of opportunities.
I have already lived away from home for four years in a hostel, so moving cities is not a concern for me. If a client needs support in their time zone I'm comfortable with shifts. I'd only ask to know the schedule in advance so I can plan around it.
Tips
- If you have a genuine constraint, mention it honestly but briefly; do not bargain in the first round.
HRClosingEasyDo you have any questions for us?
Do you have any questions for us?
What they are checking: Interest and preparation. Saying "No" signals that you have not thought about the job.
Model answer
Yes, two questions.
First, what does the first six months look like for a fresher in this role? I'd like to know how training and project allocation work so I can prepare in advance.
Second, what do the freshers who do best here have in common? I want to know what to focus on from day one.
Tips
- Ask about the work, training, team or success in the role.
- Skip questions on salary, leave or work from home in early rounds unless the interviewer raises them.
- Never ask something that is on the first page of their website.
