Meta Technical Program Manager Interview Guide

Meta typically puts its TPM candidates through these stages for the interview:

1. Recruiter screen
2. Initial Screen
3. The onsite:
4. Technical Retrospective with an engineer, 
5. Solution Design with a TPM, 
6. Program Sense with a TPM, 
7. Partnership with an XFN partner, and 
8. Behavioral with a TPM
9. Hiring committee and offer

The round names we're using are official and verbatim from the material Meta uses for this interview (which we have thanks to our Meta TPM coaches). Much of this guide treats that PDF as gospel. We’ll drop excerpts so the main bits are straight from the horse’s mouth and include tips from our coaches so you can deliver on what the PDF demands of a candidate. 

This is a short 20-30 min call with a recruiter, usually after they've looked at your resume. They'll cover your background and your interest in the role and the conversation typically is non-technical. Some candidates say their recruiters did a quick pass across some general technical and product sense. If you prepare a clean 2-minute summary of a technical program you owned, this difference in format won’t be a problem for you.

Expect basic questions like:

• Tell me about yourself. What’s your day-to-day like?
• Is there something specific at Meta you’re excited about working on?
• Are you currently interviewing elsewhere?

We recommend that you try and deflect any comp questions because your level will be decided at the end of the interview loop by the hiring committee and comp will be decided accordingly.

Meta recruiters have a ton of internal data and context that can help you a great deal. Take the time to connect with them on this call by being upfront about your background and what you want out of your career. They’re known to advocate for a candidate later in the process so they're good people to have on your side. 

This is a 45 minute conversational interview with the current TPM, with a few minutes reserved at the end for your questions. 

Officially, the screen assesses:

• program management, 
• cross-functional leadership, 
• technical ability and 
• ability to communicate clearly.

Colloquially, it’s said to be a pocket-sized version of the full loop, where it samples all the focus areas of the onsite in one sitting. The questions will mostly be anchored to your resume, but since they're touching upon so many topics, interviewers do tend to cut in between if the answer starts to wander.

What’ll be evaluated in this round are:

• Delivery of the program you ran 
• Subject matter expertise
• Technical knowledge 
• Resume depth
• Succinct answers
• Honesty about gaps 
• Motivation for Meta
• Quality of your questions at the end

Expect questions that ask about

• Your most challenging program
• If you ever took the lead and drove the team toward a successful/unsuccessful outcome
• A program you delivered with very few resources

Since this round is a gatekeeper to the onsite, there’s some advice our coaches would like to give to you: 

1. Ask the interviewer how much detail they want you to go into and deliver on it. 
2. If you don't know the answer to something, don't hem and haw, or worse, try and divert. Meta says they value honesty, so it’s OK to plainly admit that you don’t know. 

The official Meta PDF is rather lean, but spends an entire paragraph stating that whatever version of the job you may have had elsewhere doesn't matter here. A Meta TPM is not positioned as a crisis manager or a facilitator between teams. To quote, “it's a more technical role at Meta than it is at other companies”.

However, no round in the TPM loop involves writing code. The AI enabled coding interview that you've probably heard about is for software engineering loops alone. More on it in our Meta SWE guide.

If you want to hear from a peer what the interview feels like, this entry on Glassdoor should do the trick.

And if you want to literally “hear” about the interview, we have a deep-dive video too.

1. Technical Retrospective

This round is conducted by an engineer that’s interested in knowing how you bring over the technical knowledge from past programs into Meta. 

Meta also tells you which stories to prepare, which is an unusually generous thing for a company to publish about its own interviews. You’ll have to pick a project or program from the last few years that has enough complexity and where you held a technical role in the design and can speak to the ins and outs of the system. Sometimes, the interviewer will make that choice for you going off your resume.

What the round tests is your ability to hold a technical discussion with an engineer at their level of detail. As expected of engineers, their concerns will be technical dependencies, trade-offs, resource planning, how you mitigated risk, and your specific contribution to the decision-making at large.

Sitting in the interview, candidates have said that the follow-ups went several layers deeper than they expected into outages, latency, infrastructure gaps, and end-to-end debugging. You should also be ready to draw the full end-to-end system on a whiteboard or on Excalidraw (or equivalent) while you narrate it.

For this round, interviewers will score 3 areas: 

1. End-to-end technical understanding
2. Components deep dive 
3. Troubleshooting Technical Problem 

The approximate minute-by-minute breakdown of this round comes down to:

• 5 min: context of the problem and what it was supposed to solve
• 2 min: architecture summary (best presented rehearsed)
• 25 min: deep probing on the solution
• 5 min: troubleshooting 

With the project as context, candidates have been asked:

