Taro Logo

Developer Programs Engineer Interview Experience - Mountain View, California

August 1, 2009
Positive ExperienceNo Offer

Process

The phone screens were conducted by engineers from different areas working in similar roles. Each screen lasted about 50 minutes.

Each interview started with time for me to ask as many questions as I wanted about Google and the role I was applying for. After I finished those questions, I was asked to describe my experience, interests, and accomplishments. Finally, we concluded with about 20 minutes of technical questions that seemed to draw primarily on the programming languages I had listed in my application.

A few examples included:

  • How would you implement garbage collection in C?
  • Describe one of the software engineering design patterns.
  • How would you extend Array in JavaScript so that it could add all the values stored in an array? (An exploration of Object prototypes, demonstrating the level of sophistication with the language.)

The engineers were very eloquent, not at all pretentious, and highly knowledgeable. It didn't work out, but I learned a lot from the interviews and was exceedingly impressed by the engineers there. The role wasn't a great fit for me anyway, and I intend to try again in the future.

Questions

How would you extend Array in JavaScript so that it could add all the values stored in an array?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Google Developer Programs Engineer role in Mountain View, California.

Success Rate

0%
Pass Rate

Google's interview process for their Developer Programs Engineer roles in Mountain View, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Google's Developer Programs Engineer interview process in Mountain View, California.

Google Work Experiences