Taro Logo

Software Engineer Interview Experience

September 18, 2013
Neutral ExperienceNo Offer

Process

One interviewer posed a question quite vaguely. He asked about algorithms and their time complexity for an array list that is partially sorted.

I asked for clarification, "Do you mean there are several subarrays which are sorted, but the overall array is not?" He confirmed.

So, I offered an answer of O(log k), where k is the number of subarrays, as a typical case of merge sort.

However, what he actually meant was that he was expecting bubble sort, and his question was about individual elements not being in the correct order, rather than partially sorted subarrays. I finally understood this when we moved to his larger coding question instead of a screening task.

I was a little disappointed that he did not have the patience to discuss and clarify better. He seemed very hurried during the interview, spoke rapidly, and couldn't wait to leave the room. I recall he even forgot to shake hands before departing, which confused me.

Questions

What is the total number of different valid parentheses? I mean, not to code it out, but to calculate the number.

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