product sense · standard
"How would you improve WhatsApp?"
How would you improve WhatsApp?
Most candidates answer this with a student segment and a list of features WhatsApp already ships. That is a fast failure. The real test is whether you understand where WhatsApp’s growth actually lives in 2026 and whether your improvement connects to a problem businesses or users will pay Meta to have solved.
What the interviewer is actually checking
WhatsApp crossed 3 billion MAU in 2024. In India, its largest market at 853 million users, consumer MAU growth is running at 6% year over year and downloads fell roughly 49%. Consumer growth is saturated. Business messaging MAUs in India, by contrast, grew more than 130% since 2021 compared to 34% for the consumer app. WhatsApp is Meta’s primary monetization frontier in APAC and LATAM, and the interviewer is testing whether you know that. Candidates who frame the whole question around consumer engagement signal that they don’t follow the product seriously.
Know what already exists before you walk in: Channels (launched 2023), Communities (2022), Advanced Chat Privacy (2025), WhatsApp Pay live in India and Brazil, Meta Business Agent globally available June 2026, and video calls supporting up to 32 participants. Pitching any of these as new ideas ends the answer.
One more context point: as of January 2026, WhatsApp’s AI policy bans general-purpose chatbots on the platform and prohibits sharing chat data for AI training. Any AI improvement you propose has to work within that constraint or explicitly acknowledge it.
Structure a strong answer
Start with a scope assumption, name the segment and why, ground the pain in specific breakdowns, propose one improvement with a rationale, then give metrics that connect to Meta’s revenue model.
strong
"Before I dive in: I'll treat improvement as deepening value for an existing high-potential segment rather than acquisition, and I'll stay mobile-first since that's where 95%+ of usage happens globally. Let me know if you'd rather I go somewhere else.
WhatsApp's growth story in 2026 is business messaging, not consumer chat. Business MAUs in India grew 130%+ since 2021. That's where Meta is placing its monetization bet, so that's where I want to focus. The segment I'd pick: small-to-medium merchants in emerging markets, the tailor in Lagos, the caterer in São Paulo, the tutor in Mumbai, who run their entire business through WhatsApp but are doing it with consumer-grade tools.
Their core job is converting an inbound inquiry into a paid transaction without losing the thread. Three things block that consistently. First, conversation continuity breaks: a customer asks a question on Wednesday, the merchant is buried in other chats by Thursday, and the context is gone. There is no open-tickets view, no CRM layer. Second, trust asymmetry: buyers can't tell if they're talking to a real business or a scammer. WhatsApp's verified badge exists but is limited to large enterprises via the API. Third, the AI policy creates a coverage gap: WhatsApp banned general-purpose chatbots in January 2026, but small merchants need async coverage and can't be online 24/7. Meta Business Agent fills this for large companies; the long tail of small merchants gets nothing.
My proposed improvement: a Merchant Inbox mode inside WhatsApp Business. Not a new app. A distinct conversation view, surfaced inside the existing app and gated to WhatsApp Business accounts, that shows open, pending, and resolved customer threads like a lightweight helpdesk. Each thread gets a status tag, a last-message summary, and a one-tap shortcut to send a catalog item. For the AI piece: a rule-based auto-reply builder using keyword triggers like 'price,' 'available,' 'delivery,' with no LLM and no third-party data sharing. Stays fully compliant with the 2026 AI policy and solves the async coverage problem without creating a trust or spam risk.
Success metrics: merchant thread resolution rate (the share of inbound customer conversations that get a response within four hours), repeat-purchase rate from existing customers as a signal that relationship quality improved, and API conversion rate (the share of merchants who upgrade from WhatsApp Business App to the Cloud API after using this feature). That last one maps directly to Meta's revenue. The trade-off I'd watch: this adds complexity for the 200 million-plus businesses happy with simple messaging. Mitigation is progressive disclosure: Merchant Inbox is off by default and surfaces only after a merchant receives more than 20 inbound messages in a week."
weak
"I'd focus on the student segment. Students forget class timings and have trouble sharing large files. I'd add screen sharing on group calls, raise the file size limit to 2GB, and add a quiz feature inside group chats. Success metrics: daily active users and session duration." This fails on three levels: it pitches features WhatsApp already has or has changed (screen sharing exists, file limits are not the bottleneck students report); the student segment has no viable business case because Meta earns nothing from students sharing study files; and the metrics are disconnected from the feature entirely. Quiz adoption and file transfer volume are the relevant signals, not global DAU. The interviewer hears: this person doesn't use WhatsApp as a business tool and doesn't understand how Meta makes money.
The viable and lovable test
In 2026, feasibility is not the constraint. WhatsApp can ship almost anything technically. The question is whether it’s viable and lovable. Viable: does this improvement connect to a problem that businesses will pay Meta to solve, directly or by converting to the paid API tier? Lovable: does it meet merchants where they already work, anticipate the chaos of running a business over chat, and reduce friction rather than adding another surface to manage?
The student-with-files answer fails both tests. The Merchant Inbox answer passes both: merchants pay for the API when it reliably converts inquiries into sales, and the feature lives inside the tool they already use all day. That is the bar the interviewer is measuring against.