The two stages nobody warns you about
- Stage one - the interviews. Typically two technical rounds of around 45 minutes, usually virtual, each with one or two problems in a shared editor.
- Stage two - host matching. After you pass, your profile is circulated to teams with intern seats. A host has to choose you. Candidates can and do pass the interviews and never get matched, which is the part that catches people out.
What the technical rounds are like
The interviews are data structures and algorithms, conducted conversationally. Interviewers expect you to talk through the approach before writing anything, and the discussion is a scored part of the round rather than a preamble to it.
- Arrays, strings and hash maps - the bread and butter.
- Trees and graphs - traversal, breadth-first and depth-first, shortest-path variants.
- Recursion and backtracking - generating combinations, permutations, subsets.
- Binary search, including the harder variant of searching an answer space rather than an array.
- Light dynamic programming - the entry-level problems, not the hard ones.
- Follow-ups that change the constraints - this is characteristic. Expect "what if the input does not fit in memory" after you solve the first version.
Those follow-ups are the real differentiator. The first solution is often the easy part; what is being tested is whether you can adapt it when the problem shifts under you. Our 15 patterns guide covers recognition, and the Blind 75 is the right problem set for this loop.
How to handle the conversation
- Clarify before coding. Ask about input size, duplicates, empty input and the expected output format. This is scored.
- State your approach and its complexity before you write. If it is the brute force, say so and say what you would improve.
- Narrate while writing, but do not provide a running commentary on syntax. Explain decisions, not keystrokes.
- Test your own code against a small example and an edge case before saying you are finished. Candidates who find their own bug score better than those whose bug the interviewer finds.
What interviewers are told to look for
Google's interviewers score across a small number of dimensions rather than on whether the problem was solved, which is why candidates who do not finish still pass and candidates who finish in silence sometimes do not. The dimensions that recur in public accounts are problem solving, coding quality, and communication - and the last one is not a tiebreaker, it is weighted.
Practically, that means a working solution written cleanly, with variables that say what they hold and the edge cases handled explicitly, scores above a terse optimal one. It also means that saying "I think this is O(n log n) because of the sort, and I could get it to O(n) with a hash map if memory is not a constraint" is worth real points even if you then keep the sort.
Timeline
Applications open in the late summer or early autumn of the preceding year, with interviews running through autumn and host matching extending into the winter and sometimes beyond. The full picture of how the cycle works - and what to do if you have missed it - is in the SWE internship recruiting timeline.
One honest caveat: processes change between hiring seasons, and the details above describe the shape rather than a guarantee. Treat anything your recruiter tells you as authoritative over anything written on the internet, including this page.
Where CoPilot Interview fits
Disclosure: we build an interview assistant, so treat this as a disclosed pitch. CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds, across coding and behavioral rounds, with a permanent free tier that needs no credit card. For a loop like this one, the preparation matters more than anything else - the follow-up questions reward understanding rather than recall.
Frequently asked questions
How many interviews are in Google's software engineering internship loop?
Typically two technical rounds of about 45 minutes each, usually virtual, with one or two problems per round in a shared editor. Passing them moves you to host matching rather than directly to an offer.
What is host matching at Google?
A second stage after the interviews where your profile is circulated to teams with intern seats and a host chooses you. It is a genuine stage with its own timeline, and candidates do pass the interviews without being matched, so it is worth treating as seriously as the interviews themselves.
What kind of questions does Google ask in internship interviews?
Data structures and algorithms: arrays, strings and hash maps, tree and graph traversal, recursion and backtracking, binary search, and entry-level dynamic programming. The characteristic element is follow-ups that change the constraints after you solve the first version.
When do Google internship applications open?
In the late summer or early autumn of the year before the internship, with interviews through autumn and host matching extending into winter. Treat what a recruiter tells you as authoritative, since timing shifts between hiring seasons.
Walk into the round with a second pair of eyes
CoPilot Interview is a native Windows and macOS app that puts suggested answers on your own screen in about four seconds, across coding, system design and behavioral rounds. The free tier is permanent: 15 minutes a day, no credit card.
Try it free