Google UX Researcher Interview Guide

Google’s UXR loop tests a single question above almost everything else: do you have the ability to use your research skills to influence product and business decisions? 

TL;DR the interview loop for a Google UXR looks like this:

Step 1: GHA

Step 2: Recruiter screen

Step 3: Virtual interview

Step 4: Onsite - Presentation

Step 5: Onsite - Four 1:1 interviews

Step 6: Team matching and hiring committee

Sara Cambridge, UXR at Google, wrote in the official Google interview guide that every interviewer at Google asked her a version of this question:  “What was the impact of your research?”. We recommend you prepare for every part of the interview to show the impact and decisions your research reached.

Quick note: UX Researcher and Quant UX Researcher are distinct roles at Google with entirely distinct responsibilities. 

Quant UXR loops have a deeper focus on statistics and also have a coding component. Prepfully is the only platform which has both Quant UXRs from Google, as well as Qual UXRs from Google for mock interviews and interview coaching.

Before your first conversation with a researcher, there are two filter screens.

The GHA is the first and will take roughly 30 to 60 minutes online. You might get anywhere from 30 to 100 questions based on different situations. The count and specifics will change depending on the exact role. Many questions are based on self-rated Likert-style questions about how you work. But overall formats tend to vary quite a lot. 

You might even be asked questions that have been added to filter candidates using bots/not reading carefully. For example, this one candidate on Blind was asked to agree or disagree on “I am fluent in over fifty languages.”

Please note: Failing the GHA might make you ineligible to apply for other Google roles for 6 months. 

For the GHA, you will be asked questions around:

• Ethical situations involving integrity, organization, quality of work, and collaboration.
• How you communicate and manage conflicts at work.
• Some tips from us: Picking more ‘strongly agree’ or ‘strongly disagree’ options seems to score better, and the GHA is not simply a pass-or-fail test. It’s possible you pass the GHA overall but not for the role you applied for, in that case your existing score might be used for other Google applications. 
• Consistency is also super important, and keep in mind you can’t go back to change earlier answers once you’ve moved on. This Reddit commenter broke down what inconsistent answers could look like.

You’ll be given an FAQ along with the GHA, we recommend you read it carefully to not miss any instructions. Also some advice that might seem obvious but read every question twice as there might be some subtle wordplay involved with some.

If you can, write down the answers and review them while answering to help you stay consistent.

Next up is the recruiter screen where they’ll cover your background and logistics. Google recruiters can flag candidates whose communication is unclear or if the reason for wanting the role is generic.

Some questions Google recruiters might ask:

• Walk me through your background.
• Why Google? Why this role specifically?
• The “why Google, why this role” doubles as a research-depth check, so we suggest you treat your answer as a sample of your desk research. Spend some time studying the different products you could support. If you know what part of the org you’re interviewing for beforehand, look at who uses it and what the open research questions are. Let that homework show in your answer.

This round is an hour-long interview with an internal UXR. They’ll cover your research background, your projects, your process, and how you work with stakeholders. 

Some questions Google might ask UXR candidates: 

• Can you tell me a time you had a super tight budget for a study and made it work?
• Walk me through a research plan to understand [X].
• Walk me through your research process on a recent project.
• How do you usually share and communicate your findings with different stakeholders?

You likely won’t need to prepare a presentation at this stage, although we suggest writing up a short summary of your UX experience to anchor the conversation around the highlights you want your interviewer to walk away with. Some candidates have been asked to solve a short research challenge inside the hour, and the round can chain into a “hiring-manager conversation” set of questions if it goes well.

Now, at this stage, it’s likely neither you nor the UXR interviewer will know your target team, so we recommend keeping your answers focused on the process. Their job is deciding whether to bring you onsite based on your experience and skillset.

Additionally - sometimes, you’ll face another virtual or phone round simply because the first interviewer couldn’t reach a recommendation, so don’t read it as a rejection signal.

