Why Google? How to Answer "Why Do You Want to Work Here?"

How to answer "why Google" in about a minute: a three-part structure built on what Google says it assesses, plus a weak and a strong answer compared.

A good answer to "why Google" names one specific thing about the team, product or problem you would work on, ties it to something you have already done, and ends with what you would bring to this particular role. Keep it to about a minute. Leave out the perks, the brand and a recital of the mission statement: every candidate can say those. Google says it assesses every candidate for a role against the same rubrics, so an answer tied to the role gives the interviewer more to work with than general enthusiasm. This guide covers what Google says it looks for, where the question fits in the process, a three-part structure, and a weak and a strong answer taken apart line by line.

Those who also face "Why Meta?" or "Why Microsoft?" can use our guide to how big tech interviews differ to prepare for several companies at once.

To see where this question usually comes up, from the recruiter call to the interview panel, read our walk-through of the Google interview process.

What Google says it is looking for

Google publishes two pages that matter here: its hiring process overview and its interview tips. Read together, they describe the interviewer's side of the table fairly plainly:

Structured rubrics. Every candidate for a role is assessed with the same clear rubrics, and the questions are open-ended and role-related. Google says it wants to learn how you think, how you work with a team and what your strengths are. There are no brainteasers.
Connections between the job listing and your resume. The first tip on the interview page is to cross-reference the two and build a library of examples where they overlap.
Evidence with numbers. Google suggests framing achievements as what you accomplished, how it was measured, and how you did it.
Research shows in your questions. Google describes interviewing as a two-way street and says prepared questions show you understand Google and the position.
New perspectives. The tips close their preparation advice by saying there is no one kind of Googler and that Google looks for people who bring new role-related perspectives and experiences.

On cover letters, which Google does not require, its advice reads like a one-line brief for this exact question: "Draw a direct line between your passion and our position."

What this means for your answer. "Why do you want to work here?" is a small version of the whole interview. It shows whether you researched the role, whether you can link your experience to the job listing, and whether you can back a claim with something measurable. An answer about Google in general fails all three tests, however sincere it is. An answer about this role, connected to work you have done, passes all three in under a minute.

Where the question fits in Google's process

Google says the process usually takes roughly 6 to 8 weeks, varies by role and team, and may include these steps:

Assessments. Some candidates take the Google Hiring Assessment, which Google says measures workstyle skills, and some roles add a coding exercise or another role-related test. Our Google Hiring Assessment guide covers that step.
Recruiter conversations. One or two shorter phone or video calls. Google says the recruiter usually assesses key skills for the role, shares information about the team, asks about preferences such as location, and gives you time to ask questions.
Project work, for some roles: a case study, or writing or code samples.
Interviews. A panel of interviews over video or in person. For technical roles, see our notes on Google coding interview questions.

Google's hiring and interview-tips pages do not list the questions it asks, so we cannot say at which step "why Google" will come up. The recruiter calls are the natural place for it, because that is where the conversation turns to the team and to what you want. Prepare two versions: a 60-second answer about the role for the recruiter, and a sharper one for the panel, once you know more about the team.

One process detail changes how you should think about the answer. Google lets you apply for up to three jobs every 30 days and asks you to read job descriptions closely. If you cannot say why you want this particular role rather than any job at Google, take that as a sign to pick a different listing before you apply.

A three-part answer

1. The specific pull

Name one thing about the role that drew you: a problem the team works on, a product you use and have opinions about, or a skill the listing asks for that you want to go deeper in. "Innovation", "impact" and "great culture" do not count, because they describe every large tech company's careers page.

Where to find something specific:

The job listing itself. The responsibilities section usually names the problem the team owns. This is the most reliable source and the one the interviewer knows best.
Google's team pages and blog. The hiring page points candidates to Google's company and team sites, its locations and its blog. The blog is organized by topic, including product areas, so you can read recent posts about the product your team touches.
The mission, used carefully. Google's stated mission is to organize the world's information and make it universally accessible and useful. Quote it only if you can attach a concrete example from your own work. Recited on its own, it says nothing about you.

2. The bridge

Connect the pull to one thing you have done. Use Google's own framing: what you accomplished, how it was measured, how you did it. One example is enough. Two starts to sound like a resume read aloud.

3. The contribution

