Google Software Engineer Intern Interview

Google's software engineer (SWE) intern interview tests how well you reason through a challenge, communicate your thinking, and self-correct.

The technical rounds are run through Google’s internal coding platform, which functions like a collaborative plain text editor with basic syntax highlighting. Interviewers evaluate how you ask questions and work through errors as much as what you produce. Getting through the technical rounds is only part of the process; team matching selects for niche specialization and resume depth, and it's where the field narrows most.

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

Google SWE intern interview process

Google's SWE intern loop is team-independent through the technical rounds. Your interviews don't change based on which team you're targeting, but entry points can vary depending on how you enter the pipeline.

The process from recruiter call to offer typically takes 4-6 weeks, though team matching can extend the timeline.

Here's what the interview process can look like:

• Recruiter call: A brief profile check covering your resume, experience, and scheduling for technical interviews
• Online assessment: A timed, low-difficulty coding and behavioral screen
• Technical interviews: Two rounds, 45-60 minutes each, solving coding challenges on Google's coding platform
• Team matching: A series of 30-60 minute calls with hiring managers, covering behavioral questions and resume fit

Recruiter screen

Google's SWE intern recruiter screen is a brief profile check, typically conducted over Google Meet with a recruiter or staffing specialist. The call covers your resume, prior internship experience, coding prep level, preferred programming language, and scheduling for the technical rounds.

The call is focused on logistics and alignment. It can function as a filter, though; candidates without sufficient coding prep experience may not advance to the technical interviews. Recruiters may focus on collaborative projects and hands-on experience, which give a clearer signal of your experience working with others.

Recently asked questions

Here are some example questions reported by candidates:

Online assessment

The online assessment for Google's SWE intern role is a timed coding screen, typically 60-90 minutes with one or two algorithm and data structure questions. The platform is typically Codility or HackerRank, depending on batch and region.

Difficulty is generally easy to medium, with questions centered on arrays, graphs, trees, string manipulation, and dynamic programming. You may need to write your own test cases, as they aren't always provided.

Google may also include a separate Hiring Assessment alongside the OA, a behavioral questionnaire with Likert-scale responses. The questionnaire is long (50-75 questions) and assesses your working style, ethics, and other behavioral factors. Consistency across your responses matters, so keep your earlier answers in mind as you move through it.

Recently asked questions

Here are some example questions reported by candidates:

Technical interviews

The technical interviews in Google's SWE intern loop test your ability to reason through coding challenges while keeping the interviewer engaged in your thought process. Each round runs 45-60 minutes, and you'll work in a shared document on Google's internal coding platform with no IDE, no autocomplete, and no ability to execute your code.

The format is self-guided. Interviewers paste a brief prompt (often just two or three sentences) with no test cases, and you're expected to ask clarifying questions before writing any code. Google interviewers may hold back information deliberately to see whether you ask for it, though some candidates report receiving a prep session beforehand that narrows the topic scope.

Interviewers look for:

• Communication throughout the session: Whether you verbalize your intent and reasoning as you work, explaining why you're making each decision
• Clarifying questions before coding: Your ability to identify missing information and ask for test cases, constraints, and edge cases before starting
• Code readability: Whether your code is clean, well-structured, and uses descriptive variable names, especially given the blank document format with no syntax highlighting
• Self-guided debugging: Whether you draw out your own test cases, walk through edge cases, and fix errors without relying on the interviewer to find them
• Complexity analysis: Your ability to articulate time and space complexity for your solution and reason about whether a more optimal approach exists
• Collaborative problem-solving: How you collaborate with the interviewer, checking in at key decision points and incorporating their feedback
• Interviewer engagement: Whether you maintain the interviewer's active interest throughout the session

Difficulty ranges from easy to medium on standard coding challenges. Interviewers create their own variations on common patterns, so expect familiar structures with a twist. Challenges may involve processing streams of data, interval manipulation, or heap-based optimization.

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, recent technical interview questions reported by candidates:

• Given a stream of intervals, process them one at a time and determine how they overlap or merge with previously seen intervals.
• Implement a priority queue that maps identification tags to entries, then optimize it so you can update values already in the heap without removing and reinserting them.
• Design a class that caches information from a data stream and batch-processes incoming entries rather than handling each one individually.

Team matching

