Google Interview Experiences & Questions
101 real Google interviews shared by candidates: every round, the questions they were asked, how they answered, and whether they got the offer. Latest: Oct 2026.
What to expect at Google
Based on 101 real interviews
By role
The Google interview process
Most common round types: Behavioral (36), Coding (30), Technical (16), System Design (14), Analytical (13), Data Structures & Algorithms (12).
Real Google interview questions
- What are you most proud of in your career?
- Tell me about yourself.
- Find Leaves Of Binary Tree
- Increase the profit per user of a product of your choosing.
- We've experienced something similar to this on the team. What would you do in this case?
- How would you design a LinkedIn-like system that instantly shows whether a profile is a first-, second-, or third-level connection for a user at very large scale?
- What do you know about algorithms?
- How do we sample from an arbitrary distribution?
- What is the project you are most proud of?
- Tell me about a time when data failed you.
- 1 ML sys design - how would you go about doing NLP and bag of words and create a system of words to predict the next word etc..
- Let's build a schema for this product.
- Walk me through one product you've worked on end to end.
- How would you approach creating a product roadmap without prior knowledge of the product?
- Tell me about the most challenging project you've worked on.
- Review this code, identify the problems, fix it, and walk through test cases so it correctly finds the lowest missing integer from a stream of inputs.
- What would this product look like in five years?
- A production service started showing errors and timeouts after a deployment. How would you troubleshoot it?
- Design a system that synchronizes customer data with our internal system.
- Talk me through your work experience in the past year.
- Tell me about a complex project you worked on.
- Question: https://leetcode.com/discuss/interview-question/2064646/google-screening-interview-question-may-2022
- How would you build the Google Photos yearly recap feature?
- What happens when you type a URL into a browser?
- Design a system that collects logs and metrics from many source systems, processes them by dimensions like location, customer, and data type, and serves them to downstream consumers.
- If the data set is too large to fit in memory on one machine and you have multiple workers, how would you sort it?
- How do you calculate a t statistic or a z statistic?
- What did you enjoy most about your last role?
- Master data management technologies overview
- One LC round about Djikstra
- Find seasonality in this quarterly data set.
- How should we be thinking about differentiating ourselves relative to competitors?
- How would you measure success metrics for Facebook Fundraisers?
- Design a vending machine.
- A LC type question and a AI based codebase bug fix
- What is your definition of success?
- How would you improve LinkedIn Messaging?
- If you had all the geospatial data in the world and no privacy limitations, what would you build?
- Explain networking protocols like QUIC and why they matter.
- Design a high-level system for Gemini responding to a user query.
Showing 40 of 363 questions. Open any experience for every question and how the candidate answered.
All 101 Google interview experiences
“Typical Google screening round, I fumbled during the implementation using c++, hence got rejected. Make sure to write working code and go through test cases.”
“Just like any other normal SWE process. Online interviews were postponed a lot, took over 2 months to complete the interview process.”
“The questions were not too difficult, more so worry about asking clarifying questions and making sure your implementation is clear to the interviewer.”
“The overall interview process was really good. Both interviewers were experienced and made the rounds feel more like technical discussions than just solving a problem. In the first round, we…”
“Pretty standard process. Interviewers were friendly and seemed to enjoy the work culture. The interviews themselves weren't too difficult, mostly standard leetcode questions.”
“2 coding rounds, 1 googliness round, 1 AI/ML depth. THe AI/ML was mostly going over resume, recent projects and some ml system design”
“The process on start is very easy ( online assessment , phone screen) but coding is very difficult - LEETCODE MEDIUM”
“The process was smooth. First round was a mix of product solutioning and code evaluation. Recruiter screen was easy too , had to walk through the resume basically.”
“The interview was challenging and required me to think deeply about my product decisions and experiences. I enjoyed the level of detail and the directness of the conversation. I felt well prepared…”
“Overall, the interview process went well. The questions were clear and gave me an opportunity to explain my skills, experience, and interest in the position. I felt comfortable communicating with…”
“The interview was comparable to other interviews for product management and cross-functional roles, with a strong emphasis on relevant experience, analytical thinking, and communication. It provided…”
“Overall, the interview process was well structured and the communication from the recruiting team was helpful. I appreciated receiving preparation materials in advance and having clarity on what to…”
“I only gave one SQL interview for an analyst role in strategy and operations. I did not go past that round.”
“The process goes very quickly. At the beginning I introduce myself and the project expercinece. Then the interviewer gives a question of system design about LLM models, you must tell him all the…”
“The process is very unpredictable because I had one question where I was tested for strategic insight where I was asked very generic question about vision for agentic applications in infra. And then…”
“The process was straight-forward, I also felt sick the day before the phone interview and they rescheduled it without any problem. The phone interview was quite "flat", I talked almost the whole…”
“It was a mix of behavioral and hypthetical questions. The behaviroal part I was good at I think, but the hypothetical part it took me too long to answer and I was probably not confident enough, also…”
“It was smooth I had a python coding interview and then Googlyness questions which were based on projects I have worked so far”
“The interviewer gave me a very abstract description of a system, I needed to design, intentionally to let me clarify it through the questions. Most likely because role success depends on how…”
“Our interview process is straightforward: an initial conversation, a technical interview, and a final discussion focused on experience, communication, and problem-solving. What went well was keeping…”
“Throughout the process, I thought out loud, trying to take the interviewer along with me at every single step. He seemed pretty satisfied with my answers. At the end, we discussed the role of an…”
“The overall interview process was smooth and well-organized, moving from the initial recruiter reach-out to the technical and behavioral rounds within three weeks. Communication throughout was…”
“The recruiter was very clear and prompt about the expectations and the reply time for emails was generally great. The technical interviews were all DSA and had a story built around the underlying…”
“I gave a high level design, came up with requirements both functional and non functional, designed api's, data modeling etc. The feedback I got was that I did not do a deep dive on certain components”
“The recruiter round was for 30mins. Recruiter explained about the role and asked questions regarding my background”
“Just focus on you preparation and survive the situation the best you can. Don’t get nervous. Interview just tests your surviving skills.”
“few stages: an initial recruiter conversation, a technical screening, and then a set of onsite or virtual interviews. The technical rounds typically cover coding/DSA, system design, and behavioral…”
“Technical Depth: The technical discussions felt like peer-to-peer architecture reviews rather than a standard quiz. Mission Alignment: Every interviewer was deeply aligned with the company’s core…”
“The interview process was well organized and professional. The interviewer explained the process clearly and asked a mix of technical and behavioral questions. What went well was my ability to…”
“It's pretty standard. Medium difficulty, nothing that is really surprising. For the domain interview, they also expect you to do a mini-design, but it was simple and brief.”
“My case recruiter was unresponsive and they simply ignored me throughout the whole interview process and I still ghosted on the status.”
“The process was weird. I thought the interview went well, the interviewer even told me to prepare my leetcode for the next round and then I got rejected.”
“The process was long and hard, I prepared A LOT. The interviewers were mostly nice and positive. The recruiter was very helpful.”
“i think i definitely underprepared so i am preparing a lot leading up to my nexxt interview it was a good experience”
“The interview process was challenging but very informative. The recruiter guided me well about preparation.”
“Everything was quick; the recruiter was really informative. There is a lot of prep material. Very little technical stuff to deal with. I was also referred to the role so it was a little easier for…”
“DSA is the key. Learning problems will not help but understanding them will. I had 2 rounds online (1 technical, 1 behavioral) and 2 technical rounds onsite. Each technical round had 2 questions and…”
“It was good, not much feedback during the interviews, so there was not a lot of help. Most of the interview was independent”
“HR is amazing. The first company in Australia I encountered that arrange a time for phone screen and confirmation beforehand but not random call candidates at any time.”
“Google told me each round mapped to a specific rubric, but in reality the interviewers just asked whatever they wanted, and my so-called Googliness and execution round turned into Google Photos…”
“Interviewer was very comforting but focus on more Eval part. Prepare eval better along with failover strategy, model choices.”
“Coding question was not leetcode but it had lot of probing questions. I ended up not having sufficient time to complete it. The interviewer sounded positive like I would pass but I didn't”
“Pretty easy, just very long. For technical just need to do leetcode, no system design. Interviewers help you if you are stuck.”
“My strongest Google round was with a senior interviewer who never opened a LeetCode prompt. He just asked what I knew about algorithms, pushed me into distributed merge sort from first principles,…”
“I got all the way to the end for an L6 EM role, and the must-pass round was a 200-plus-line code review in a Google Doc where I had to manually debug broken interval logic with no IDE and no tools.”
“The hiring manager provided an overview of the team's structure, mission, and the open PM role. I shared my background and drew relevant connections to the team's focus area. The conversation…”
“I had prepared well with product sense, and had a good understanding of how ML algo's work, that instilled a lot of confidence in me. Having a clear structure and a lot of clarification questions…”
“Overall, the interview process was a positive experience. I enjoyed getting to know the team and appreciated how the interviewers made the conversations feel collaborative rather than overly formal.…”
“Very fast paced interview with lots of behavioural and analytical qus. Some interviewers were more intense than others.”
“The process was pretty straight forward. The recruiter gave good guidance and gave a list of concepts to prep from. Pretty generic.”
“The process was pretty straight forward just know how to do leetcode very well. I messed up the intervals question in which i was to merge intervals but build a new list on it which i could not…”
“Went harsh and the interviewer was rude while asking the questions it was 45 mins but they extended it beyond 1 hr”
“recruiter was helpful and gave accurate pointers on what to expect. They also try to set expectations wrt timing”
“Overall, this was one of the more rigorous interview processes I've been through, but also one of the most organized. The recruiter was transparent about the interview stages, what each round would…”
“The recruiter was very nice and all the interview went very smoothly. I think I was rejected because some of my answer showed unexperienced.”
“The process was quite different - they wanted a cybersecurity engineer with advanced DSA-level coding experience + consulting. Somewhere it seemed its kinda Software Security Engineer role, but they…”
“I’d been applying to Google for five years, like 50 to 100 times, with and without referrals, and this one just randomly responded. Honestly, I think for TPM it’s a chance thing, so sometimes you…”
“Techs were fair medium LC. Team match is dependent on team. They offer a third technical if one of them went poorly, which was nice.”
“overall smooth. Learned that they really care about full line by line understanding not just throwing things at the wall and what sticks.”
“One of my onsite interviewers pasted a prompt that was basically one sentence long and then just sat back. That round made it click for me that Google was testing how I clarified and structured the…”
“I was first contacted by the recruiter for a buisness DS position and had a quick screen. They walked me through the several rounds and what is covered in each. Later on they even helped me go…”
“They were trying to team match me to a Gemini role before the loop, and then in strategy it got almost combative. Every idea was, 'Slack can do that too, so how are you going to compete with free?'”
“The process was rigorous, and they clearly expected a high standard of technical knowledge even for a PM role. My recruiter was awesome and really helped move the process forward.”
“Smooth process, time taken after technical is very long wait. Talking through code went well, communication is important.”
“The process included an initial recruiter screen followed by two APM-style interviews focused on product sense, analytical thinking, and execution. I felt strong on the product design and…”
“Online application, then technical product manager interview, where I had to talk them through improving a selected product.”
“Pretty good. Interviewer is friendly and the problem is medium difficulty. It's a great experience to visit google campus.”
“Recruiter call was quite okay. It was just basic level of asking if I had certain experiences, very surface level of asking, then just preparing me for what the rounds are. Followed up with an email…”
“It was an internship role, AI engineer. First was an online coding round on arrays and strings where I had to return a palindromic subsequence, and later they asked dynamic programming and a linked…”
“The process was very profesional, got time to prepare and engage where possible, received alot of material to help me succeed.”
“The take-home said to spend no more than four hours on it, but if you're that far in the process, there's no way people aren't spending way more.”
“I probably did at least 10 solid 12 hour days of prep and kind of overprepped into oblivion, and then the interviews were so loosey goosey I barely got to show my thinking before they hired someone…”
“What surprised me most was that after typing a simple URL in the browser, they expected me to drive the whole conversation end to end, from DNS and system calls to interrupts and sockets, and then…”
“I just found like nervousness dropped my IQ like 20 points, so I ended up doing a lot of mocks with GPT. Then I started seeing way more causal inference in interviews, like the field can go back to…”
“Overall, the interview process was well organized and structured. I appreciated the communication throughout the process and the opportunity to speak with different people from the team. The…”
“The interview process was quite extensive, spanning approximately four months from the initial screening to the final offer. The interviewer mentioned that their goal is to accept candidates rather…”
“I’d never had to do vibe coding live before. In the product design interview, they gave me 10 to 15 minutes to actually build a rough prototype, and most of what they were probing on was how I…”
“Google’s online assessment took me like 5 minutes and it was supposed to be 90, and that’s when I realized they really prioritize your interactions with the interviewer. You absolutely are not going…”
“Recruiter call and 1st round scheduled in March 2025 which was people management. Next round System Design and scheduled in March 2025. Cleared both and next round schedule in in May. which was…”
“Asked to code the pre order traversal of a tree. Later asked determine if pre order traversals of two trees are same or not.”
“The process focused on data structures, algorithms, and problem-solving. The interviewers were professional, and I was able to explain my approach. I could have managed time better when optimizing…”
“If you are interviewing for a cloud role, reviewing topics from the PCA was helpful. That is the base, everything stems from there.”
“The process was tedious but having some patience helps. Ask questions first solve later. Understand what is being asked.”
“The interview process moved very quickly overall, which I appreciated because it kept momentum high and reduced uncertainty between stages. Communication from the recruiting team was generally…”
“The recruiter was helpful. The team itself is focused on supporting data management initiatives. But the questions were not all related to it. One of the questions was to code a palindrome- coding…”
“It was quite a lengthy process. The TAT was quite long and slow as well. Didn't receive a lot of feedback to prepare better for the next rounds, but overall was a great learning experience.”
“The interview process was well-structured and focused on both coding and system/infrastructure knowledge. The interviewers were professional and gave me enough time to explain my thought process. I…”
“Started off with recruiter screening with light technical questions, and walked me through all the rounds. Next, I had several rounds. Very light coding, mostly case studies and stats knowledge.…”
“The overall process was spread across months making it challenging to keep up with constant preparation. I was able to ace the product design, analytics and execution questions. I could have done…”
“Regular case questions, but took too long. Made final round and then team matching went on for months, until I finally pulled out.”
“It was okayish, however would have been better if I was better prepared for ML sys design fo NLP. I was good for CV projects and I filled out I want to go for CV but they gave me a NLP problem and…”
“The interview was not too bad, two mediums and two hards. I just don't enjoy coding that much so it went downhill.”
“It was nice but very robotic. The question was same as reported be others before. I started with the verbal solution first and then code in google doc.”
“I went through 5 rounds for a Senior PM role: a recruiter screen, a hiring manager call, then three virtual on-sites covering Product Sense, Analytical/Metrics, and Googleyness/Leadership, followed…”
“My process started with a talent screen with the recruiter and quickly moved to a hiring manager interview. They then scheduled me for a full loop on a tight timeline as I was far along with another…”
“What went well was my effort and organization. What didn't go well was time management. Next time, I would start earlier and ask for help sooner if I needed it. What stands out to me is how well…”
“It was a very long process. Got to Team matching phase, but wasn't able to match after several tentatives. The rounds after the full loop (where I got mixed rating) were harder than the techinical…”
“The process started with a resume screen followed by a recruiter call. There is a hiring assessment that they send you as a first step (behavioral questions). This was followed by the first…”
“Interviewer was very professional. Asked followup questions to the case. Cut me off at the end and said the CEO walked into the elevator and asked for the 2 minute pitch.”
“Long process with multiple rounds. Recruiter was very efficient and helped with expectations for each round.”
“They give you a study guide. I'd recommend reading it. It's your classic data structure and algorithms interviews.”
Frequently asked questions
How many rounds are in the Google interview?
Candidates report a typical 3 rounds, usually including a recruiter screen, online assessment, phone screen, take-home assignment.
How hard is the Google interview?
Candidates rate it 3.4/5 on average (medium), across 101 interviews.
How long does the Google hiring process take?
About 4 weeks from first contact to decision, based on reported timelines.
What percentage of Google candidates get an offer?
35% of candidates with a final result got an offer (24 of 68).
What does the Google interview focus on?
The most common round types are Behavioral, Coding, Technical, System Design.