Google Software Engineer (SWE) New Grad Interview

The Google new grad SWE interview measures how clearly you reason out loud at every step of the loop. Interviewers require a line-by-line walkthrough of your code in the technical screen, treat time and space complexity as a core evaluation dimension, and may give you a vague prompt during the onsite to test whether you ask clarifying questions before coding.

Effective software engineering interview prep for the new grad loop emphasizes clarification and complexity reasoning alongside pattern fluency.

This guide breaks down each stage of the new grad SWE interview process, what Google interviewers look for, and how to prepare with real example questions, actionable tips, and resources.

Google new grad SWE interview process

The Google new grad SWE interview process is unusually compact for a FAANG loop, running three interview rounds after the initial screening stage. The interview loop is the same regardless of which team you'll join, and team matching happens after the final round.

Here's what the interview process can look like for a new grad or junior candidate:

1. Recruiter screen and online assessment: Initial alignment check or a 60-90 minute coding test, depending on how you entered the pipeline
2. Technical screen: A 45-minute coding interview with a Google engineer in a shared document
3. Behavioral screen: A 45-minute round covering workplace-conflict scenarios and a resume walkthrough
4. Onsite coding interviews: Two 45-minute coding rounds, typically held at a Google campus on a provided Chromebook

Recruiter screen and online assessment

How the Google new grad SWE process starts depends on how you entered the pipeline. Candidates with a referral or recruiter outreach typically skip straight to the technical phone screen, while candidates who applied directly may receive either a recruiter call or an online assessment first.

The recruiter call covers a brief resume walkthrough, working style, and availability, since new grad candidates may still be finishing school or completing an internship. Expect questions about the types of projects you've enjoyed working on.

The online assessment runs on HackerRank or Google's internal coding platform and includes two questions to complete in 60-90 minutes. Expect data structures and algorithms challenges, often involving graph or tree traversal, or writing functions to simulate the outcome of a rules-based game.

Recently asked questions

Here are real, recent interview questions reported by candidates:

• Reverse a singly linked list in place.
• Given an integer array, return true if it has a subarray that sums to a multiple of k.
• Given a matrix with a rat, bread, cat, and obstacles, find a path that maximizes the minimum distance from the cat.

Technical screen

The Google new grad SWE technical screen is a 45-minute coding interview conducted in a shared Google doc that doesn't execute code. Expect a coding challenge focused on a common data structure pattern, followed by a line-by-line walkthrough where you talk the interviewer through your code using an example you generate yourself.

Interviewers may not specify target time and space complexity upfront in this round, and you're expected to ask before you start coding. Prepare for follow-ups on specific language functions or methods you used, especially edge-case behavior.

Interviewers look for:

• Clarifying instinct: Whether you surface assumptions about input shape, target complexity, and edge cases before writing code
• Pattern recognition: How quickly you map the prompt to the correct data structure approach
• Code-walkthrough fluency: Your ability to talk through your own code line by line against an example you generate, catching errors as you go
• Complexity reasoning: Whether you can state the time and space complexity of your solution and articulate concrete paths to improve it
• Function-level precision: How well you understand the language functions and methods you use, including their behavior on edge cases

Recently asked questions

Here are real, recent interview questions reported by candidates:

• Given an array of strings, return a 2D array grouping buddy strings.
• Given an integer array, return an array where each element is the product of all other elements except itself, without using division.

Behavioral screen

The Google new grad SWE behavioral round, known internally as Googleyness, is a 45-minute interview paired back-to-back with the technical screen, focused on workplace-conflict scenarios and a brief resume walkthrough. Expect the interviewer to review your resume at the top of the round, ask about past internships or projects at a directional level, then move on to hypothetical conflict prompts.

Follow-up questioning is sustained. When you describe an approach (e.g., "I'd surface my contributions in a one-on-one with my manager"), expect the interviewer to ask exactly what you'd say, what you'd bring to the meeting, and how you'd handle pushback. Anticipate the follow-ups and prepare concrete answers.

Interviewers look for:

• Conflict-handling depth: How you'd communicate when a coworker, another team, or a manager creates friction around your work
• Specificity under follow-up: Whether you can describe concrete tactics instead of restating principles
• Self-advocacy without ego: Your ability to surface your contributions to a manager without sounding defensive or transactional
• Cross-functional judgment: How you'd handle a disagreement during a meeting with a coworker who wants to solve a problem differently
• Resume coherence: Whether your past internships or projects hold up when an interviewer asks what you liked, disliked, and learned

Recently asked questions

Here are real, recent interview questions reported by candidates:

• How would you handle a situation where another team rewrote code you'd written, and the rewrite broke functionality?

Onsite coding interviews

