WhatsApp Contact Discovery in India round·Product Management·Easy·20 min

Meta RPM Interview — WhatsApp Contact Discovery in India

20 min · 1 credit · scorecard at the end

Take this on a laptop or desktop — not your phone. The live interview needs a full screen and keyboard (including a sketch whiteboard on coding rounds). You can buy now, but start it from a computer.

ZeroPitch Research Desk

Updated 2026-05-16 · Newly added · be among the first to take it

Field: Product Management
Company: Meta
Role: Rotational Product Manager
Duration: 20 min
Difficulty: Easy
Completions: New
Updated: 2026-05-16

How to prepare

What this round tests, what strong and weak answers sound like, and the traps to sidestep.

What this round is about

Topic focus. You improve WhatsApp contact and group discovery for a first-time smartphone owner in Tier 2 or Tier 3 India whose address book is almost empty.
Conversation dynamic. The interviewer works the problem with you, interrupts when the answer drifts, asks one sharp question at a time, and never says whether an answer landed.
What gets tested. Whether you pick one user segment and hold it, define a success metric from scratch, name tradeoffs out loud, and use the India constraints that actually bind.
Round format. A single twenty-minute product sense conversation that escalates from framing to a pressure probe to a short reflection.

What strong answers look like

One user, held all the way. You name a specific person, for example a first-time smartphone owner in a Tier 3 town with three saved contacts, and never drift off them.
Metric built from scratch. You define success with a clear denominator and a guardrail, for example the share of new users reaching a first real conversation within seven days, guarded against spammy group adds.
Tradeoff resolved out loud. You propose two or three ideas and kill the weaker one with a stated reason rather than listing everything.
India constraints as design variables. You reason about low-end Android, data cost, connectivity, and regional language as binding, not as decoration.

What weak answers look like (and how to avoid them)

Feature-first. Jumping to a solution before naming the user and the goal. Say who it is for and what success means before any idea.
Vague segments. Offering overlapping groups like new users so follow-ups collapse. Pick one segment with an explicit reason and commit.
Vanity metric. Choosing total messages or DAU that rises even when the new user is still lost. Tie the metric to that user reaching value.
US power-user framing. Assuming reliable data and a mid-range phone. Anchor every choice to the low-end device and metered data reality.

Pre-interview checklist (2 minutes before you start)

Recall why the screen is empty. Have one sentence on how contact discovery runs on the phone address book and why it is barren for a first-time user.
Identify one segment in advance. Pick the precise person you will design for so you do not stall when asked to choose.
Think of your success metric shape. Have a denominator and a guardrail in mind before you are asked to define it.
Pull up the non-address-book channels. Be ready to discuss group invite links and click-to-WhatsApp as discovery paths.
Have a privacy answer ready. Know how you would rework a suggested-contacts idea if the contact graph cannot be exposed.
Recall the India constraints. Keep device, data cost, connectivity, and regional language ready to apply.

How the AI behaves

Probes every claim. It asks for the denominator and the guardrail behind any metric you state, not the headline.
No mid-interview praise. It will not say great answer or validate; it acknowledges a detail and pushes.
Interrupts on abstraction. It stops a vague segment or a feature list and makes you commit to one user.
Holds the privacy line. It raises a contact-graph privacy objection and expects you to rework, not defend stubbornly.

Common traps in this type of round

Solution before user. Naming a feature before stating the user and the goal.
Segment that does not hold. Picking a broad or overlapping group so later answers contradict each other.
Metric with no denominator. Stating a number that has no base and no guardrail.
Metric that cannot move the goal. Choosing a count that rises while the new user is still stuck.
Framework recital. Naming a method without adapting it to WhatsApp or the India user.
Connectivity-blind design. Assuming reliable data, English UI, and a mid-range phone for a Bharat first-time user.

How to use the canvas in this round

