Google Software Engineer - Internship interview questions
based on 823 ratings - Updated Jul 6, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
64%
Applied online
Applied online
16%
Employee Referral
Employee Referral
11%
Campus Recruiting
Campus Recruiting
8%
Recruiter
Recruiter
1%
Other
Other
Interview search
823 interviews
Viewing 561 - 565 of 823 Interviews
Google interviews FAQs
Software Engineer - Internship applicants have rated the interview process at Google with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 61.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer - Internship roles take an average of 105 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Google overall takes an average of 44 days.
Common stages of the interview process at Google as a Software Engineer - Internship according to 3 Glassdoor interviews include:
Skills test: 50%
Phone interview: 25%
One on one interview: 25%
Here are the most commonly searched roles for interview reports -
I took a shot coding assessment then was notified that 2 phone interviews would be next.
Phone interviews involved technical coding problems. Interviewers were kind and helpful.
Responses were fairly quick after interviews, however the whole process took about 2 months.
I applied through an employee referral. The process took 4 months. I interviewed at Google (San Francisco, CA) in Nov 2018
Interview
In terms of the difficulty, what you find online gives you a pretty good idea of what you will need to do to prepare. I found that the process was incredibly slow until I had other offers on the table. After telling them about the other offers it was sped up a little, but mostly I was just being strung along.
I first spoke to a recruiter, was given an automated coding test, then after I passed I was connected with a different recruiter. The recruiter asked a few questions, then set up two harder coding interviews where I was matched with two different Google engineers and asked to "whiteboard" on a shared google doc. I've been told after those two, normally there is a third before the application packet is sent to the first hiring committee. I, however, only wound up doing those two interviews. After the hiring committee, you are sent to "host matching" where you wait in limbo for a while. Your packet is in the bottom of the pile when you are first sent to host matching, so it's very likely you will be waiting for a few weeks before your recruiter contacts you to interview for a team. After a few interviews, you rank your preferences and they do the same. If you get a match, your packet gets sent to another hiring committee and if you pass, some VP reviews it and signs your contract.
They claim to not care about grades, but they really do.
Was very intimidating as you would expect. Not very friendly and it was hard to show your personality through the phone. I would say be confident, but do not expect to answer every single question correctly. It really is all about the interviewer you get.
Interview questions [1]
Question 1
Not technically allowed to say but wasnt expecting question about functions built into a language and I was asked one so be prepared for that