Taro Logo

Software Engineer Interview Experience

February 1, 2015
Positive ExperienceNo Offer

Process

The recruiter contacted me via email.

We set the time and date for a technical phone interview in the email.

The recruiter also sent a list of websites and great resources to review and to expect.

During the interview, the recruiter directly moved to the technical part.

The technical problem took about 45 minutes, and at the end, there was a Q&A where the interviewer answered any questions I had about the company in general.

Questions

Four Questions Asked:

  1. Find the longest palindrome in a string.
  2. What is a HashSet? What is the difference between HashSet and TreeSet?
  3. Given a List<x> and a function f: x -> y, convert the list to a map, i.e., Map<x, y>.
  4. What happens in the background (the whole procedure) when you type a URL until the page is displayed?

Was this helpful?

Interview Statistics

The following metrics were computed from 3,728 interview experiences for the Google Software Engineer role in United States.

Success Rate

12%
Pass Rate

Google's interview process for their Software Engineer roles in the United States is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive59%
Neutral29%
Negative12%

Candidates reported having very good feelings for Google's Software Engineer interview process in United States.

Google Work Experiences