• What was your specific contribution to this project?
• Are you well versed with the failure scenarios? Do you know how they were handled?
• Knowing what you know now, would you do anything differently in the project?

We suggest that you prepare for this round after solution design. That round forces your hand into a fixed order of describing any system. Once you’ve internalised it, you can use it to walk through your own project.

Also, sift through chats and reread the technical documentation for the project you plan to present. The milestones and decisions will come by easily, but the details live in the docs.

Go back and chat with the engineers who worked with you. No one better to tell you how the version that you've shipped works. 

Discuss each trade-off at the moment it comes up in your explanation. Buy v/s build, SQL v/s NoSQL, whatever it may be, address it on the go so it doesn’t come off as “lack of depth” if you happen to gloss over them in the summary at the end. 

2. Solution Design

The interviewer, who is a TPM in this round, will hand you an ambiguous problem, and will try to understand your thought process and structure in solving it. What matters here is that you break down and devise product and technical strategy for a hypothetical problem that's super complex.

What adds to the complexity of this round are two things: 

• the problem sits outside your domain on purpose
• interviewers will interject and change the requirements halfway to see how well you adapt. 

In the sweeping stride of this round, you should expect to discuss product solutions, architecture, data flow, technical tradeoffs, and metrics. 

Officially, there are 3 focus areas that are assessed. Our coaches have lent us their time to expand and tell you exactly what you should do to score well for each.

1. Product Clarity

• Clarify and agree scope with the interviewer
• User reqs / use cases, written on the Excalidraw
• Why are we building this
• Who uses it, who's the core audience
• How they use it, which features to focus on
• Follow-ups and assumptions: which markets, launch volume
• Reqs: functional (what we're building, what's in the MVP) and non-functional (latency, privacy, security, consistency vs availability)
• Metrics / KPIs defined, design tied to those goals
• User flows for the core experience

2. Technical Design

• Constraints
  - Traffic and data handling constraints at scale
  - Scale: RPS, request types, data written per sec, data read per sec
  - Special reqs: multi-threading, read or write oriented
• High level architecture (abstract design). Sketch the important components and the connections between them, no details yet
  - App service layer, which serves the requests
  - List the services required, define each one and what it does
  - Data storage layer: how the schema looks
• Detailed design through user flows: which services, when they're used, what data is stored where, how the interfaces work
  - Each service and what it does
  - Data models, DB types
  - Interfaces and APIs
• Optimizations, scale, resiliency: how you scale and optimize this
  - Gateways (auth, load balancing)
  - Data partitioning
  - Cache and cache policy
  - Backups and replicas
  - Microservices (scaling)
  - Market expansion
  - Latency

3. Metrics and Trade-offs 

• Success criteria and the associated metrics / KPIs
• System deps articulated with adequate depth
• Failure scenarios and mitigation plans
• Technical tradeoffs in the design, and how you'll hit all your goals

If you’re targeting infrastructure-heavy scopes, cross-reference your solution/system design prep with our Amazon and Stripe TPM Guide.

The prompts can ask you to design a service of any kind

• Chat app like WhatsApp
• Feed, like Instagram/Facebook
• Video app like Youtube 
• Shopping app like Amazon 

About half the list of practice prompts in the official PDF are Meta’s own product lines so that’s a hint on how much familiarity is assumed.  

3. Program Sense

This round discusses the lifecycle of a program with a laser focus on the details of every phase and is conducted by a TPM.

The phases typically are: kickoff -> problem definition -> XFN buy-in -> goals / KPIs -> prioritization -> risk and mitigation -> execution -> lessons learned.

The round tries to gauge how you execute and own large cross-company programs, especially how you manage relationships with XFN partners without muddling impact or deliverability.

There are 7 focus areas to this round: 

• Program Complexity: Pick a program that lets you show off your range, preferably spanning multiple teams and dependencies. 
• Program Strategy: Address the milestones you set and how you sequenced them. Don’t forget to mention what you deliberately left out of scope and why.
• Prioritization: Explain how you sorted out the hierarchy of priorities and the business value was behind each of those calls.
• Program Execution: This is not purely about monitoring. Bring up instances of re-planning or how you stepped in to unblock teams.
• Risk Mitigation: A risk you named at kickoff with a mitigation plan scores better than a risk you escalated in the week it went live.
• Level of ambiguity: This is a level differentiator. The lesser the clarity at start, the greater pull you have in seniority. If you're gunning for the staff level, the expectation is that you took advantage of the ambiguity. For example, you used it to find an opportunity nobody else was driving, or you stepped in to address it without being asked to.
• Communication: This is about tiered comms. Talk about how you manage the exec update, the XFN update and the eng channel for the same program.

