Meta UX Researcher Interview Guide

This guide uses the internal Meta UXR interview docs compiled by their own researchers, which we have thanks to our coaches. 

Going by those official docs, the interview loop typically goes through these stages:

• Recruiter screen
• Initial interview
• Full Onsite loop: (we’re counting the presentation in it)
  Research Presentation 
  Collaboration
  Direction
  Skill 1
  Skill 2
• Hiring committee and team match

Meta hires UX Researchers into 3 tracks: Qualitative, Quantitative and Mixed Methods. The track you choose decides the scope of what the 2 Skill interviews will cover. The rest of the loop remains the same. 

Be sure to check out our guides for Meta Quantitative UX Researcher, Expedia UX Designer and Amazon UX Researcher for further preparation.

This is a 30 minute call with your recruiter about your

• background
• experience
• long-term goals
• why Meta

To confirm your track and also set the level at which the rest of your rounds will be evaluated against. For some roles, it’s possible that Meta replaces this call with a prescreen form that’s in your Career Profile. 

Lots of candidates have mentioned that the recruiter goes through your resume “line-by-line” and asks about specific skills that have been listed there, suggesting that this is where your track is confirmed. 

Expect questions along the lines of:

• Do you have any experience with sampling bias correction?
• How good are you with R or Python?

There are 3 super important things to do on this call to make sure your interviews go smoothly:

• Ask about the 2 Skills interviews and what they’ll cover
• Ask about the presentation and when those details will arrive. You’ll get 7-10 days from the day you receive the email to prepare for it so you’ll want to have that stretch of time available, especially if you’re still working/ prepping for other interviews.
• Establish a good rapport with your recruiter 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 interview with a Meta UXR usually over video that’s positioned as the gatekeeper for the onsite interviews. This is a conversation that focuses on the depth and breadth of your research skills and you’ll be expected to lead it. 

You’ll be asked to pick an app and then design research for a hypothetical problem. 

You’ll then walk through:

• how you'd propose research questions
• how you'd scope the research plan (methods selection)
• how you'd validate your choices

Once you’ve committed to a plan and it starts to take shape, the interviewer will shift constraints and ask how your plan would adapt if you had more time (or less). 

Expect questions like:

• Pick an app of your choice. Let’s say users are suddenly dropping off. They’re keeping their accounts but are no longer using the app. How would you research the basis for that churn?  
• Think of an app you like to use, other than Meta's. Assuming you have only 3 weeks, how would you design a study to find the biggest pain points and see if it’s responsible for lower engagement? 

A detailed account from a Quantitative candidate (in June 2025) even lists follow up questions after the initial plan to touch upon:

• integrating log data, survey data and qualitative data
• sampling and weighting
• what they’d do if the cause of churn is something they can't measure
• how they’d reach users who stopped using the app
• what the plan is if someone needs an answer in 2 days and there’s no time to run a survey

The stakes are pretty high for this round so we consulted with our coach network for 2 main tips

• Remember that the round exists to understand 4 main things
  depth and breadth of your research skills
  research process and rigor
  flexibility and creative thinking
  understanding of potential tradeoffs of the methods you have proposed

and prep accordingly 

- Read The 7 Habits of Highly Effective Researchers written by Steve Wengrovitz, the former Head of Research at Meta. He even ties it back beautifully to the “Move Fast” motto and how you can embody it (while knowing when to step back too). This is good fodder for any behavioral-esque questions you might face. 

If you clear screens, you move on to the onsite interviews that have the following rounds:

1. Research Presentation
2. Collaboration
3. Direction
4. Skill 1
5. Skill 2

As you might’ve noticed, there is no stand-alone behavioral round so you should expect these questions to come up in every round. You’ll know they’re behavioral questions when the interviewer touches upon themes like:

• difficult conversations you’ve had with stakeholders, like breaking bad news to them
• seeking/incorporating feedback from colleagues (your team/cross-functional teams)
• shifting priorities to deliver on positive outcomes for teams/projects that rely on you
• presenting ideas and detailing plans to make sure everyone’s on the same page, even non-technical stakeholders
• growing continuously as a professional, both as a team player and an individual seeking more complex projects

1. Research Presentation

This is a 45 minute video presentation of your own research to a panel of Meta's researchers. Typically, they’re the same people that’ll go on to run your 1:1 interviews later in the loop.

In this presentation, Meta asks for the “story” of a well-defined business problem, told through a data-driven narrative and visualization that adheres to a clear business impact. Your recruiter will formally send over instructions and details once your interview date is finalized and you’ll get 7-10 days to prepare. 

While the internal PDF says you’ll spend roughly 30 minutes on your presentation and do a Q&A the remaining 15, candidates say the panel will raise questions on the spot and don’t save them for the end. 

In this round, the interviewers are officially told to assess 5 areas:

• Communication and time management: this can sound plain but it’s super important to land your story in time despite the questions 
• Informative data visualization: How well your charts communicate what they're meant to without you having to intervene and explain?
• Relevance of content, specifically research and impact: If your project shows research that changed a product decision.
• Compelling storytelling: if the problem and the outcome hold together as one narrative.
• Ability to engage the audience: Not being thrown off when the panel interjects, or if you're able to handle the pace of the conversation.

