# Meta Product Sense Interview (2026 Guide)

Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access.

Source: https://www.aced.io/blog/meta-product-sense-interview
Source observed: 2026-11-04T22:02:47.642Z
Last checked: 2026-11-04T22:02:47.642+00:00
Indexed: 2026-11-05T02:36:46.311+00:00

---

# Meta Product Sense Interview (2026 Guide)

Meta's product sense interview asks candidates to design a product from scratch, defend decisions under follow-up pressure, and increasingly prototype solutions live with AI tools. This guide covers traditional and AI product sense formats for individual-contributor and manager-level loops.

- [Meta](https://www.aced.io/blog/tag/meta-facebook)
- Last updated a month ago by Aced Team
- The guide is based on firsthand accounts from Meta PM candidates and one Meta PM interviewer, covering traditional and AI formats across IC and manager-level loops.

## Meta's Product Sense Interview

The loop varies by level:

- **IC roles (L5/P4–P5):** Typically two phone screens—one product sense and one product execution/analytical—followed by an on-site product sense round, analytical round, and behavioral/leadership round. Some candidates report a gate in which Meta reviews phone-screen performance before advancing to the on-site.
- **Manager-level roles (L7 equivalent):** One Google director who interviewed for Meta's PM leadership track described six on-site rounds: people management, cross-functional partnership and influence, execution, operating/project retro, product sense, and metrics. He also completed multiple recruiter screens and a PM aptitude screen; the process took months.
- **Timing:** Each round is typically 45–60 minutes. The interviewer is a Meta PM, although their team and background may have little connection to the question.

Meta introduced an AI product sense round in late 2025. Candidates spend the first 30 minutes on a traditional product sense case—clarifying questions, user segmentation, and solution design—then spend the remaining 30 minutes vibe coding the solution in a Llama-based prototyping tool.

[Read more about the product sense interview](https://www.aced.io/blog/product-sense-interview?ref=exponent-blog.ghost.io) and [read firsthand interview experiences from Meta candidates](https://www.aced.io/experiences?company=meta-facebook&ref=exponent-blog.ghost.io).

## Meta Product Sense Interview Questions

[Browse Meta product manager interview questions](https://www.aced.io/questions?company=meta-facebook&page=1&role=pm&ref=exponent-blog.ghost.io).

### Phone screen questions

- **“Design a parking solution.”** The prompt supplied no context or constraints, so the candidate had to scope it through clarifying questions.
- **“You're a product manager at Meta tasked with making a tool to connect handymen with consumers. How would you design the product?”** The interviewer specified domestic use, web and mobile, and a required ROI.

### On-site product sense questions

- **“Design a product for volunteering.”** One version was: “You're a PM at Meta. You've been put in charge of a brand new product for volunteering. What would you do and why?”
- **“Design a parking solution for Google Maps.”**
- **“Design a solution for contractors.”** The candidate asked whether it should live on an existing Meta platform; the interviewer said yes, and the candidate built it on Facebook.
- **“Build me a Facebook events product.”** At L7 level, clarification narrowed the prompt to going to the movies together.

### AI product sense questions

- The volunteering prompt, followed by prototyping in Meta's Llama-based tool.
- **“If Meta wanted to create a map app, how would you go about creating it?”** The same 30/30 format was used.

### Analytical questions often bundled with product sense

- **“Determine a north star metric for Instagram Reels.”** Candidates had to prioritize Reels over Stories and defend the choice, including counter and guardrail metrics.
- **“Define north star metrics for live events on Facebook.”**
- **“You're the PM for notifications—the bell icon in Facebook. Why would Meta build this, how would you set goals, and how would you measure success?”**

## Follow-ups and trade-offs

Follow-ups introduce constraints that put metrics into conflict. Common examples include:

- A handyman tool's monthly active users rise for consumers and businesses while monthly active users on Facebook decline.
- A handyman product performs well in New York but not California.
- Notification engagement rises weekly for six weeks across all users, geographies, and mobile apps while time on site remains stable or declines. In one case, “engaging” meant clicking comment notifications, replying, and immediately exiting the app.

Expect **“How would you improve this?”** and **“How would you measure success?”** on almost any product sense question. For trade-offs, first clarify the metric definition, enumerate possible explanations, then prioritize which explanation to investigate and why.

## Meta's AI Product Sense Round

The AI round uses a strict **30/30 format**:

1. **First 30 minutes:** Run a traditional product sense case—clarifying questions, user groups, pain points, and a solution. Stop at the solution.
2. **Remaining 30 minutes:** Use Meta's internal Llama-based chatbot to prototype what you described.

The tool is described as roughly similar to Vercel's v0: candidates enter prompts, receive an app preview in a side panel, then refine features, add pages, and adjust the UI. The first generation takes five to seven minutes. One January 2026 candidate entered notes, assumptions, pain points, user groups, and a solution, then requested a volunteer-opportunity listing page and onboarding page.

Follow-ups fall into three buckets:

- **Technical AI:** Token optimization, latency, inference compute, and retrieval. Examples include improving a prototype for compute power, token optimization, and latency; deciding whether explicitly specifying a pie chart uses more tokens than allowing the LLM to choose; sourcing geographic data; optimizing retrieval; and integrating directions.
- **Prompting strategy:** Why a prompt was written a certain way, whether a more efficient approach exists, and how to handle edge cases surfaced by the LLM.
- **Product:** User onboarding, incentives for users to provide data for recommendation improvements, standalone app versus Facebook integration, and mobile versus web.

The follow-ups depend heavily on whether the interviewer is an AI specialist or generalist PM. The guide emphasizes that candidates should not spend the round polishing UI at the expense of backend functionality, data sourcing, retrieval, and technical discussion.

Prepare by practicing with v0 (Vercel) and Lovable, completing three to five full prototypes on a 30-minute timer, and learning the basics of token optimization, latency trade-offs, and retrieval-augmented generation. Use generation time to review notes, identify out-of-scope features, and prepare for what would change in a production app.

## Meta Interview Rubric

General product sense criteria include problem framing, creativity, user empathy, and structured thinking. Meta-specific signals include:

- **Clear user segmentation:** Explain how users are segmented, why one segment is prioritized, and the reasoning behind that choice.
- **Metrics depth:** A north star metric is not enough. Prepare secondary, guardrail, and counter metrics, with the reasoning for each.
- **Response to interviewer guidance:** Some interviewers guide candidates toward a framework; others provide no feedback. Be ready for both.
- **Connection to Meta's mission:** Bring answers back to Meta's mission of connecting people.

## Common Mistakes

- **Poor time management:** Starting the AI prototype with only 20 minutes left leaves too little time for technical follow-ups. A useful approach is to divide calls into thirds and check in at each interval; enforce the 30/30 split for AI rounds.
- **Insufficient metrics depth:** Prepare north star, secondary, guardrail, and counter metrics for every practice question.
- **Too few clarifying questions:** Scope ambiguous prompts early, such as what “volunteering” means or whether a contractor product belongs on an existing Meta platform.
- **Ignoring interviewer signals:** Follow a redirect rather than spending time fighting it.
- **Over-indexing on UI in the AI round:** Treat the prototype as a vehicle for discussion, not the deliverable.
- **Not spacing out rounds:** One candidate recommended two to three weeks between rounds, with up to a month if needed.

## How to Prepare

- Read [Meta product manager interview questions](https://www.aced.io/questions?company=meta-facebook&page=1&role=pm&ref=exponent-blog.ghost.io).
- Practice at least 20–30 questions by speaking through or writing answers. Use our [questions database](https://www.aced.io/questions?sortBy=most-popular&type=product-design&ref=exponent-blog.ghost.io) and [PM interview course](https://www.aced.io/courses/pm?ref=exponent-blog.ghost.io).
- Use a timer and divide calls into thirds; enforce the AI round's 30/30 split.
- Practice three to five timed AI prototypes with v0 or Lovable, focusing on efficient prompting rather than pixel-perfect UI.
- Network with Meta PMs; one L7 candidate spoke with 10 Meta PMs before the loop.
- Study Facebook, Instagram, WhatsApp, and Messenger, and connect answers to the “connect people” mission.
- Practice north star, secondary, guardrail, and counter metrics. Our mock on [designing Facebook Movies](https://www.aced.io/courses/product-analytics-product-sense/mock-interview-facebook-movies?ref=exponent-blog.ghost.io) covers the type of product sense question reported at L7.
- Senior candidates should expect 100+ hours of preparation; IC candidates typically prepare for weeks.
- Schedule two to three weeks between phases, extending to a month when needed.

## Coaching and related resources

- [Browse Meta interview questions](https://www.aced.io/questions?company=meta-facebook&src=blog)
- [Book time with a Meta coach](https://www.aced.io/coaching?company=meta-facebook) for mock interviews, career coaching, or resume review
- The coaching card shows a 96% rating from 5,400 reviews.
- [Create your free account](https://www.aced.io/signup?src=blog)

## Related blog posts

- [Meta Behavioral Interview Guide and Top Questions](https://www.aced.io/blog/meta-behavioral-interviews) — a month ago · 7 min read
- [Meta Layoffs Tracker](https://www.aced.io/blog/meta-layoffs) — a month ago · 4 min read
- [Get a Job at Meta: Interview Process and Top Questions](https://www.aced.io/blog/the-meta-facebook-interview-process) — a month ago · 10 min read
- [How to Get a Meta Job Referral](https://www.aced.io/blog/how-to-get-a-meta-referral) — a month ago · 8 min read

---

[Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fblog%2Fmeta-product-sense-interview&trace=t_679ff9ab98f3)

## Ask a follow-up about this page

Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required.

Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup.

`GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3`

[Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fblog%2Fmeta-product-sense-interview). Opening a form does not execute a tool.