Taro Logo

Database Engineer Interview Experience - United States

January 1, 2017
Negative ExperienceNo Offer

Process

The overall interview process was pretty good. The interviewer was very pleasant to talk to, and the questions were to the point. The sad part about the entire process was the HR recruiter who was assigned to me after the interview. No communication bridge was made after the interview. I expect that from some startups, but not from an established company like Google. It has been 20 days since the interview, and I have no feedback. Upon contacting them 10 days after the interview, I was told the interviewer was still working on the feedback and it would take time. However, upon asking again after another 10 days, there was no communication whatsoever.

Questions

Most of the questions were related to the DR process. Questions involved:

  • FTPing a file to multiple servers from one server by leveraging the network pipe completely.
  • Any two database wait events.
  • How would you debug a slow-running query?
  • What would you bring to the table?

Was this helpful?

Interview Statistics

The following metrics were computed from 2 interview experiences for the Google Database Engineer role in United States.

Success Rate

50%
Pass Rate

Google's interview process for their Database Engineer roles in the United States is fairly selective, failing a large portion of engineers who go through it.

Experience Rating

Positive50%
Neutral0%
Negative50%

Candidates reported having mixed feelings for Google's Database Engineer interview process in United States.

Google Work Experiences