I got into the loop through a backdoor-ish hiring manager route instead of a cold apply, and for L4+ I had to have a soft match with a team before the loop even started. My process was a recruiter alignment call, the GHA questionnaire, one phone screen, two onsite technicals, and a standard Googliness behavioral. What stood out was how collaborative and non-LeetCodey it felt, especially the phone screen, which was basically a live algorithms conversation that pushed on first principles instead of rehearsed patterns. I also learned that Google is doing more team matching before hiring committee now, because a hiring manager's statement of support can strengthen your packet if one round is only lean hire. I ended up accepting because the interview experience was consistently positive and honestly much better than how Google interviews are usually portrayed online.
I got in through a referral, so I didn't have a recruiter screen and went straight into interviews. I applied around the end of September, didn't hear back until mid-November, then did two 45-minute virtual rounds in December: one technical and one googliness/behavioral. I heard back within the week that I passed, then had about another month to prep before the onsite in mid-January, which was just two more 45-minute technical interviews. The coding questions felt more custom than straight LeetCode, and the main thing Google seemed to care about was how I clarified the problem, communicated my thinking, and reasoned my way to a solution. I made it through the full loop but got rejected, and the timing was all over the place because the first feedback came quickly while the final decision took about three weeks.
I applied online, sent the recruiter my transcript, graduation date, and availability, and then got an online assessment before they scheduled me. After that I had two 45-minute coding interviews in a scratchpad. There was basically no behavioral portion at all, and even the intros were super short before we jumped into the problem. The questions themselves were classic algorithm problems: one shortest-path style graph question and one meeting rooms question with an overnight twist. It felt very stripped down and technical the whole way through.
- Can you send your transcript, graduation date, and interview availability?
- Solve this shortest-path style graph traversal problem.
- Find the minimum number of meeting rooms needed to host overlapping meetings.
I got an OA first, and it was so easy that I finished it in about five minutes even though it was supposed to be ninety, which told me pretty quickly Google was not using that as the real filter. After that I had two technical interviews that were both blank-doc coding rounds where you cannot run code, so the whole thing is about reasoning, asking good questions, and keeping the interviewer engaged while you work. My actual coding questions were both pretty standard LeetCode-medium level, but the follow-up optimizations were where the signal really was, especially when I had to optimize a heap update problem with no hints. Then I went into team matching, which lasted way longer than the technicals and stretched from September into December with multiple team-specific conversations. Those calls were mostly resume-driven, but some were unexpectedly technical, so it felt like the real bottleneck was not passing interviews but getting matched.
It felt pretty classical to me. What surprised me was how streamlined it was, because for the internship loop I only had two rounds. There was no system design round at all. Both interviews were basically coding rounds, and they stayed really focused on fundamentals like graphs, heaps, and prefix sums. That was the whole process for me.
- Solve this graph algorithm question.
- Can you implement a min heap?
Recruiter was very helpful but the interviewers varied.
First one was very nice and an active participant.
Second pasted the question prompt and was mostly quiet for an hour.
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.
- A LC type question and a AI based codebase bug fix
- Prime number
- Given a family tree, find upcoming birthday
The questions were not too difficult, more so worry about asking clarifying questions and making sure your implementation is clear to the interviewer.
- Simple array and string processing
- plant adjacent crops in a 2d array field
- linked list, add, delete
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 discussed different approaches to the binary tree problem, along with their tradeoffs, time and space complexity. In the second round, we explored multiple variations of the router problem, which tested both problem solving and code design.
What went well was that I could come up with optimised solutions, write working code, and explain my thought process clearly. I also enjoyed discussing how to make the code flexible enough to handle changing requirements. Overall, I felt comfortable with the discussions and was able to address the variations we covered. I don't think anything went particularly poorly, though I could always improve on how quickly I explore edge cases and communicate tradeoffs.
- Find Leaves Of Binary Tree
- Question: https://leetcode.com/discuss/interview-question/2064646/google-screening-interview-question-may-2022
Pretty standard process. Interviewers were friendly and seemed to enjoy the work culture. The interviews themselves weren't too difficult, mostly standard leetcode questions.
The process on start is very easy ( online assessment , phone screen) but coding is very difficult - LEETCODE MEDIUM
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 interviewer and appreciated the professional and respectful approach. One area that could have gone better was that I was a little nervous at the beginning, but I became more confident as the interview continued. Overall, it was a positive and useful experience.
The most organized and nicely structord interview process. Starting from the recuitor reach out, to the people I interviewed with and the whole process itself. They seem to really care about that process.
- Regular just fit into google
- House robber question just in different wording. Dynamic programming that was quite challenging
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 expect from the different interview stages.
The technical interview was challenging and gave me an opportunity to demonstrate my problem-solving approach. I felt the discussion was engaging, although I would have benefited from having more clarity around the expectations for the specific problem and additional time to explore and optimize my initial solution.
The Googleyness and Leadership portion allowed me to reflect on my experiences with collaboration, leadership, and working through ambiguity. Overall, I found the process valuable and appreciated the opportunity to learn from the experience.
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 time both at the technical and behavioural round and the interviewers basically always only agreed with what I was saying. The on-site was really cool, offices are great and my 2 interviewers were really kind persons that made me feel very comfortable.
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 intern at Google and the different teams within the company.
- Can you introduce yourself?
- Course Schedule
- You are given an array and an operation that you can perform on it. In one operation, you can select any two distinct indices i and j, remove arr[i] and arr[j], and add (arr[i] + arr[j]). This operation costs you (arr[i] + arr[j]). What is the minimum cost to reduce the array to a size of 1?
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 question that the candidate has to uncover to get to the actual algorithm.
The Googliness interview for me particularly was all 'how would you' questions instead of 'tell me about a time' questions, which surprised me a little and I probably did not do as well as I should have. Clarity of thought and conciseness in response is incredibly important for these interviews.
For the onsites, both my interviewers were helpful and communicated really well. The second interviewer went really deep into the time and space complexity of Djikstra's, a couple layers below the standard answers and the follow-ups became increasingly complicated to answer. In hindsight, my overall interview loop focused on depth of DSA knowledge over doing all sorts of obscure medium and hard leetcode questions.
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
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 or leadership-oriented questions. For a Senior role, I’d expect system design and demonstrating technical leadership to carry significant weight. I’d also prepare for Googleyness/culture-related questions
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.
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 focus on safety, reliability, and scaling responsibly.
Problem Scope: The system design scenarios perfectly mirrored the actual, massive-scale infrastructure problems the team faces daily.
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 explain my projects and answer fundamental software engineering questions. However, I struggled with a few system design concepts and could have provided more detailed answers in some technical discussions.
My case recruiter was unresponsive and they simply ignored me throughout the whole interview process and I still ghosted on the status.
- Implement self-locating strings in pi
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.
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 one has to do well in every round. I did well on the online rounds and got stuck on 1 question in one of the onsite round. Ultimately, I took more than expected time for 1 question in my last round which I could have done better.
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.
Pretty easy, just very long. For technical just need to do leetcode, no system design. Interviewers help you if you are stuck.
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. The technical questions were challenging but fair, and I liked having the opportunity to explain my thought process. One thing that could have been better was having more clarity on what to expect in each round, especially regarding the format and difficulty of the technical interviews. Other than that, I thought the process went smoothly.
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 really comprehend
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.
Software Engineer
1. Online assessment with two easy style LeetCode questions
2. Round 1 interview: one behavioral asking questions to test your leadership, working with others, and how you deal with failure/ambiguity. One technical interview.
Smooth process, time taken after technical is very long wait. Talking through code went well, communication is important.
- How many Leetcode questions have you done?
- Many dice questions
- Time complexity of two pointer?
The process was very profesional, got time to prepare and engage where possible, received alot of material to help me succeed.
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 technical interviews were challenging but relevant and gave me a good understanding of the level expected at Google.
One thing that could have gone better was the amount of time between some stages, as it made the process feel a bit longer than necessary. Overall, though, I had a positive experience and appreciated the professionalism and transparency of the interviewers.
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 than reject them, and they primarily evaluate how you navigate challenges while problem-solving.
- it was just resume shortlisting
- It has 2 dsa problem need to be solved in 1 hr
level of dsa problem was medium
- it has multiple behaviour problem more related to what I have done in past ?
what I can improve ?
what I can bring on table ?
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 solutions.
The process was tedious but having some patience helps. Ask questions first solve later. Understand what is being asked.
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 was ultimately rejected because my coding experience, particularly with data structures and algorithms, was not strong enough. In hindsight, I could have communicated my approach more clearly and solved the coding problems more efficiently. Compared to other interviews I've done, this one placed a stronger emphasis on coding fundamentals while also evaluating infrastructure concepts.
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 was stumped there.
- Mostly about the role, what I have done in the past and details about the role, etc
- This was a pure bfs question - like rotting oranges
- This was a dfs questions like finding the word in a matrix
The interview was not too bad, two mediums and two hards. I just don't enjoy coding that much so it went downhill.
- If a robot was trying to move from one location to another location with obstacles in the way, code up a solution for that
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.
They give you a study guide. I'd recommend reading it. It's your classic data structure and algorithms interviews.
Software Engineer
Software Engineer
Software Engineer
Software Engineer
Software Engineer