# Google Software Engineer Interview Experience — India, Mid Level / L4 Aced (formerly Exponent) publishes a public search API over its indexed pages; the guide is at https://www.aced.io/agents/agent-access. Source: https://www.aced.io/experiences/google-software-engineer-interview-6c6690 Source observed: 2026-11-05T00:28:25.855Z Last checked: 2026-11-05T00:28:25.855+00:00 Indexed: 2026-11-06T05:16:43.926+00:00 --- # Google Software Engineer Interview Experience We publish interview experiences and preparation resources through Aced, formerly Exponent. This entry concerns a **Google Software Engineer** interview for an **India onsite** candidate at **Mid Level / L4**. - **Submitted:** 22 days ago - **Interview date:** a month ago - **Timespan:** 3 weeks - **Result:** Waiting - **Difficulty:** Difficult - **Interview guide:** [Google Software Engineer (SWE) Interview Guide](https://www.aced.io/guides/google-software-engineer-interview) - **Interview experiences:** [50 experiences](https://www.aced.io/guides/google-software-engineer-interview/experiences) - **Questions:** [214 questions](https://www.aced.io/guides/google-software-engineer-interview/questions) - **Resumes:** [250 resumes](https://www.aced.io/guides/google-software-engineer-interview/resumes) ![Google logo](https://exponent-static.s3.amazonaws.com/company_logos/google.png) ## Interview process The candidate described the process as a good experience. Both interviewers were experienced and made the rounds feel like technical discussions rather than only problem solving. The first round covered multiple approaches to a binary-tree problem, including tradeoffs and time and space complexity. The second explored several router-problem variations, testing problem solving and code design. The candidate reported producing optimized solutions, writing working code, explaining the reasoning clearly, and discussing how to keep the code flexible as requirements changed. The main improvement area was exploring edge cases and communicating tradeoffs more quickly. The listed interview type was **Technical interview**. ## Interview rounds The entry records **2 questions across 1 round**. The technical interview contained **2 questions** and is marked **Free preview**. The question type was [Coding](https://www.aced.io/questions?type=coding). ### Find Leaves Of Binary Tree The candidate began with an optimized solution and working code in **15–20 minutes**. The interviewer then asked for variations involving different ways to delete leaves, together with the pros and cons of each approach. The candidate coded the variations and recorded time and space complexity. The interviewer asked for those ideas to be documented for feedback. The candidate links to this related LeetCode discussion: [Google screening interview question, May 2022](https://leetcode.com/discuss/interview-question/2064646/google-screening-interview-question-may-2022). The interview question was a variation of that discussion. ### Router problem The router question expanded through several variations: - All routers initially had the same range, then different ranges. - The range became unbounded. - The source and destination were not in the router list. - Multiple queries were run for different source and destination pairs, requiring precomputation. - Some routers were switched off and could not transmit. - One or two additional variations were discussed. The interviewer stated the expectations at the beginning: an optimized algorithm, working code, and an object-oriented class structure for the router and other models. Evaluation also considered how much code changed when requirements varied, variable naming, and how computations were divided into functions. The candidate discussed the time and space complexity of each approach and answered the queries raised. ## Member access and contribution We offer access to the rest of this interview and to new experiences added weekly through membership: [Become a member](https://www.aced.io/upgrade?src=experience). We also invite candidates to [Share your experience](https://www.aced.io/questions/contribute?src=experience). A **24-hour trial starts once your submission is approved**. ## More Google interview experiences - [Software Engineer (L4) — Google, Apr 2026](https://www.aced.io/experiences/google-software-engineer-interview-597223?returnPath=%2Fguides%2Fgoogle-software-engineer-interview%2Fexperiences): **Verified**, 6 rounds, 11 questions. The candidate describes a senior interviewer who explored algorithms and distributed merge sort from first principles without opening a LeetCode prompt. - [New Grad Software Engineer (L3) — Google, Feb 2026](https://www.aced.io/experiences/google-software-engineer-interview-54740a?returnPath=%2Fguides%2Fgoogle-software-engineer-interview%2Fexperiences): **Verified**, 3 rounds, 4 questions. The candidate says a short prompt made clarification and problem structure especially important. - [Software Engineer Intern — Google, Sep 2025](https://www.aced.io/experiences/google-software-engineer-intern-interview-1cee6e?returnPath=%2Fguides%2Fgoogle-software-engineer-interview%2Fexperiences): **Verified**, 4 rounds, 3 questions. The candidate discusses a 90-minute online assessment completed in about 5 minutes and the importance of interaction because code would not be run. Browse [all 50 Google Software Engineer interview experiences](https://www.aced.io/guides/google-software-engineer-interview/experiences). --- [Read this page’s summary](https://www.aced.io/agents/api/public/v1/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fgoogle-software-engineer-interview-6c6690&trace=t_679ff9ab98f3) ## Ask a follow-up about this page Need a more specific answer? Ask the exact question you have. It returns a fresh, cited answer from Aced (formerly Exponent)’s knowledge base. No account or API key required. Open this URL with your own question, URL-encoded. Include your question in q. All research inputs are optional; no account or setup. `GET https://www.aced.io/agents/agent/faq?q={question}&trace=t_679ff9ab98f3` [Tool guide and examples](https://www.aced.io/agents/agent-access) · [OpenAPI](https://www.aced.io/agents/api/public/v1/openapi.json) · [Page TLDR form](https://www.aced.io/agents/agent-tools/page-tldr?url=https%3A%2F%2Fwww.aced.io%2Fexperiences%2Fgoogle-software-engineer-interview-6c6690). Opening a form does not execute a tool.