Sketch the user first, then everything else. Put your chosen first-time smartphone owner on the canvas with name, town, and the rough state of her address book labeled. The persona on the board is what stops you drifting to a different segment halfway through.
Draw the discovery channel tree. Branch out from her into address book, group invite links, mutual-group context, click-to-WhatsApp, business directory. Each branch should have one line on the mechanism. When you propose an idea, mark which branch it lives on.
Strike through the privacy-blocked branch when the objection lands. Do not just say I would use a different mechanism. Cross out the blocked branch on the canvas, add the new one, write the mechanism under it. The rework only counts if it is visible.
Pair the win signal with the early-warning signal. Write the success metric with its denominator on one side and the guardrail with its rollback threshold on the other. The catch number should be as visible as the headline.
List the India constraints visibly. A short strip on the canvas naming low-end device, metered data, intermittent connectivity, and regional language keeps them in the room so you do not quietly forget any of them.

Reference

The full breakdown

How you're scored, the questions candidates ask most, and the research this interview is built on. Skim it — or just start the interview.

Interview framework

You will be scored on these 7 dimensions. The full rubric with definitions is below.

Segment Discipline

Whether you pick one specific user and hold that person through every later answer instead of drifting across vague groups.

20%

Metric Authorship

How well you build a success metric from scratch with a real denominator, timeframe, and a guardrail rather than naming a dashboard count.

20%

Tradeoff Resolution

Whether you choose between competing ideas by stating out loud what the chosen one sacrifices.

17%

India Constraint Grounding

Whether device, data cost, connectivity, and regional language shape your design as binding limits rather than decoration.

15%

Constraint Recalibration

Whether you keep the user goal alive and rework the design when the privacy limit removes your first idea.

Structured Narration

Whether your reasoning is sequenced clearly enough that the interviewer can follow your logic in real time.

Canvas Discovery Tree Visualization

Whether the user anchor, the discovery channel tree with the privacy-blocked branch struck through, and the metric pair exist on the canvas as visible artifacts, not just narrated verbally.

15%

What we evaluate

Your final scorecard breaks down across these dimensions. The full rubric and tier criteria are revealed inside the interview itself.

Prioritized User Segment Discipline17%
From-Scratch Success Metric Rigor17%
Tradeoff Decomposition And Kill Decision16%
India Constraint Binding Reasoning14%
Privacy Constraint Recalibration12%
Structured Reasoning Narration9%
User Anchor And Channel Tree On Canvas15%

Common questions

What does the Meta RPM product sense round actually test?

It tests whether you can take an open product prompt, in this case improving WhatsApp contact and group discovery for first-time smartphone users in India, and reason like a product manager rather than a feature list. The interviewer is checking that you pick one prioritized user segment and hold it, define a success metric from scratch with a real denominator and a guardrail, name tradeoffs out loud and kill an option with a reason, and ground the design in the India constraints that actually bind, such as sparse address books, low-end Android, data cost, connectivity, and regional language. Recited framework names do not score; structured reasoning the interviewer can follow does.

How should I structure my answer to this WhatsApp prompt?

Start by restating the user and the goal before any solution, then list a few candidate user segments and pick one with an explicit reason, for example a first-time smartphone owner in a Tier 3 town with an almost empty address book. State the job that person is trying to do, define what success looks like as a metric you build from scratch with a denominator and a guardrail, then propose two or three ideas and choose between them by naming the tradeoff and killing the weaker option. Close by saying what you would measure and how you would test it. Keep narrating so the interviewer can follow your logic in real time.

What are the most common mistakes candidates make here?

The frequent failures are jumping straight to a feature before naming the user and the goal, giving vague or overlapping segments so follow-ups collapse, and picking a success metric like total messages or DAU that rises even when the new user is still lost. Others recite a framework name without adapting it to WhatsApp or India, focus on features instead of the user problem and the business outcome, ramble without structure, or answer as if for a US power user and never mention a low-end phone, a data pack, or a regional language. Each of these maps to a real no-hire pattern from Meta interview reports.

How is this AI interviewer different from a real Meta interviewer?

