Meta · Senior (L5)
Recommended next: your first attempt
A complete first attempt shows where you stand before any narrow practice starts.
Pick a round to see what it asks of you and where you stand on it.
Present your own work as a decision narrative that makes personal ownership, craft choices, evidence and learning easy to examine.
The reviewer challenges whether the result came from your change.
A partner preferred the alternative you rejected.
Choose two projects with different product problems or decision types. Gather the original brief, key constraints, your artifacts, research notes, outcome data, and one decision that you personally owned.
The supplied guide reports two portfolio projects in a 45-minute assessment. Complementary evidence helps you show scope without turning the presentation into a feature tour.
Company researchMeta Product Designer interview guide
For each project, write a short sequence: user and business problem, constraints, alternatives, pivotal decision, iteration, outcome, and lesson. Mark team work, your work, measured results, and assumptions separately.
A first attempt takes the full 45 minutes.
Prepare a portfolio screen, panel portfolio review, app critique, design problem-solving exercise, and behavioral conversation. Meta design preparation rewards visible craft decisions, clear problem framing and constructive collaboration. This plan uses a recent L4/L5 guide corroborated by an older candidate account; some pipelines add an early critique. In-room portfolio practice rehearses your narrative, while critique cases provide a self-contained product description.
Every session saved against this target, newest first. Standings live on the round cards.
Initial portfolio review, Panel portfolio review, App critique, Design problem solving, and Collaboration and growth have no attempts yet.
This format makes the link from problem to decision to outcome easy to examine. It also protects against claiming team results as personal impact.
Suggested approach
Practice explaining one discarded alternative, the evidence behind the final choice, and a disagreement that changed the work. Keep the explanation brief enough to leave time for questions.
The round asks for decisions, alternatives, evidence, disagreement, and learning. A focused rehearsal prepares useful detail without completing a full mock round.
Suggested approach
You have selected two projects and a one-page evidence map for each, including ownership, alternatives, outcomes, and one lesson you can explain aloud.
Worth redoing if you hear something from the recruiter that contradicts this.
Questions that close the gaps above.
Where does this role need to raise the team’s craft bar?
How are product designers involved in choosing problems before execution?
How does the team validate new interactions with diverse users?