To prepare for this round, go through your major projects and outline core talking points for each. You should basically list out what you want your interviewer to take away, for each project you talk through. It might be a particularly creative application of your craft; it might be the way you set up the strategy; it might be how you managed a particularly convoluted set of stakeholders. You know your work well, the goal is to ensure your interviewers understand why it makes you a fit for Google.

If you’re also interviewing at Meta or comparing loops, this screen differs between the two companies, you can check out our Meta UX Researcher interview guide for how Meta does their interview loop.

You’ll spend 45 to 60 minutes presenting your work to a panel. The panel can be made up of researchers, mixed UX disciplines, or UX plus a PM or engineer. Some people may not be UX people at all. The business half of that story is what the PM or engineer on your panel is there to assess.

You can also ask your recruiter for a detailed brief and the names of the panel. Google recruiters are usually super helpful and typically share this info.

Some follow-up questions Google interviewers ask during the UXR presentation:

• What alternative methodologies could you have used for this project? Why didn’t you go with [XYZ] research method here? 
• How did you ensure inclusiveness and diversity within your participant pool?
• What were the specific sampling biases in your recruitment for this project, and if your recruiting budget was cut by 50%, how would you have sourced a comparable demographic?
• If you had a lot more time (or resources), what would you have done differently?

Google is mainly looking at your problem-solving approach rather than the specifics of the product you worked on. What we mean by this is: while the user problem is important, and so is the way in which the product is solving for it, don’t make the mistake of focusing primarily on this (we’ve seen some candidates spend overly long in setting up the context around these topics). The way in which you used research to unblock the problem; or identify the best solution, is the part your interviewers actually want to dig into.

Therefore, for this round, focus on the more practical and concrete issues as you walk through your deck. If there were any issues, or problems that cropped up during your research, also discuss how you solved them. No research project is truly free of hiccups; and talking proactively around unexpected hiccups, or even bad decisions you learnt from or pivoted away from, shows that you are prepared for such scenarios in the future.

This Reddit commenter recommends making sure you share things that are in line with Google’s UX philosophy. 

After your presentation, you’ll have four interviews of 45 to 60 minutes each. Some candidates have reported loops running up to six. You might also have an off-the-record lunch with a UXR which will be more of a friendly chat than an interview.

The interviews will be split between technical conversations (about research design) and behavioral conversations (about how you work). 

The topics covered will be distinct ones such as your soft skills, research and methodology know-how, business cases, research process, decision-making and prioritization process, and how you deal with limited resources or timelines.