Close with what you would do in the role, or what you want to learn there that you cannot learn where you are. Saying what is missing in your current job is fine and often more convincing than pure praise, as long as you frame it as what you are moving toward, not away from. Then, if the conversation allows, hand it back with a question about the team. The interview tips present prepared questions as evidence of research, and our questions-to-ask generator can help you draft a few.

A weak answer and a strong one, compared

Both answers below are illustrative. The role is a hypothetical product analyst position whose listing says the team measures how people adopt new collaboration features. The candidate and the numbers are invented to show the structure.

Weak answer:

"Google is one of the most innovative companies in the world, and I've always admired its mission to organize the world's information. I love the culture, and I'd be excited to work alongside such talented people. It's honestly my dream company."

Why it fails:

Every sentence could come from any candidate applying to any Google role. Nothing in it is about the job.
The mission appears but is never connected to anything the candidate has done.
"Culture" and "talented people" are things Google provides, not things the candidate brings.
"Dream company" tells the interviewer about the brand, not about fit. Google says it assesses candidates against role-related rubrics, so an answer this general gives the interviewer very little role-specific to go on.

Strong answer:

"The listing says this team measures how people adopt new collaboration features, and that is the problem I've worked on for the last two years. At my current company I rebuilt our onboarding reporting, cut the dashboard from fourteen metrics to the four that predicted retention, and the product team used it to lift week-one activation from 31% to 38%. What I don't have yet is scale. Our product has about 200,000 users, and I want to do this work where a one-point change in adoption affects far more people. I'd also like to understand how the team decides which features get measured first."

Why it works:

First sentence: a specific pull, taken from the listing, which shows the candidate read it.
Second sentence: the bridge, with an accomplishment, a measure and a method, which is the framing Google suggests.
"What I don't have yet is scale": an honest reason that only a company of Google's size answers, which is far more believable than praise.
The closing question: it turns the answer into a conversation and shows interest in how the team works.
Length: about 100 words, which fits comfortably under a minute when spoken.

Expect a follow-up. Google says interviewers ask follow-up questions to understand your thinking, so anything you mention, such as the four metrics, is something you should be ready to explain in more depth.

Mistakes that sink the answer

Leading with perks. Perks are things Google provides, not things you bring, and many employers offer them. Leading with them suggests you are shopping for benefits.
Prestige as the reason. "It's Google" answers why anyone would apply, not why you fit this role.
Product claims you cannot defend. If you praise a feature, be ready for "what would you change about it?"
Running long. Google's tips point out that interview time is limited and recommend concise examples. Past about 90 seconds, you are spending time the interviewer wanted for other questions.
A script recited word for word. Know your three parts and your one example; let the wording vary. Google says it wants your own thinking and does not allow Google Search or AI tools during interviews, so the answer has to be something you can say naturally.

Adjusting the answer to your situation

Students and new graduates. Use a class project, internship or side project as the bridge. The structure is the same; the evidence is smaller in scale, and that is fine.
Reapplying. Google notes that most Googlers applied for other roles before they made it to interviews, and that not getting a role is often about timing. If this is your second or third application, say what you have done since the last one. It answers "why Google" and "why now" together.
Non-engineering roles. Google says the same basics apply to engineering, marketing, internships and leadership roles. Swap the technical example for a campaign, a deal, a process you fixed or a team you led.

Practice it out loud

Write the three parts as bullet points, not a paragraph. Say the answer out loud, time it, and cut until it fits in a minute. Then practice the follow-ups: why this team, why now, what you would change about the product. If you want structured reps before the recruiter call, you can rehearse with a friend or run a session in Verve AI's mock interview. For the behavioral questions that usually come next, our list of common STAR interview questions is a good place to build your example library.

Sources

Process length (roughly 6 to 8 weeks), assessments, recruiter conversations, project work, panel interviews, structured rubrics, open-ended questions, no brainteasers, three applications per 30 days, reapplication note, cover-letter advice, AI tools not permitted, same basics across role types: https://www.google.com/about/careers/applications/how-we-hire/
Cross-referencing the listing and resume, past experience questions, the accomplished/measured/doing framing, follow-up questions, limited interview time, prepared questions as evidence of research, no one kind of Googler, Google Search and AI not permitted during interviews: https://www.google.com/about/careers/applications/interview-tips/
Google's mission statement: https://about.google/company-info/
Google's official blog, organized by topic and product area: https://blog.google/