The Product Architecture Round
Intermediate · 20 min read · High-Level Design, Foundations
Meta's product-focused design interview: APIs, data models and client–server flows, with a worked example.
Meta runs two kinds of design interview for software engineers: System Design and Product Architecture. Candidates applying for product-focused roles are usually steered to Product Architecture, infrastructure roles to System Design, and some candidates are offered a choice.
What changes compared with System Design
The same question can go either way. "Design Instagram" in System Design means feed fan-out, media storage and CDN. In Product Architecture it means the endpoints the app calls, how a post, its likes and comments are modelled, how the feed pages, how a new comment appears for someone already viewing the post, and who…
The framework, adjusted
Two habits help a lot here:
Worked example: comments on posts
Choices to say out loud:
What interviewers look for
Common Product Architecture prompts
Practise by applying the same steps: requirements, entities, API, flows, deep dives.
Interview questions
- Why is cursor pagination the right default for a comment list?
- A user posts a comment but doesn't see it after refreshing. What's happening and how do you fix it?
- How would you show like counts on a comment that's receiving thousands of likes per second?
Practice
Write your answer before opening the suggested one. Anything you mark "Partly" or "Missed it" comes back in your review deck.
Further reading
Key takeaways
- Product Architecture centres on the user-facing product: requirements, data model, a concrete API and client–server flows.
- Write endpoints precisely: fields, pagination cursors, status codes and idempotency.
- Walk through user actions to drive out every call the app needs.
- Expected deep dives are user-visible: live updates, read-your-writes, counts, ordering, edits, deletes and privacy at read time.
- Scale still matters, but as a constraint on choices, not the main topic.
Previous: The HLD Interview Framework · Next: Back-of-the-Envelope Estimation