Taro Logo

Software Engineer Interview Experience

January 1, 2015
Negative ExperienceNo Offer

Process

A recruiter reached out to me and set up a technical phone screening. That screening went well, and I received a second phone screening.

For the second one, however, I couldn't understand my interviewer's accent. I tried asking him to repeat himself many times, but it didn't help. In the end, I performed poorly because I simply had no idea what he was asking of me. There were times that I wasn't even sure if he was talking about the code he wanted me to write or about my resume.

Additionally, he asked me for qualifications that, if he'd read my resume, it would have been clear that was not my area of expertise. I'm mostly qualified for OO-programming at a high level, and he was asking me about computer architecture.

I emailed my recruiter right after the second interview, explaining my situation politely. A week later, she called to tell me they rejected me. When I asked if she'd gotten my email, she seemed confused, and I'm not entirely sure she paid it much mind.

I'm not saying I deserved to get the job, but I certainly didn't deserve to be ruled out because I couldn't understand my interviewer's accent.

Questions

Did I take Computer Architecture in college?

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