Went through the Meta TPM loop a few months ago for an E6 role. Posted a short version elsewhere but want to write a full breakdown here because the Meta TPM interview is genuinely different from other companies and the prep resources are thin.
First: Meta TPMs are not PMs. If you've been preparing using PM interview resources, stop. Meta TPMs are expected to be highly technical -- they own execution, manage dependencies across eng teams, write technical specs, and own project timelines. You will not be asked to 'design a product' or 'prioritize a roadmap.' You will be asked how you unblock engineering.
The loop (E6 TPM): Recruiter screen + hiring manager call Technical screen: usually a system design or architecture review Onsite: Technical execution round, cross-functional leadership round, Jedi behavioral, and one more that varied by team (for me it was an estimation/scoping round)
Technical execution round: This is 'show me how you run a project.' Expect: here's a vague engineering initiative, how do you break it down, how do you find dependencies, how do you track risk, how do you know when it's slipping before it slips. They'll give you a realistic scenario with ambiguity and watch how you structure it.
I got: 'We want to ship a new feature that requires changes to three backend teams and two client platforms. It has a 10-week deadline. Walk me through how you'd run this.' I spent about 35 minutes on that one. They kept adding complications (one team is understaffed, one dependency is external). It felt like a live war game.
Cross-functional leadership: How do you build relationships with skeptical engineering leads. How do you influence without authority (the Meta classic). How do you push back on executive pressure when the timeline is unrealistic.
Estimation round: I was not expecting this. 'How long would it take to migrate 50 million user records to a new schema without downtime?' You don't need the right answer. You need to decompose it clearly: batch size, migration strategy, rollback plan, dependencies. Think out loud.
What E6 vs E5 looks like: E6 TPMs own programs, not just projects. Cross-org alignment, influencing roadmaps, not just executing them. Your stories need to show that.