Got an offer for a Product Designer role at Meta (Instagram team, Level 5) after going through the loop in early 2026. There's not much specific info out there for design loops at Meta so I wanted to share what actually happened.
The loop structure: Portfolio review screen (60 min, 1 interviewer) Design exercise (take-home, given 48 hours, then presented in a 60 min session) Onsite (3 rounds): portfolio deep-dive, product critique, cross-functional / Jedi behavioral
Portfolio review: They ask you to walk through 2-3 projects. The thing that surprised me: they don't care that much about the visual output. They want to understand your process. Specifically: How did you frame the problem before designing anything How did you involve research or data to inform decisions What tradeoffs did you make and why How did you work with PM and engineering What would you do differently
Don't show your prettiest work. Show your most interesting work -- meaning projects where you made real decisions under real constraints and can talk about the reasoning.
Design exercise: I was given a prompt about improving a specific flow in a social product (can't share details). 48 hours. They're not expecting polished high-fidelity Figma. They want to see how you think: do you start with user goals, do you consider edge cases, do you know when to stop and decide.
In the presentation, they'll interrupt you with questions mid-walkthrough. Lean into this. It's not adversarial, they're trying to understand where your decisions came from.
Product critique: They'll pick a Meta product (could be Instagram, WhatsApp, Facebook, Ray-Ban glasses) and ask you to evaluate it as a user and designer. Structure: what's working, what's not, what would you change and why. Practice this format on 3-4 different products before the interview.
What tripped people up in my cohort: Designers who led with aesthetics over reasoning. A beautiful deck with shallow thinking gets scored lower than a rougher deck with strong rationale. Meta cares a lot about impact and scale -- if your design feedback doesn't connect to user outcomes or business metrics, it reads as junior thinking at L5.