Google HR interview questions and answers

12 Google HR interview questions with sample answers: why HR asks each one and how to answer. From public candidate reports. Free.

At Google, the HR or recruiter conversation usually happens at two points: a short screening call before your phone screen, and later discussions around scheduling, compensation, and offer. The recruiter is your main point of contact through the whole loop, and candidates report long gaps and unclear timelines between rounds. There is no separate formal HR round like service companies run; the non-technical part is spread across the recruiter calls and the Googlyness round.

What the Google HR round checks:

The first question is always some version of "tell me about yourself". Write your self introduction for the interview (free, no signup).

Google HR interview questions with answers

7 of these 12 questions appear in public Google interview reports; the rest are standard HR questions the company is known to ask.

1. Can you walk me through your current role and why you are looking to move? (reported)

Why they ask: The recruiter wants a short, honest picture of your background and whether your reasons line up with the level you applied for.

How to answer: Keep it to your current work, one clear reason for moving, and why Google specifically. Do not badmouth your current employer. Mention your years of experience so the recruiter can map you to L3 or L4.

Sample answer: I have been at [current company] for about [X years], working mostly on backend services in [tech stack]. I own a couple of services end to end, from design to on-call. I am looking to move because the scale of problems here is limited and I want to work on systems that serve users at a much larger scale. Google is the obvious place for that, and the kind of work your team does on [area] is exactly what I want to grow into.

2. What is your current CTC and what are your expectations? (reported)

Why they ask: The recruiter is checking whether your number fits the band for the level before spending weeks on interviews.

How to answer: Give your current fixed plus variable split clearly, then give a range rather than one number. If you are unsure, say you are open to a fair offer based on the level. Do not inflate numbers you cannot back with payslips.

Sample answer: My current fixed is [amount] and variable is around [amount], so roughly [total] per year. I do not have a hard number in mind. I am more focused on the level and the work. That said, based on what I have seen for this level, I would expect something in the range of [range], and I am open to discussing it once we get to the offer stage.

3. How soon can you join if you get an offer? (reported)

Why they ask: Google plans team matching and start dates around your notice period, so they need a realistic date.

How to answer: State your notice period exactly as per your contract, then add buffer for handover and any buyout possibility. Do not promise a date you cannot meet. If you have competing offers, mention the timeline without turning it into a threat.

Sample answer: My notice period is [X days] as per my contract. I can start within that, and if needed I can check with my manager about an early release, but I would not want to commit to something I cannot deliver. Realistically I can join by [month], and I will keep you updated if anything changes on my side.

4. Are you open to relocating to [city] or working from a different office? (reported)

Why they ask: Teams are tied to specific locations and the recruiter needs to know if you will actually take the role in that office.

How to answer: Be clear about which locations work for you and which do not. If you are flexible, say so plainly. If you have a constraint like family or a partner's job, state it now, not after the offer.

Sample answer: I am open to [city] and [other city]. I do not have a hard constraint on location. My only preference is [reason, like being closer to family], but if the team is in [city] I am fine relocating there. I would rather sort this out now than after the interviews.

5. Why do you want to work at Google? (reported)

Why they ask: They want a specific reason, not a generic one, to judge whether you will actually join if an offer comes.

How to answer: Pick one or two concrete things about Google that matter to you, like scale, a product you use, or a specific area of engineering. Avoid saying it is just a big brand. Connect it to something you have done.

Sample answer: Two reasons. One, the scale. I have worked on services handling [small number] requests a day, and I want to see what it takes to build for billions. Two, the engineering culture around code review and design docs. I have read some of the public material on how teams here write design docs and I want to work in that environment. It is not just the brand for me.

6. Tell me about a time you handled a difficult situation at work. (reported)

Why they ask: This is the Googlyness style question. They are checking how you behave with people, not just your coding.

How to answer: Pick one real incident with a clear situation, what you did, and what changed. Keep it short. Show that you listened to the other side and did not just push your own view.

Sample answer: We had a release where my change broke a downstream service. My first instinct was to defend the design, but I sat with the other team and we traced it together. The issue was a contract we had not documented. I wrote the missing contract doc, added a test, and we shipped a fix the same day. After that we started doing a quick cross-team review before any interface change. It cost me half a day but saved a lot of back and forth later.

7. Do you have any questions for me about the process? (reported)

Why they ask: The recruiter is checking if you are engaged and if you understand what is coming next.

How to answer: Ask about the timeline, the number of rounds, and what the team matching step looks like. These are the things candidates report being unclear about. Do not ask about salary again here.

Sample answer: Yes, two things. What does the timeline look like from here, and how long does team matching usually take after the onsite? I have heard it can stretch, so I just want to plan my notice period properly. Also, is there anything I should prepare differently for the Googlyness round compared to the coding rounds?

8. What are your strengths and weaknesses?