The Google new grad SWE onsite interviews consist of two 45-minute coding rounds, typically held at a Google campus on a provided Chromebook with the same shared-document environment as the technical screen. Each round is a single coding challenge with a different interviewer, and the questions tend to be more custom than standard pattern-based challenges.

Interviewer behavior varies between the two rounds. One interviewer may specify the target time complexity upfront (e.g., "I'm looking for a linear solution") and point out exactly where your current approach falls short of it. Another may give you a one-sentence, under-specified prompt and wait for you to clarify; starting to implement before clarifying scope is a common reason candidates underperform in this round.

Interviewers look for:

• Clarification before code: Whether you surface scope, constraints, and edge cases before reaching for an implementation
• Process-led thinking: How you narrate your reasoning, not just whether you arrive at a working solution
• Hint integration: Your ability to incorporate a targeted nudge (e.g., "have you considered modulo here?") into a meaningfully better approach
• Complexity targeting: Whether you can match a stated complexity bound and identify where your current solution exceeds it
• Custom-prompt adaptability: How you handle challenges that don't map cleanly to a memorized pattern

AI-assisted coding round

The new code comprehension round asks candidates to use Gemini to read, debug, and optimize an existing codebase, with interviewers evaluating AI fluency: prompt engineering, output validation, and debugging skills.

Recently asked questions

Here are real onsite coding interview questions reported by candidates:

• Given an array of strings, compare them using a sliding-window approach to find pairs or groups that satisfy a defined relationship.
• Given an array and a window size, return the maximum value in each sliding window as the window moves across the array.
• Find the minimum window substring that contains all characters of a target string.
• Given a string and an integer representing a width, return how many lines the string can be written across.
• Given an array of integers and a target value, find elements that sum to the target.

How to prepare for the Google new grad SWE interview

1. Solve challenges by hand first: Before opening a coding environment, work through the prompt on paper or a tablet. Build the intuition for the solution before translating it into code.
2. Treat complexity as a core skill: State the time and space complexity of every solution you write during practice, then articulate at least one concrete improvement path. Google interviewers will ask for both, and some will state the target complexity in advance.
3. Practice clarifying under-specified prompts: Train yourself to spend the first 2-3 minutes asking questions on any prompt that feels vague. A one-sentence prompt is a signal to clarify scope before coding.
4. Run mock interviews on data structures and algorithms: Aim for five or more before your interview. Practice the walkthrough explicitly: code a solution, then talk through it line by line with a self-generated example.
5. Prepare conflict scenarios with specifics: For the behavioral round, build out 2-3 workplace-conflict stories with concrete tactics ready to surface under follow-up. The interviewer may keep asking "and then what?" until you produce something actionable.
6. Expect custom challenges: Google's coding rounds tend to deviate from standard pattern-based formats, so memorizing solutions to common patterns won't cover the range you'll see. Practice applying patterns to unfamiliar prompts instead.
7. Get expert feedback before the onsite: Most candidates fail several onsite interviews before receiving an offer, and Google is rarely the easiest interview on a candidate's list. If you can't schedule real onsites at other companies first, work with a Google SWE coach for mock interviews and feedback calibrated to Google's evaluation style.

Additional resources

• Google software engineer interview questions
• Coding interview questions
• Algorithms interview questions
• Behavioral interview questions
• Data structures and algorithms mock interviews
• Behavioral mock interviews
• Google SWE interview guide
• Last-minute coding interview prep blog post

FAQs about the Google new grad SWE interview

How long does the Google new grad SWE interview process take?

The Google new grad SWE interview process typically runs 2-3 months from application to onsite, though the wait between the onsite and a final decision varies widely. Expect 1-4 weeks between applying and a first-round invitation, then about one month of prep before each subsequent round. Decisions can come within a few days of the onsite or take three or more weeks, while team matching can last several months.

Does Google use standard coding challenges in new grad SWE interviews?

Google's new grad SWE coding questions typically build on common data structure and algorithm patterns (sliding window, two pointers, hashmaps, modular arithmetic), and interviewers use refreshed internal question banks. The evaluation factors in reasoning, clarification, and complexity targeting alongside the final solution, so candidates who memorize pattern solutions without practicing communication often underperform.

What happens after the final round at Google for new grad SWE candidates?

After the final round of the interview, Google's new grad SWE candidates either receive a direct offer, a rejection, or are routed into team matching. Team matching is Google's process for placing approved candidates with a specific team, and it can stay open for weeks or months. A rejection followed by a team-matching callback is a known outcome; the post-loop timeline is unpredictable.

How much does a new grad Google software engineer make?

Here are the reported compensation ranges by level for new grad or junior Google software engineers, according to Levels.fyi:

• L3 (SWE II, Entry Level): ~$212K
• L4 (SWE III): ~$308K