Taro Logo

Software Engineer Interview Experience

October 11, 2016
Positive ExperienceNo Offer

Process

First round Technical Telephone Screen:

Python coding challenge in a shared Google Doc.

Phone interview - 45-minute call with an engineer.

Two problems:

  • One warm-up.
  • Then a few minutes after for me to ask questions.

All in all, thoroughly enjoyable. It felt more like pair-programming with the interviewer than like an interview.

Questions

  1. Write a function that converts a dictionary to a JSON string.

Input: python d = {} d['a1'] = 1 d['a2'] = "str" d['a3'] = True d['a4'] = {...}

Output: json '{"a1":1,"a2":"str","a3","a4":{"b1":...}}'

  1. Write a function that determines if a list of integers is in the same order as a second list of integers.
  • Do not assume the first list is distinct/unique.
  • Do assume the second list is.

Input: python s1 = [6,4,2,8,9,6,2,2] s2 = [4,2,9]

Output:

True

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