Why they ask: Standard HR question to see if you are self-aware and honest without oversharing.

How to answer: Give one real strength with a small example, and one weakness that is genuine but not a dealbreaker, plus what you are doing about it. Do not use the fake weakness like I work too hard.

Sample answer: My strength is that I am steady when things break. During a production incident last year I was the one coordinating the fix and keeping the team calm. My weakness is that I used to jump into code before writing down the approach, which cost me rework. I have started writing a short design note before starting anything non-trivial, and it has cut down the back and forth with reviewers.

9. Are you interviewing anywhere else right now?

Why they ask: The recruiter uses this to gauge urgency and to plan your loop faster if needed.

How to answer: Be honest but do not overshare. If you have other processes running, say so and give rough timelines. Do not bluff about offers you do not have.

Sample answer: I am in early stages with [one or two companies], nothing at offer stage yet. My main focus is Google because of the kind of work here. If it helps with scheduling, I can be flexible with interview dates, but I would appreciate knowing the timeline so I can plan the others.

10. Are you comfortable with the background verification and document checks?

Why they ask: Google runs a proper background check before joining, and they want to know early if there is anything that needs explaining.

How to answer: Confirm you can provide payslips, offer letters, and education documents. If there is a gap or a mismatch in dates, mention it now with a simple explanation. Hiding it only causes problems later.

Sample answer: Yes, I can provide everything. I have my offer letters, payslips, and degree certificates ready. There is a [X month] gap between [year] and [year] when I was preparing for exams, and I can explain that if needed. I would rather flag it now than have it come up during verification.

11. How do you handle feedback and criticism?

Why they ask: This is part of the Googlyness check. They want people who take feedback without getting defensive.

How to answer: Give a real example where feedback changed how you work. Show that you asked for it rather than just received it. Keep it specific.

Sample answer: Early on, my manager told me my code reviews were too blunt and it was affecting the team. I did not agree at first, but I started watching how I wrote comments and switched to asking questions instead of making statements. It made a real difference in how people responded. Now I actively ask for feedback after every big project instead of waiting for the review cycle.

12. What kind of team and work are you looking for?

Why they ask: This feeds into team matching, where the recruiter tries to place you with a team that fits.

How to answer: Name the kind of work you want, like backend, infra, or ML, and be open about adjacent areas. Do not say you are open to anything, that reads as having no direction.

Sample answer: I want to work on backend or infrastructure, ideally on something with real scale and latency constraints. I have done [specific work] and I enjoy that. I am open to adjacent areas like [area] if the team is strong. What I do not want is a purely maintenance role with no design work, because that is part of what I am trying to move away from.

What candidates report about the Google HR round

Recruiter is your single point of contact. Candidates report that all updates, scheduling, and feedback come through the recruiter, and responses can be slow or unclear for weeks.

No separate formal HR round. Unlike service companies, Google does not run a standalone HR interview. The non-technical check happens in recruiter calls and the Googlyness round.

Googlyness round. Reported as one of the onsite rounds, focused on collaboration, handling conflict, and how you work with people, not on coding.

Team matching after onsite. Candidates report a team matching step after clearing the onsite, where you talk to teams about interests and past work. It can take multiple rounds and stretch for weeks.

Feedback can change. One reported case had an interviewer change feedback from positive to negative, leading to an extra round. Treat every round as final and do not assume you are through until the offer is in hand.

Scheduling delays are common. Candidates report waiting a month or more between phone screen and onsite, with no clear reason given. This is commonly reported and not necessarily a bad sign.

How to prepare

Practise the Google HR round in a free 5-minute mock

Google technical rounds

Quick answers about the Google HR round

What is asked in the Google HR interview?

Candidates report questions such as: Can you walk me through your current role and why you are looking to move; What is your current CTC and what are your expectations; How soon can you join if you get an offer; Are you open to relocating to [city] or working from a different office. Each one is answered on this page.

How long is the Google HR round?

At Google, the HR or recruiter conversation usually happens at two points: a short screening call before your phone screen, and later discussions around scheduling, compensation, and offer. The recruiter is your main point of contact through the whole loop, and candidates report long gaps and unclear timelines between rounds. There is no separate formal HR round like service companies run; the non-technical part is spread across the recruiter calls and the Googlyness round.

Can I fail the Google HR round?

Yes. Candidates are rejected in the HR round for unclear answers on relocation, shifts or the package, for contradicting their resume, or for seeming uninterested in Google. Decide your honest answers before the call.

Are these questions official?

No. They come from public candidate reports and are unofficial. PortLume AI is not affiliated with Google.

Sources

Based on 14 public reports: YouTube (8), LeetCode Discuss (6), last updated Oct 2026.

Unofficial guide from public candidate reports. PortLume AI is not affiliated with Google. HR questions for other companies · all company interview guides.

Featured on FoundrList

PortLume AI

Loading…