In this round, to give it your all, you should:

• Show enough methodological detail that your command of the methods is clear. Meta asks for this directly, so keep the discussion guide, the screener, the sampling frame and the analysis decisions in the deck.
• Like with any panel, be ready to defend your method choices against the alternatives the panel suggests. That doesn’t mean you vehemently oppose their opinions. This isn’t a black-and-white approach so make sure you gracefully acknowledge the merit in their POV before you stand your ground. 
• Make sure you reach for a spine from research question to product decision. Meta’s research leadership postings describe the team to be more focused on impact over interesting quirks and patterns of user behavior. 

2. Collaboration

This is a 45-minute 1:1 interview that runs on behavioral questions to zoom into how you maintain working relationships and the skill set you’ve developed to collaborate seamlessly with your peers and cross-functional partners. 

Officially, the round covers 3 elements:

• Modeling inclusive behavior: how you actively seek and incorporate input of different people when you research or share findings
• Effectively communicating information across functions and making sure each stakeholder gets what’s relevant to them from the same finding
• Building relationships across a diverse group of people (crafts, seniorities, etc.) to align and accomplish shared goals (despite any friction that may be)

Expect questions like:

• Tell me about a time a working relationship was damaged. What did you do about it?
• What do you do to build inclusion on team projects?
• How do you keep your xfn partners (PMs, content designer, etc) accountable for all their deliverables when you’re working on a project?

For this round especially, you should prepare a story bank of 8-10 stories so you have an anecdote for every tangent of probing. You should definitely have examples of a successful collaboration/one where it missed the mark with details of everyone involved and the part you played.

We recommend that you 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. Meta’s internal docs ask interviewers to look for evidence of a growth/learning curve and no better way to deliver on that. 

3. Direction

Like the name on the tin says, this is a 45 minute interview where you’ll discuss how you’ve independently set and driven the direction of your work or your overall team’s strategy. 

Meta operates at a dizzying speed and relies on researchers to be strategic product partners. The objective for you is to show proof from your past roles that you don’t rely on authority for your responsibilities.

The main focus here is on your experience with the following 3 focus areas:

• Embracing ambiguity: showing resourcefulness and a bias for action even when the path/project is not defined clearly
• Building complex systems to solve long-term problems: research programs that keep informing decisions even after the original study has been completed 
• Ability to assess changing priorities and adapt

Prepfully candidates who recently appeared for this round have reported the following questions:

• Tell me about a time you said no to a low-impact research request
• Has a product team ever wanted to ship something against your explicit recommendation? How did you handle it?
• How do you make sure your insights shape sprints for engineers and don’t just sit in a slide deck?
• Imagine your product team asks you to research 5 different high-priority requests at once, but you only have the bandwidth for one. Walk me through your framework for deciding what to cut

4. Skill interviews (1 & 2)

These interviews, 45 minutes each, evaluate your ability to design rigorous research studies. You’ll be given a hypothetical, often ambiguous product scenario that's relevant to Meta. The interviewer will assess how you approach and breakdown that problem and draw from your experience being out in the field to

• define clear research objectives
• account for constraints (time, engineering bandwidth, business goals, etc.)
• and translate the insights you have into something actionable

Details of track variation:

A. Qualitative: 

• Assess your theoretical knowledge of qualitative research and will typically drill into interviewing, evaluative methods, your thought process behind research designs, how you decide the best method fit, how you execute and analyze, all of it. 
• The second is more of a retro that asks you to lay out all the details of a research project you drove end-to-end. This is a deeper focus on how you select methods, the quality of your execution and how you adapt to change or ambiguity and ultimately, articulate the impact of your work. 

B. Quantitative: 

• Focuses on survey design skills, especially how you craft and design your data collection and execution. 
• Focuses on your approach to analysis and reporting skills like data prep and cleaning

C. Mixed methods (a literal mix with more or less the same rigor as the above)

• Assess qualitative expertise
• Assesses quantitative expertise
  

The following questions are what our coaches ask in both mocks and real Meta UXR interviews:

• Describe a recent discovery research study you did that resulted in a large amount of data. How did you analyze the data, and how did you come up with insights and recommendations to improve the team?
• How do you deal with circumstances in which individuals are doubtful of the value of your research, for example, when they challenge your sample size?
• What is the difference, in your opinion, between research on healthcare items and research on ordinary consumer products?
• Based on user feedback, your project manager determines that the default cell size in Excel is too tiny. What method would you take to the conclusion and related requests?
• What was an amazing discovery or insight you gained from a recent project?
• How would you go about conducting a user trial focused on email? And how would you safeguard a user's data if they opted to utilize their own email address during the experiment?
• How do you tell whether your research was successful?

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 UXRs 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: $157K
• IC4: $203K
• IC5: $287K
• IC6: $398K
• IC7: $482K

View the latest compensation for Meta UXRs on Levels.fyi