It behaves like a real Meta RPM loop interviewer in the ways that matter: it interrupts when your answer drifts, asks one sharp question at a time, probes at least once before moving on, and never tells you whether an answer was good. The differences are that it is available on demand, it stays strictly in the product sense domain for the full session, and it produces a written transcript-backed scorecard afterwards that names the exact moment your segmentation or metric broke. It will not coach you during the round or hint at an outcome, exactly like the real loop.

How is the scoring done in this practice round?

Your transcript is evaluated against the specific signals this round cares about: whether you anchored on one prioritized segment, whether your success metric had a denominator and a guardrail, whether you named and resolved a tradeoff, whether you used the binding India constraints, and whether your reasoning was structured enough to follow. Each dimension is scored independently from the transcript text only, so delivery style, accent, and filler words do not count. The scorecard quotes the actual moments that earned or lost points so the feedback is concrete rather than a single number.

What should I do in the first two minutes of this round?

Use the thinking time to restate who the user is in one sentence and what goal you are optimizing, then sketch two or three candidate segments so you can pick one out loud with a reason. Do not start listing features. Have one sentence ready on why the cold-start screen is empty for this person, since the whole problem hinges on the sparse address book. Decide early what success would even mean for them, because the interviewer will ask you to define the metric from scratch and will push hard if it has no denominator or guardrail.

How do I handle the interviewer's privacy objection on a people-you-may-know idea?

Expect the interviewer to push that surfacing suggested contacts leaks the contact graph and will not survive WhatsApp's privacy posture or Indian regulatory scrutiny on cross-Meta data sharing. Do not abandon your goal under that pressure. Acknowledge the constraint, then rework the proposal so discovery happens through channels the user already controls, such as group invite links, mutual-group context, or opt-in flows, rather than inferred social-graph suggestions. The interviewer is testing constraint recalibration: whether you can keep the user goal while respecting a hard limit, not whether you can defend the original idea stubbornly.

What does a strong answer to this prompt sound like?

A strong answer names one user, for example a first-time smartphone owner in a Tier 3 town with three contacts saved, states the job they are hiring WhatsApp for, and never drifts from that person. It defines success as a clear metric with a denominator and a guardrail, for instance the share of new users who reach a first meaningful conversation within seven days, guarded against spammy group adds. It proposes a couple of ideas, picks one by naming what it sacrifices, and reasons explicitly about low-end Android, data cost, connectivity, and regional language as binding constraints, not afterthoughts.

Do I need to know WhatsApp's internal metrics to do well?

No. The round rewards defining metrics from first principles, not reciting WhatsApp's real dashboards. The interviewer explicitly expects you to build a success metric from scratch rather than choose from a list, so inventing a well-reasoned metric with a denominator and a guardrail scores better than naming a real internal metric you cannot justify. What you do need is a working mental model of how contact discovery functions, that it runs on the phone address book and phone-number identity, because the entire problem comes from that address book being nearly empty for a first-time user.

How does the India context change the answer versus a generic WhatsApp question?

India is the binding context, not flavor. The target user is often on a low-end Android phone with limited storage, paying for a metered data pack, on intermittent connectivity, and more responsive to regional-language content than English by roughly two to one in Tier 2 and Tier 3. Group invite links and click-to-WhatsApp entry points are the main non-address-book discovery channels for these users. A generic answer that assumes reliable data, a mid-range phone, and English UI will get interrupted. Treat language, device, data cost, and connectivity as first-class design variables that shape which discovery mechanism is even viable.

What happens after the round ends?

When the round closes you receive a transcript-backed scorecard rather than a verbal verdict. It breaks down how you performed on segment discipline, metric authorship, tradeoff reasoning, India-constraint grounding, and structured communication, and it quotes the specific moments where your answer strengthened or weakened. There is no live feedback during the session and the interviewer never hints at an outcome, mirroring the real Meta loop where recruiters often give no reason. The point of the scorecard is to show you exactly where the segmentation or metric broke so you can fix it before the real round.

Sources this interview is built on

Real candidate-report URLs (Glassdoor / AmbitionBox / PrepInsta / GeeksforGeeks / Medium) reviewed when authoring the questions, persona, and rubric. Verify the realism yourself.