Community Posts
Read and share interview experiences and discussions
Google Software Engineer Mid-LevelA Google software engineering phone screen with two rounds. The behavioral round covered conflict, differing work styles, a teammate who is not engaged, and having too many tasks. The coding round covered a TTL-limited network connection problem and a follow-up without a TTL limit. The interviewer gave few examples and limited feedback during the coding round.
Google Software Engineer Mid-LevelA Google L4 phone screen with one coding problem about redistributing numbers across rows so that each row is sorted with no duplicates, including a check for the impossible case. The phone screen then covered behavioral questions about conflict and mistakes.
Google Software Engineer SeniorA Google L5 onsite with two coding rounds and an AI token rate-limiter design round. The candidate's request to switch the onsite to a virtual onsite was declined.
Google Software Engineer Mid-LevelA Google L4 software engineering interview with a coding section and a Googliness behavioral section. The coding section covered a BFS grid-connectivity problem and a follow-up that counts lakes fully enclosed by land.
Google Software Engineer InternA two-round Google software engineering internship interview. The algorithm round expected multiple solution approaches and an understanding of how data structures such as quicksort and binary search trees are implemented. The system design round focused on understanding requirements, choosing data structures, and defining clear class structures.
Google Software Engineer Mid-LevelA Google Sunnyvale onsite for an L4 software engineering role with two coding rounds. The first combined a DFS and object-oriented design problem about nested variable expansion with cycle detection, and the second was a variation of a word-distance problem with a class-design follow-up. The process ended in a no-hire decision citing communication.
Google Software Engineer Mid-LevelA Google software engineering phone screen with two back-to-back 45-minute interviews. The first was behavioral and covered disagreements with colleagues, conflicts with other teams, and managing an uncooperative junior colleague. The second was a coding problem to implement an HTTP router that registers handlers and looks up handlers for request paths using a prefix tree.
Google Software Engineer InternA two-round Google 2027 summer software engineering internship process. The first round asked the candidate to merge two YAML-based trees with many merge rules, and the second asked for a knapsack-style selection problem. The first prompt was long and took substantial time to understand.
Google Software Engineer Mid-LevelA Google behavioral interview with four questions: improving oneself, handling a disagreement between two people, learning from a former leader or manager, and prioritizing a large amount of work. The interviewer details, round format, and outcome were not reported.
Google Software Engineer SeniorA Google L5 phone screen round with a median-of-sorted-arrays coding problem, a follow-up with many inputs, and behavioral questions about a successful project, a teammate conflict, a changed view of a teammate, and the values sought in a next role. The candidate's result was not reported.
Google Software Engineer Mid-LevelA Google L4 onsite with two rounds, a solution design interview and a coding interview. The onsite was in person with a virtual option available, and the candidate had four interviews with Google in total.
Google Software Engineer Mid-LevelA two-round Google L4 phone screen. The first round combined coding questions with behavioral questions about a project deep dive, collaboration and project management, and conflicts and tradeoffs. The second round was a solution design interview followed by a coding problem. The candidate reported passing the screen.
Google Software Engineer JuniorA Google L3 software engineering process that ran over several months, with an online coding round, a behavioral round, and two onsite coding rounds. The candidate reported passing the later rounds, and the team match was still pending.
Google Software Engineer SeniorA senior onsite for an Applied AI role with two coding rounds and one system design round. The candidate reported that interruptions in the first coding round disrupted the flow of the interview, and recruiter feedback described that round and the system design round as below expectations.
Google AI/ML Engineer Mid-LevelA single machine learning system design interview for a Watch Next recommendation system for a video-streaming product. The interviewer asked detailed follow-up questions about loss functions and optimizer formulas.
Google Software Engineer Mid-LevelA two-round process for a GenAI software engineering role: a data structures round on grid connectivity problems with a follow-up, and a requirements and design round for an AI agent in manufacturing. The design round included follow-up questions on hallucination prevention and permissions. The candidate reported running short of time in the first round and answered the design round normally.
Google Software Engineer New GradA New Grad Google process that began with an online assessment, followed about two to three weeks later by a four-round verbal (VO) interview loop. Each round combined a coding problem with behavioral questions, which mostly covered team projects and related experiences.
Google Software Engineer Mid-LevelA phone coding interview with a path-existence warmup and a safest-path problem on a grid with a cat, a Googlyness phone round, and two onsite coding rounds on rectangle area, job scheduling, and range-uniqueness queries. The record gives the prompts and examples but not the candidate responses or the outcome.
Google Software Engineer Mid-LevelA phone coding interview on grid path counting with checkpoint constraints, a Googlyness round, and two onsite coding rounds on graph shortest paths and time-ordered connectivity, each with follow-ups. The record does not describe the candidate solutions or the outcome.
Google Software Engineer Mid-LevelA Level 4 onsite round with two coding interviews: a problem whose statement is not included, and a URL request-handler router with path parameters. The record gives the router rules but not the candidate approach or result.