Updated by Meta candidates
Technical Program Manager (L5) Interview Experience
That technical retrospective was the one that stuck with me because the whole 45 minutes was just one architecture. I had to draw it end to end, go into every component, and explain what I actually did as the TPM.
Interview process
I got in through an internal referral, and the recruiter screen was just a normal background chat plus a process walkthrough. The first real screen was a standard TPM phone interview where I talked through a complex program, stakeholder management, and some behavioral stuff. After that the loop had five parts, and one of them was a pretty standard system design round on building a travel website. Another round was a full 45-minute technical retrospective where I had to stay on one architecture the whole time and explain it end to end. The rest of the onsite was the usual TPM mix of program management, partnerships with a PM, and a behavioral round tied to Meta values.
- Recruiter screen
- Phone interview
- Final round
Interview rounds
7 questions across 3 roundsRecruiter screen
1 questionOverview
I got in through an internal referral, and the recruiter screen was just a normal background chat plus a walkthrough of the process.
Question types asked
Specific questions asked
Can you walk me through your experience and the interview process?
I came in through an internal referral. We mostly went over my experience at a high level and what the interview process was going to look like. It felt pretty normal.
Phone interview
1 questionOverview
The first real screen felt like a regular TPM phone screen. It was mostly about a complex program I had worked on, how I handled stakeholders, and some behavioral questions.
Question types asked
Specific questions asked
How do you usually manage stakeholder alignment?
I treated it like a standard technical program management screen. I talked through a complex program I had run, how I managed stakeholders, and answered some behavioral questions. Nothing about that round felt unusual.
Final round
5 questionsOverview
The onsite loop was five parts and covered the full TPM spread. The standout thing was that one round was a pretty standard system design exercise, while another spent the entire 45 minutes on one deep technical retrospective.
Question types asked
Specific questions asked
What are the high-level functional and non-functional requirements?
How would you scale the application?
What components are likely to fail at scale?
I started with high-level functional and non-functional requirements, then moved into scale, drew the architecture, and talked through the different components and what would fail as traffic grew. The interviewer was a senior software engineer, so it felt like a pretty standard system design interview.
Tell me about a technically complex program you solved end-to-end.
Draw the architecture.
Can you go deeper on the flow? What was happening in each component?
What did you as the TPM do in the architecture decisions?
I drew the architecture end to end and then went level by level through the flow, explaining every component and the technical details behind it. I also had to be clear on what I, as the TPM, actually did in the architecture decisions. The whole 45 minutes stayed on that one retrospective.
This one was straight program management. I answered around risks, dependency management, stakeholder management, and the standard TPM-style scenarios they usually ask.
How do you resolve conflicts with internal partners?
How do you work with product managers specifically?
This round was with a product manager. I talked about how I work with cross-functional teams, how I partner with PMs, and how I handle conflict resolution when there is tension with internal teams.
How does that connect to Meta's mission and values?
This one was very tied to Meta values and mission. I had to answer around moving fast, why speed matters, and lessons learned, so it was basically a culture and values behavioral round.
Interview tips
For the system design, I would not overcomplicate it. Just use the normal framework, start with functional and non-functional requirements, then scale it, draw the system, and talk about which components fail. For the technical retrospective, be ready to stay deep on one technically complex program for the whole round and explain every layer of the architecture. The important part is not only the system itself, but also being clear on what you as the TPM actually did in those architecture decisions. I would also have solid stories ready for risks, dependencies, stakeholder management, cross-functional partnership, conflict resolution, and then go through Meta values because they ask pretty directly about moving fast, speed, and lessons learned.
Company culture
What I felt from them was speed. They look for fast solutions instead of waiting for more approvals and all that stuff, so they want you to cut short the extra process and move. It felt more like a startup culture than what people usually expect from a big company.
Get full access with a membership, or share your experience to try it free.
More Meta interview experiences
“It was a smooth experience. But it was not clear on what they were looking for as this was a generalised interview with team matching later”
“The interview was highly rigorous but followed a format: four interviews and then five rounds of on-site. The preparation material provided by the recruiter did really help. It's always better to understand from the recruiter what is expected and then prepare accordingly.”
See all 6 Meta Technical Program Manager interview experiences →
