Taro Logo

Engineering Interview Experience - San Jose, California

April 1, 2010
Positive ExperienceNo Offer

Process

After the recruiter's phone call with general organizational questions, I had a short technical phone interview.

The interviewer was 10 minutes late, so we only talked for 30-35 minutes. During that time, they were only able to ask me a few things: some questions about my previous experience, the most difficult bug I'd faced recently, and one technical question requiring coding in a shared document.

After that, they let me ask them something about Google. They answered one question and then finished the interview, leaving me no opportunity to find out everything I had planned.

I also had the feeling the interviewer was not interested in being there, as they didn't guide me through the resolution process and spoke very little. Their communication skills could also have been better; I had difficulty understanding their questions in Indian English and had to ask for repeats several times. Google should send better-skilled and more articulate English speakers for interviews, in my opinion.

I successfully resolved the technical coding question in two different ways (both time and memory efficient), commenting my thought process. However, I received a negative response from the recruiter within a week.

Questions

Write code to find out if two string words are anagrams.

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Google Engineering role in San Jose, California.

Success Rate

0%
Pass Rate

Google's interview process for their Engineering roles in San Jose, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Google's Engineering interview process in San Jose, California.

Google Work Experiences