This round is typically where you’re asked questions like:

• Tell me about the time you took a strategic risk.
• Have you ever pushed back against an Eng Lead? How did that resolve?
• Tell me about a time you couldn't meet a deadline. How did you talk about this with your team and stakeholders? Did you learn anything from this?

If you go into a theoretical tangent to any of the questions they ask, the interviewer will redirect you pretty bluntly to provide a concrete answer.

To have an anecdote for every opening question or follow up, we suggest that you make a story bank. Take the classic STAR framework and build it out into STAR+ (Situation, Task, Action, Result + the X-Factor: Learning) to structure your stories. The X-Factor at the end - Learning - is your definitive chance to demonstrate intellectual humility, and helps you reflect on a personal takeaway on how that situation changed you for the better. 

4. Partnership

This round again is behavioral in nature and is conducted by someone in the XFN group that you might end up working with. 

The round exists to assess how well you leverage relationships across the org to get to where you want to be, delivery/goal wise. 

There are 3 focus areas to this round:

1. Collaboration with partners: While this is mostly about building cross-team relationships, it's also about the accountability that comes with it. Interviewers want to see if you can hold a partner to a commitment (esp when they don’t report to you) without damaging or ending that working relationship.
2. Effective communication: This is tiered comms, that we just touched upon in the previous round.

1. Influencing without Authority: This is about how you can align people on a shared goal without reaching for your status, formal authority, and more importantly, locality. The first two are obvious, but locality here means ruling out proximity as a tool. This means NO stories of walking over to someone's desk or catching the right person at coffee. 

The third point is a hefty idea, more so because the level calibration sits inside of it.

• For senior roles, candidates typically tend to communicate with Director+ levels on their program.
• For staff roles, Meta looks for "more of an ability to have two-way comms on programs, being able to pushback, not just take leader’s feedback and run with it, but understand context they are missing and provide that feedback."

Our coaches warn that the partnership round can be misunderstood because it looks like a soft conversation, but scores some very specific culture related things.

You'll understand better when you look at the line of questioning:

• Has the team lead from another craft resisted or opposed your goals? Did you finally convince them?
• How do you tailor an update for Director+ vs your eng partners, especially when scope or goals have moved?
• Tell me about a program that cast a wide XFN net. How many partners were there? Did it get difficult?

Anupama Mayooranathan from Meta reportedly jumped through a bunch of legal hoops to contribute to the Meta TPM insider’s guide which is worth the read, especially to understand how ownership for TPMs is demarcated in teams where PMs are also present.  

5. Behavioral

Conducted by a TPM, the interview will focus on what you're passionate about in tech and what kind of impact you want to make. More specifically, this is a test to see if you would thrive in Meta’s environment where the entropy is off the charts. 

The volume of questions in this round can be pretty high. Some candidates say they felt a little overstimulated and it wasn't anywhere close to a relaxed chat.

There are 5 signals that Meta looks for:

1. Resolving conflict: Going past the obvious disagreement bit, this is a signal where Meta wants to see if you can empathize with people whose views are radically different from yours. If in your retelling of the incident, the other person has been painted as “all wrong”, it definitely doesn't demonstrate that.
2. Growing continuously: If you accept feedback gracefully and file it away, that's a weak signal. The “growth” here is personal growth, and you need to have evidence of seeking and acting on feedback from colleagues. 
3. Embracing ambiguity: This can be simmered down to one question. Can you decide and stay productive with information missing?
4. Driving results: This is measured in how you go after impact, without needing someone to micromanage/motivate you. You’ll benefit greatly if your story has some metrics to back it up.
5. Communicating effectively: This is the one signal the interviewer doesn't have to take on trust. You'll be communicating with them for 45 minutes anyway.

Recently reported behavioral questions:

• What's the accomplishment you're proudest of so far in your career?
• Tell me about working with someone whose style was very different from yours.
• Tell me about a time you used data to clarify something when everybody else was working off instincts.
• Give me an example of you prioritizing ruthlessly.

Generally speaking, you have to review Meta's mission statement and core values first. It'll give you some context into how they operate and inspire the right stories for your story bank.

At the end of each round, interviewers get 24 hours to submit their notes and pick between Strong Hire, Hire, Leaning No Hire, or No Hire for you. 

The Hiring Committee, consisting of senior TPMs then reviews that feedback to make the final call and decide your level. 

If the committee signs off on a “yes”, you’ll then move into the Team Matching phase where you'll do 30-minute informal chats with HMs until you zero in on a fit.

IC3: $158K

IC4: $216K

IC5: $341K

IC6: $415K

View the latest compensation for Meta TPMs on Levels.fyi