Interviewers will also look at Googleyness. It starts with Google’s motto: Do the right thing (formerly ‘Don't be evil’). Google wants to know if you’re someone who fits that.

Quick tips from us: Whenever you feel your answer requires a longer framework, you can ask for a 10-second pause to think; write the structure down, and scratch off items to make sure you hit every major talking point. 

And along the way, check in with some small questions to make sure your answer is going along the right tracks, and is aligned with what the interviewer wants like “does that answer what you were getting at?”

Google interviewers are constantly typing during interviews to note down your answers so we suggest you keep your delivery as simple as you can. Since the hiring committee will be reading down this packet at the end of the process, keeping the delivery simple makes sure everything gets recorded as is, and your answers are also easy to understand for someone who’s going to be reading them without you there.

For the technical portion, the questions will focus on common tasks you might be given, sometimes with a small twist. So the questions themselves could be vague. The interviewers are scoring if you handle the task the way a Google researcher would.

You will also be asked how you use AI and interviewers will expect you to break down what parts you delegate and how you verify outputs before using them. 

Google UXR candidates have been asked these types of questions: 

• So [this event] happened, diagnose why.
• Which of these two designs do you think is better?
• Can you explain this method and its tradeoffs?
• We're launching an AI feature like AI Mode in Search. How would you evaluate user trust?
• How are you using AI in your research practice to increase quality or speed?
• Google wants to build a grocery store, design a research plan to help us decide what type of store.
• Sales are down (or traffic is up). How do you figure out what’s going on?
• Can you come up with some engagement metric for a job website?
• Can you explain diary studies, and when would you run one over longitudinal interviews? Are there any things they miss? 
• For an experiment we’re using eye tracking, but one of the participants is cross-eyed and the tech isn’t calibrating right. What do you do?
• How do you design research protocols for the exploratory stage and the validation stage?
• We want to launch an educational portal for K-12 teachers on ChromeOS. How would you figure out user needs and viability?
• So we have [X problem], can you apply this [specific design framework] to solve it?
• One of our teams has come up with a sensor that can measure a person’s breath; how would you integrate and use this technology for Fitbit?

A very common format is “plan a research study for X”. You’ll have 10 to 15 minutes for questions like these, so slow down and take your time on them. The interviewers are looking at your research process, so narrate the major steps you’ll be going through before as well as during. 

You can approach it in many ways, one way would be you start by restating the prompt in terms of a research problem and you then scope out. So think through questions like: Why are we even doing this? What’s the timeline and budget? What already exists? What would be the ideal outcome? 

Interviewers make these questions a little ambiguous on purpose to see how you scope and gather requirements. If the interviewer answers vaguely throughout this process, commit to a reading and state it out loud.

Next, discuss what you’re optimizing and the possible business impact and KPIs your research could move. Also discuss any possible constraints you can think of even if the interviewer doesn’t bring up any.

Then once you’ve defined the problem you walk through the foundational research, and validate your methods. Bring up 2-3 research objectives, choose your methods, talk about the people you’ll need for this, and discuss some sample tasks they’d have to do. Then you bring up the outputs and analysis.

Finally, you close with a realistic timeline and what success looks like.

For metric design questions, you can use Google’s HEART framework for UXR while answering which connects goals to signals to metrics.

Define what engagement means for this specific product, pick the behavioral signals that provide evidence for it, then get the metrics from those signals, and also name one guardrail that must not get worse. 

Google interviewers are looking at specific Googleyness attributes like how you challenge the status quo. They want to understand your judgment and mental frameworks to see how you solve broad categories of problems.

Now, this round can be quite subjective. It’s possible two interviewers can hear the same story and take different things from it, which is one more reason the hiring-committee structure exists. 

Some questions Google interviewers have asked:

• Can you tell me about someone who inspires you?
• A senior stakeholder wants a feature redesigned, but you disagree and think it’d make the UX worse. How do you approach it?
• Who is a leader who inspires you, and why?
• When there is conflict between stakeholders and the product direction, how do you make sure research doesn’t get sidelined in the way?
• Tell me about a time your research ideas or findings were rejected.

For your answers stick to a structure, make the stakes clear, discuss your decision, then the outcome, and finally what you reflected on.

After the interview loop, you’ll go through a team matching exercise. This can function as a separate interview round itself. Do note: sometimes team matching can happen before the interview loop as well although this is rarer.

Also, a word of caution from other candidates' experiences: Treat what the recruiter describes as a starting expectation. Some candidates have reported the team matching round deviated from what they were told.

Now, your interviewers write their feedback, and at the end, a hiring committee of senior Googlers makes the decision. The committee only meets the version of you your interviewers wrote down. 

The ‘written packet’ contains your resume, a score and detailed written feedback from each interviewer, questions you were asked and your responses, often your deck as well, recruiter notes, and any internal references if applicable. If you’ve already gone through team matching, it could include a letter of support from the hiring manager as well.

Sometimes, the hiring committee won’t meet until this team matching exercise is over. Some of our coaches have recommended asking the recruiter if they are willing to send you to the committee without a match.

If you hold a competing offer, tell your recruiter, because the recruiters can then use competing offers to pressure hiring managers.

Base range for Google UX Researchers in the US starts from $137K (total $171K) at L3 to $252K at L7 (total $710K) according to data from Levels.fyi.

Google has various different vesting schedules. The most common is a four year division with 38% in year 1, 32% in year 2, 20% in year 3, 10% in year 4.