Google Intern As Software Engineer interview questions
based on 253 ratings - Updated May 22, 2026
Averageinterview difficulty
Very positiveinterview experience
How others got an interview
62%
Applied online
Applied online
13%
Employee Referral
Employee Referral
13%
Campus Recruiting
Campus Recruiting
10%
Recruiter
Recruiter
1%
Other
Other
1%
In Person
In Person
1%
Staffing Agency
Staffing Agency
Interview search
253 interviews
Viewing 201 - 205 of 253 Interviews
Google interviews FAQs
Intern As Software Engineer 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 100% positive. To compare, the company-average is 68.7% positive. This is according to Glassdoor user ratings.
Here are the most commonly searched roles for interview reports -
I applied online. The process took 4 weeks. I interviewed at Google (Mountain View, CA) in Dec 2012
Interview
They ask most straightforward questions. I don't encounter those complicated and tricky ones out there. Basically, they care a great deal about code quality. And I believe they also design the questions according to your background. So don't panic if there are things you don't know.
I applied online. The process took 2 weeks. I interviewed at Google in Jan 2013
Interview
I applied online where I submitted my CV and was contacted after a day. I was working during that time, so my two phone interviews were scheduled on the same day and the recruiter was really helpful in making sure I can make the time. The phone interviews were 15 minutes apart and the first one had a lot of small questions that required no coding, but rather collaboration on how I might do things as well as questions about data structures. On one of the questions I did not entirely understand what I was asked and the interviewer explained what was expected. The second interview was a single coding exercise. I had to write a solution to a given problem and after I wrote it, I had to explain the complexity of my solution. After that I was asked to improve my algorithm so that it runs faster. The interviewer did not require the code to be compilable, but to show knowledge of the language and the solution. Off the top of my head I did not remember the exact way of doing I/O with files in Java, but that was not a problem. After the interviews I was contacted the following day and the recruiter informed me that I am continuing to the next stage where they search for a project for me. The project was found in a couple of days and I had a phone conversation with the team manager who asked me about my previous experience with some technologies and my availability for the needed dates. After that I was given my offer in another couple of days. Through all the experience the recruiter made sure I was informed of what is coming next and what I need to expect.
Interview questions [1]
Question 1
The most difficult part was to improve my solution in the second interview, which was not hard by itself, but when put on the spot it is harder to think of another way to solve it.
Applied on line and got response within 10 minutes. After discussed with my recruiter I set up my 2 phone-interview for 1 month later. The first interviewer is really nice, kept saying "that's great!" But the second one is cold all the time. I guess that's the one I screwed up. Got reply from Google after two weeks of my phone interview
Interview questions [1]
Question 1
One system analysis question regarding to Google book