Team matching in Google's SWE intern process evaluates whether your skills and experience align with a real project that a team is working on. After you pass the technical rounds, you'll receive a questionnaire about your interest in different Google products and services. Be specific and opinionated here; teams select for candidates who show genuine enthusiasm for their domain.

You're competing against master's students, PhD candidates, and full-time employees, so the key is specificity. You'll need to connect your experience, both technical and interpersonal, to what that team is working on in real time.

Each call runs 30-60 minutes, and you may not learn the team or role until the session itself. The process can take weeks, and candidates who pass the technical interviews are sometimes not matched to a team at all.

Interviewers look for:

• Resume-to-role alignment: Whether your technical experience and project work map to the team's specific domain
• Niche specialization: Whether you've developed depth in a focused area (e.g., AI agents, systems optimization, applied ML) rather than listing broad, generic skills
• Ability to articulate fit under pressure: How you connect your background to an unfamiliar team and role in real time, without advance preparation
• Enthusiasm for the team's domain: Whether you show genuine interest in and knowledge of what the team is working on
• Authenticity: Whether your described experience holds up under follow-up questions
• Technical depth on past work: Whether you can walk through implementation details, trade-offs, and optimization decisions for projects on your resume, including cross-language or performance-focused follow-ups

Sample questions

Team matching questions are driven by your resume and the team's domain, so there's no standardized question set. Here are examples of what to expect:

• How would you rebuild your project in a different language to improve performance?

How to prepare for the Google SWE intern interview

1. Practice reasoning on a blank document: Solve coding challenges in a plain text editor with no syntax highlighting, autocomplete, or execution. Focus on talking through your approach, drawing out test cases, and catching errors manually. This mirrors the real interview format.
2. Study class-based and heap optimization patterns: When a challenge involves streaming input, consider whether a class-based solution with caching would outperform a simple iterative approach. For heap-based challenges, think about auxiliary data structures (like an array that tracks element positions within the heap) to enable in-place updates.
3. Build your communication habit: Practice verbalizing intent behind every decision. Instead of saying "I'm writing a for loop," explain why: "I'm iterating through the sorted intervals to find the first overlap." Run through mock interviews with a partner who can give feedback on how engaged they felt during your walkthrough.
4. Specialize your resume before applying: Google matches interns to teams based on specific skill sets. Pick an area tied to your genuine interests, build projects in that area, and pursue prior internship or research experience if possible.
5. Practice adapting your pitch in real time: You won't know the team or role before the call, so practice connecting your experience to unfamiliar contexts on the spot. 1:1 coaching sessions are a good way to simulate this; an expert can push back on your framing the way a hiring manager would.

Additional resources

• Google Software Engineer Interview Guide
• SWE Interview Practice Course
• SWE Behavioral Interview Course
• Mock interviews
• 1:1 expert coaching
• Google SWE Interview Questions
• Google's advice on how to prepare for the hiring process

FAQs about the Google SWE intern interview

Is there a recruiter screen for Google's SWE intern interview?

Google's SWE intern process typically includes an initial recruiter or staffing specialist call to verify your profile, discuss your experience, and schedule the technical interviews. The call is a logistics and alignment check focused on fit and scheduling.

What difficulty level are Google's SWE intern coding challenges?

Google's SWE intern technical interviews stay in the easy to medium range, but interviewers write their own variations on common patterns. A standard interval merging challenge, for example, might be reframed as processing a stream of data one entry at a time. The interviewers are less interested in a pristine solution than they are testing your ability to think through the problem and communicate about your process.

How hard is team matching at Google?

Google's SWE intern team matching is competitive: you're matched against master's students, PhD candidates, and even full-time employees for positions on specific teams. Niche specialization and a project-driven resume are the biggest factors in getting selected.

Do you find out your team before the Google SWE intern team matching interview?

Google doesn't share the team or role before the SWE intern team matching call. You'll learn what team you're interviewing with during the session itself, so focus your prep on knowing your resume deeply enough to adapt your pitch to any team.

How much does a Google SWE intern make?

Here are the reported compensation ranges for a Google SWE summer 2026 internship in the US, according to Levels.fyi:

• Undergraduate: ~ $55-57/hr (~ $9,400-9,800/mo)
• Master's: ~ $61/hr (~ $10,500/mo)
• PhD: ~ $72/hr (~ $12,500/mo)

Google also typically provides a housing stipend and a relocation allowance, though these vary by location and program year.