The short answer: Meta publishes its own TPM interview guide, and it defines the onsite as five 45-minute interviews: Technical Retrospective, Solution Design, Program Sense, Partnership and Behavioral. An engineer runs the Technical Retrospective, a cross-functional partner runs Partnership, and TPMs run the rest. Before the onsite, Meta describes a recruiter call, and candidate reports describe a technical screen with a Meta TPM. Meta says the whole process usually takes about 2 to 3 months. Meta treats AI tools as outside assistance unless Meta provides them, and only the tools inside the interview environment may be used. Last reviewed October 2026.
Meta Technical Program Manager at a Glance
Interview Rounds
6 to 7 rounds
Levels
Intern - Staff
Meta technical program manager interview: quick answers
| Question | Short answer |
|---|---|
| How many interview rounds? | Meta's TPM guide sets the onsite at five 45-minute interviews. Before it come a recruiter call and, per candidate reports, a technical screen with a Meta TPM. |
| What do the rounds test? | A deep dive into a past program you had a technical role in, a product and system design for an ambiguous problem, program leadership, cross-functional partnership, and five behavioral signals. |
| Do I have to code? | Meta's guide says the Technical Retrospective involves no code or complex algorithms. The technical bar sits in design: Solution Design asks for scale estimates, architecture, data model and APIs on a whiteboard. |
| Can I use AI tools? | No outside AI tools. Meta's TPM guide counts AI tools as outside assistance unless provided by Meta, and its hiring FAQ says only the tools available within the interview environment may be used. |
| How much does a Meta TPM make? | US postings list base salary of $160K to $272K, mostly in two bands: $168K to $234K and $199K to $272K. Postings mention bonus and equity on top of base. |
| How long does it take? | Meta says the process usually takes about 2 to 3 months. Follow up with your recruiter if you hear nothing within a week of your interviews. |
The Meta technical program manager role
What Meta technical program managers work on, the skills its job postings ask for, and what a week can look like. Meta posts the role as Technical Program Manager, often with a team name (for example Capacity Planning and Delivery, AI Infrastructure, ASIC or Ranking AI), and Technical Program Manager Intern.
Primary Focus
What You Need
- B.S. in Computer Science or a related field, or equivalent experience
- 10+ years in software, systems or hardware engineering or technical program management (general posting)
- Executive-level communication and influencing senior leaders
- Analytical problem solving on large-scale systems
- Cross-functional execution in a matrix organization
- Domain depth by team, such as ASIC design flow or network backbone topology
Nice to Have
- Using AI tools to redesign workflows
- Responsible AI practices
- Ongoing AI skill development
- Mentoring other TPMs (Capacity Planning and Delivery)
Want to ace the interview?
Practice with real questions.
A Week in the Life of a Meta Technical Program Manager
Illustrative week · Meta
An illustrative week for a technical program manager, built from what Meta says about the role in its own job postings and publications. Real weeks vary by team.
Culture notes
- Meta's guide describes a fast-moving, bottom-up environment where TPMs own large cross-company programs.
- TPMs are expected to be subject matter experts on their systems, and Meta's guide says they are not communication facilitators.
- Execution runs through a matrix organization, so influence without authority matters as much as the plan.
- Recent postings ask for AI skills, such as using AI tools to redesign workflows and responsible AI practices.
Key takeaway: Expect to own a cross-team program end to end and to be the person who can explain its architecture as well as its schedule.
Meta technical program manager levels and pay
Your level sets the bar you are interviewed against and the pay band of the offer.
Meta Technical Program Manager Levels
Each level has different expectations, compensation, and interview focus.
What This Level Looks Like
A 2027 internship for final-year students, with a supply chain and operations focus.
Interview Focus at This Level
Meta publishes no intern loop; the onsite guide is written for full-time TPMs.
Find your level
Practice with questions tailored to your target level.
Meta's TPM postings name no levels. Its TPM guide describes senior and staff expectations, and postings ask for 8+ years (Child Safety), 10+ years (the general TPM posting) or 12+ years with 8+ as a TPM and mentoring other TPMs (Capacity Planning and Delivery).
Pay in Meta's US job postings
Meta's US TPM postings each list one base salary range and mention bonus and equity on top. They name no levels, so the rows use the posting titles.
| Posting | Location | US base salary range |
|---|---|---|
| Technical Program Manager - Child Safety (Legal) | Los Angeles, Austin, Menlo Park, Washington DC, New York, San Francisco or Chicago | $160K to $223K |
| 4 postings: Technical Program Manager, Technical Program Manager, AI Infrastructure, Technical Program Manager, AI/ML and others | Several US locations | $168K to $234K |
| 4 postings: Technical Program Manager, Capacity Planning and Delivery, Technical Program Manager - Ranking AI, Technical Program Manager, Infrastructure Software Systems and others | Several US locations | $199K to $272K |
Two bands cover most postings: $168K to $234K and $199K to $272K. The Capacity Planning posting in the higher band asks for 12+ years, and the Child Safety posting asks for 8+. The intern posting, which lists monthly pay, is left out. Ranges seen October 29, 2026.
Meta technical program manager interview process
The onsite rounds, their length and what each one tests come from Meta's TPM interview guide. The recruiter call and the timeline come from Meta's hiring process page, and the technical screen comes from candidate reports.
6 to 7 rounds·~8 to 12 weeks end to end
Screen
2 roundsRecruiter call
Meta says the recruiter call covers your background and goals. Some roles use a prescreen form instead.
Tips for this round
- Have a clear story for why you want this role at Meta; Meta's guide says to know it.
- Ask whether your loop follows the five-round TPM guide and which team you are interviewing for.
Technical screen
Meta does not describe this screen for TPMs. Candidate reports say it covers your resume and experience, plus program sense, conflict resolution, prioritization, behavioral and system design questions at less depth than the onsite.
Onsite
5 roundsTechnical Retrospective
A deep dive into a past program where you had a technical role: your end-to-end understanding, a deep dive into its components, and troubleshooting a production problem. Meta says there is no code or complex algorithms. Its suggested shape is the problem (5 minutes), a system overview (2), the solution deep dive (25) and troubleshooting (5).
Tips for this round
- Follow Meta's shape: problem in 5 minutes, overview in 2, deep dive for 25, troubleshooting for 5.
- Reread the design docs of the project you pick and be ready to defend choices like build vs buy or SQL vs NoSQL.
- Prepare one production problem from that system and how it was found and fixed.
Solution Design
An ambiguous hypothetical product. Meta lists product clarity (scope, users, functional and non-functional requirements, KPIs, user flows), technical design (scale estimates, high-level architecture, services, data model, APIs, scaling, caching, partitioning, replicas), and metrics, trade-offs, dependencies and failure scenarios.
Program Sense
Questions on the program lifecycle: kickoff, turning ambiguity into a program, buy-in, goals and KPIs, prioritization, risk mitigation, execution and communication. Meta names seven focus areas: program complexity, strategy, prioritization, execution, risk mitigation, ambiguity and communication.
Partnership
How you collaborate with partners, communicate and influence without authority, including pushing back with leaders.
Behavioral
Meta lists five signals: resolving conflict, growing continuously, embracing ambiguity, driving results and communicating effectively.
Tips to Stand Out
- In Solution Design, define the problem, users and product needs before any architecture, then tie metrics to the MVP.
- Go deep on technical design, including database types and partitioning, and carry every feature you propose into the architecture.
- Practice common designs on a whiteboard, such as a chat app, a feed, a video app, a location service, a reservation system and a shopping app.
- For the Technical Retrospective, pick a project you can explain at both high level and in detail, reread its design docs, and discuss each trade-off as it comes up.
- Prepare for Solution Design before the Technical Retrospective, since it gives you a structure for explaining your past system.
- Use STAR with real examples and be honest about failures; Meta says theoretical answers get redirected to a real example.
Based on Meta's own pages and candidate reports.
Meta says each onsite interview leaves a few minutes for your questions and that the whole process usually takes about 2 to 3 months. A candidate guide labels the rounds a little differently but describes the same five-round shape and puts the process at four to eight weeks. Last reviewed October 2026.
What is different at Meta
- Meta wants TPMs who go deep. Its guide says TPMs are not crisis managers, technical consultants or communication facilitators. They dive deep into system design and architecture and act as subject matter experts.
- The interviewers are mixed. An engineer runs the Technical Retrospective and a cross-functional partner runs Partnership, so two of the five rounds are judged by the people you would work with every day.
- Solution Design blends product sense with system design. Users, requirements and KPIs come before the architecture, and Meta asks you to carry every feature you propose into the technical design.
- The bar rises with level. For Program Sense, Meta expects senior candidates to bring more complex, ambiguous programs, and says staff-level candidates often spotted an unowned opportunity and drove it. For Partnership, staff-level candidates show two-way communication and push back with leaders.
- TPMs work across the whole company. Product TPMs sit between technical execution and business strategy across Facebook, WhatsApp, Instagram, Messenger and Reality Labs, and infrastructure TPMs run capacity planning cycles for compute, storage, GPU and network capacity.
- AI shows up in the job and in the rules. Recent postings list AI-related preferred qualifications, such as using AI tools to redesign workflows. In interviews, Meta counts AI tools as outside assistance unless Meta provides them.
Meta technical program manager interview questions
Questions from our bank, then practice prompts we wrote for this guide around Meta's work.
Questions tagged Meta
From the DataInterview question bank, where our team tags each question with the companies it fits. Open one to answer it and compare with the solution.
Design Facebook News Feed
Design Messaging System
Instagram Design
Facebook Marketplace Design
Design Instagram Hot Topics
Messaging App Consolidation
System Architecture Experience
Improve Facebook BuySell Groups
Solution design practice
Prompts we wrote for this guide around Meta's work. They are not reported interview questions. Each answer is an outline or a worked solution.
Design live location sharing for WhatsApp groups: a user shares their location with a group for up to an hour. Assume 10 million active sharing sessions at peak, one update every 30 seconds, and 5 viewers per session on average.
Sample Answer
Start with product clarity: who shares, who sees it, how it stops, and privacy controls. KPIs could be share starts and sessions ended by the user instead of by timeout. Scale: 10,000,000 / 30 = about 333,000 location writes per second, and with 5 viewers each, about 1.67 million deliveries per second. Keep only the latest location per session in memory with a time to live, since history is not needed, and push updates over the existing messaging connection. Cover end-to-end encryption, battery use and what viewers see when the sharer loses signal.
Design video uploads for Facebook Groups. Assume 2 million uploads a day at 50 MB each.
Design event RSVPs for Facebook Groups where events have limited spots. A popular event has 500 spots and 50,000 people try to RSVP in the first minute.
Design the home feed for Instagram, showing recent posts from accounts a user follows. Assume 500 million daily users who open the feed 10 times a day.
Technical retrospective practice
Prompts we wrote for this guide around Meta's work. They are not reported interview questions. Each answer is an outline or a worked solution.
Give the 2-minute system overview of a program you led, the way you would open a Technical Retrospective.
Sample Answer
Name the problem and who it served, then the main components and how data flows between them, in plain terms. Point out the one or two components you will go deep on and why they mattered to the outcome. Stop at two minutes so the interviewer can steer, since Meta's suggested shape gives most of the time to the deep dive.
The interviewer asks why your program used a NoSQL store instead of a relational database. How do you answer?
Walk through a production problem in the system from your program: how it was detected, diagnosed and fixed.
Your program chose to buy a vendor system instead of building one. Defend the decision.
Program sense practice
Prompts we wrote for this guide around Meta's work. They are not reported interview questions. Each answer is an outline or a worked solution.
Ranking AI teams request 12,000 GPUs for the next half. Capacity planning can deliver 9,000. How do you run the decision?
Sample Answer
The shortfall is 3,000 GPUs, 25% of demand (3,000 / 12,000). Get each request tied to its expected impact and its date, since some demand may be needed late in the half. Look at levers: efficiency work that frees capacity, shifting some training to off-peak, and moving delivery dates. Bring leadership a ranked list with what each team gets, what it loses and the risk of each option, and agree on a review point if supply changes. Communicate the outcome to every team with the reasoning.
You are asked to "improve integrity enforcement on Groups" with no further detail. How do you turn it into a program?
Two product teams both need the same infrastructure team in the same quarter, and that team can only support one. What do you do?
A network backbone upgrade will miss its date by three weeks because of a supplier delay. Two launches depend on it. How do you handle it?
Behavioral practice
Prompts we wrote for this guide around Meta's work. They are not reported interview questions. Each answer is an outline or a worked solution.
Tell me about a conflict between two teams that you resolved.
Sample Answer
Meta lists resolving conflict as a behavioral signal. Explain both positions fairly, how you found the shared goal, what you proposed and the outcome. Say what the relationship looked like afterward.
Tell me about a time you pushed back on a leader.
Tell me about a program that failed or fell short.
Tell me about an opportunity nobody owned that you turned into a program.
Practice problem: allocate scarce capacity by priority
pythonA capacity planning cycle has supply per region (a dict of region to units) and a list of requests, each (team, region, units, priority), where a lower priority number goes first. Write allocate(supply, requests) that grants requests in priority order (ties keep the input order), giving each request as much as its region has left. Return (granted, shortfall): granted maps each team to its total units granted, and shortfall maps each team with unmet demand to its total unmet units. Raise ValueError for an unknown region or a negative unit count. Example: supply {"prn": 100, "odn": 50} and requests [("ranking", "prn", 80, 1), ("ads", "prn", 40, 2), ("genai", "odn", 60, 1)] return ({"ranking": 80, "ads": 20, "genai": 50}, {"ads": 20, "genai": 10}).
1from typing import Dict, List, Tuple
2
3def allocate(supply: Dict[str, int], requests: List[Tuple[str, str, int, int]]) -> Tuple[Dict[str, int], Dict[str, int]]:
4 """Return (units granted per team, unmet units per team with a shortfall)."""
5 pass700+ coding problems with a live code executor.
Practice in the EngineHow to prepare
A plan for the Meta loop, most important first:
- Read Meta's TPM interview guide and plan your prep around its five rounds: Technical Retrospective, Solution Design, Program Sense, Partnership and Behavioral.
- Practice Solution Design on a whiteboard with Meta-style products (chat, feed, video, location, reservations, shopping), product clarity first and architecture second.
- Pick your Technical Retrospective project, reread its design docs and rehearse the 5, 2, 25, 5 minute shape, including one production problem.
- Build Program Sense stories that cover the full lifecycle, from kickoff and buy-in to risks and communication, at the complexity your level calls for.
- Prepare Partnership and Behavioral stories for each of Meta's five signals, including a time you pushed back on a leader.
- Do mock interviews with no outside help, since Meta counts AI tools as outside assistance unless it provides them.
Practice path
Courses that cover the rounds above:
Are you ready for the Meta technical program manager interview?
1 / 6Can you plan a multi-team launch: milestones, dependencies, risks and how you track them?
Frequently Asked Questions
How many rounds is the Meta technical program manager interview?
Meta's TPM guide defines five 45-minute onsite interviews: Technical Retrospective, Solution Design, Program Sense, Partnership and Behavioral. Before the onsite there is a recruiter call and, per candidate reports, a technical screen with a Meta TPM.
What is the Meta TPM Technical Retrospective?
A 45-minute interview with an engineer about a past program where you had a technical role. You explain the problem, give a short system overview, go deep on the solution and its components, and troubleshoot a production problem. Meta says there is no code or complex algorithms, and suggests rereading the design docs of the project you pick.
Can I use AI tools in a Meta TPM interview?
No outside AI tools. Meta's TPM guide says outside assistance includes using AI tools unless provided by Meta, and its hiring FAQ says only the tools available within the interview environment may be used. The FAQ mentions an authorized AI assistant in some software engineering technical interviews, but does not say whether TPM interviews use it.
How much do Meta technical program managers make?
In US postings seen in October 2026, the general TPM posting and the AI Infrastructure, AI/ML and ASIC postings list $168K to $234K base. Capacity Planning and Delivery, Ranking AI, Infrastructure Software Systems and Network Infrastructure list $199K to $272K, and Child Safety lists $160K to $223K. Postings mention bonus and equity on top.
How is a Meta TPM different from a project coordinator?
Meta's guide says TPMs are not crisis managers, technical consultants or communication facilitators. They dive deep into system design and architecture and act as subject matter experts, which is why the loop includes a technical retrospective with an engineer and a solution design round.
Does Meta hire TPM interns?
Yes. Meta posts a Technical Program Manager Intern role in Reality Labs for 2027, based in Sunnyvale or Seattle, for final-year bachelor's or master's students in engineering, supply chain, operations or business. It lists US pay of $6,688 to $10,800 per month. A second 2027 TPM internship in Reality Labs Global Supply Management appears in job search.
Are Meta TPM roles remote?
Most postings list offices such as Menlo Park, Sunnyvale, Bellevue, Seattle, New York and Fremont. The general TPM posting also lists Remote, US. Meta's guide says video interviews may require screen sharing and asks you to turn off video filters, including blurred backgrounds.




