InterviewLegend

Google Internship & New-Grad Interview: What to Expect

Alex Chen9 min readUpdated 557 real interview reports
In this lesson
  • Know how the intern and new-grad loop differs from the full-time SWE process
  • Understand why the online assessment carries more weight for students
  • See what the shortened loop tests and what it drops
  • Understand host matching, and why passing every interview is not yet an offer

The Google software engineer internship and new-grad interview is a shorter version of the full-time loop, front-loaded onto one gate: the online assessment. An intern takes a recruiter call, then the assessment, then two technical interviews, then team matching. A new grad adds a dedicated Googleyness round and a brief onsite. Neither gets a system design round. What neither drops is Googleyness, which is scored the same way it is for a senior hire.

Clear the assessment and the rest is lighter than what an experienced candidate walks through: fewer rounds, no design, and less weight on scope and impact. There is one catch specific to internships, though. Passing every interview still does not hand you an offer. An intern has to be matched to a host team, and some strong candidates never are.

The online assessment does the first cut

For students the assessment carries more of the decision than it does for anyone else, and it is really two tests in one sitting. Prepare it specifically rather than treating it as a warm-up, because it is the gate almost everything else depends on.

PartWhat it isHow it is scored
Coding assessmentOne or two data-structure and algorithm problems, roughly 60 to 90 minutes, on a platform like Codility or HackerRankRuns your code against hidden tests. Candidates report the cases are not always provided, so write your own before submitting
Google Hiring AssessmentA work-styles questionnaire, roughly 50 to 100 statements you rate on a scaleNot a coding test. It reads for the same traits the Googleyness round scores: comfort with ambiguity, a bias to action, doing right by users

On the coding half, arrays and strings, graphs, and trees dominate, with the occasional dynamic-programming problem. It is easy-to-medium difficulty, lighter than the full-time bar. The single most common mistake is spending the whole budget on the code and clicking through the work-styles questionnaire on autopilot. That questionnaire is not a formality. Answer it honestly, but consistently, because contradictory answers read as gaming it.

The shortened loop

Pass the assessment and the interviews themselves are short. An intern typically gets two technical rounds of 45 to 60 minutes. A new grad gets a 45-minute technical screen, often paired back-to-back with a 45-minute Googleyness round, then a brief onsite of two more coding rounds. Every round runs in a shared Google Doc with no IDE and no way to execute your code, so practice writing clean code in a plain text editor before you sit it.

The coding bar is medium, not brutal. What trips students up is the shape of the questions: interviewers tend to spin their own variation on a standard pattern rather than hand you a stock problem off a list. Drilling the patterns to reflex is what lets you recognize the variation for what it is. Start with Graphs & Grids, then Arrays, Strings & Hashing; What Google Tests ranks the full list by how often each pattern appears.

There is no system design round for interns or most new grads. Design is reserved for senior levels (L5 and up), on the reasoning that you are not expected to have architected a large system yet. Do not spend your prep there. The time is far better spent on coding patterns and two or three Googleyness stories.

Team matching, and why passing is not the finish line

After the interviews, an intern is matched to a host: the manager who owns the project you would work on over the summer. It happens through short fit calls, 30 to 60 minutes each, with managers who have open headcount. This is where the internship funnel differs most from the full-time process. Clearing the technical bar puts you in the pool. Being chosen by a host is what turns it into an offer.

The uncomfortable part: some candidates pass every round and still go unmatched, especially in a competitive cycle where interns compete against master's and PhD applicants for the same seats. You cannot fully control the match, but you can widen your odds. Keep your resume and project stories sharp for the fit calls, respond quickly, and stay flexible on team and location.

The Google angle
The highest-leverage move a student can make is to treat Googleyness as seriously as the code. A student's instinct is to grind LeetCode and coast the behavioral parts, which is exactly backwards for Google, where a behavioral red flag can sink an otherwise-clean loop. Prepare two or three STAR stories from projects, internships, or coursework, each ending on a concrete result, and answer the work-styles questionnaire in that same register. Then prepare the online assessment as its own event, because for you it is the event.

Timing and the application

Google recruits interns and new grads on a university cycle that opens early and fills on a rolling basis, so postings for a given year tend to go up well before it and close as seats fill rather than on a single deadline. Applying late means competing for fewer remaining spots. Apply as soon as postings open, use a referral if you have one, and have your assessment prep ready before you submit, because the online assessment can arrive within days of the application.

Common questions

How hard is it to get a Google internship?

The online assessment does most of the cutting. It pairs one or two coding problems, roughly 60 to 90 minutes on hidden tests, with a work-styles questionnaire that students often rush. Pass it and the two technical rounds sit at an easy-to-medium bar. The last filter is host matching, where some candidates clear every interview and still go unmatched. Postings open early and fill on a rolling basis, so apply as soon as they go up.

Does Google give interns an online assessment?

Yes. Nearly every intern and new-grad candidate takes one, and it is two tests together: a timed coding assessment of one or two problems, plus a separate work-styles questionnaire (the Google Hiring Assessment). It is the main gate, so prepare it specifically rather than as a warm-up.

Is there a system design round for interns or new grads?

No. System design is reserved for senior levels, L5 and up. Interns and new grads are tested on coding and Googleyness only, so put your time into patterns and behavioral stories, not architecture.

Do Google interns get a Googleyness interview?

New grads get a dedicated 45-minute Googleyness round. For interns, most of the behavioral read comes from the work-styles questionnaire in the assessment and from the team-matching calls. Either way, walk in with two or three STAR stories ready.

Key Takeaways

  • ✓The intern and new-grad loop is a lighter full-time process: recruiter call, online assessment, then two to four interviews. There is no system design round.
  • ✓The assessment does most of the filtering and is two tests in one: a coding OA (one or two problems on hidden tests) and a work-styles questionnaire. Prepare both.
  • ✓Passing the interviews is not an offer. Interns must be matched to a host team, and some strong candidates go unmatched, so keep your fit-call stories sharp.
  • ✓Googleyness is scored at every level. Bring two or three STAR stories, and apply early in the rolling university cycle.
Had your Google interview?Tell us what they asked. Reviewed before it goes in, never with your name.
Google interview guide

Know what Google asks before you walk in.

34 coding · 7 system design · 47 behavioral questions

Get Premium$49 a year · Cancel anytime
Or start freeNo card.

Get their questions first.

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.