Taro Logo

Release Engineer Interview Experience - Mountain View, California

February 1, 2018
Positive ExperienceGot Offer

Process

I was contacted after applying, as I had gone through the interview process before.

I completed one HR phone screen, one online coding interview, and five on-site interviews.

The on-site interviews included:

  • 3 coding interviews
  • 1 Linux knowledge interview
  • 1 branching strategies interview

The difficulty of the interviews was based on a self-assessment I provided.

Questions

NDA, so I can't talk specifics, but in general:

  • Coding questions around random numbers, string manipulation, grid search, and stream processing.
  • Coding questions to re-implement two common Linux utilities.
  • Long discussion about how to design and roll out a distributed build and test system.
  • Discussion about branching strategy. For me, it was Git, as I know it best. Questions focused on choices made and their tradeoffs, handling unusual situations (i.e., bugs after release, security patches, hotfixes, etc.), and difficulties presented by the model as a whole.
  • Other questions about bash and Linux fundamentals.

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Google Release Engineer role in Mountain View, California.

Success Rate

25%
Pass Rate

Google's interview process for their Release Engineer roles in Mountain View, California is very selective, failing most engineers who go through it.

Experience Rating

Positive25%
Neutral25%
Negative50%

Candidates reported having very negative feelings for Google's Release Engineer interview process in Mountain View, California.

Google Work Experiences