Google Interview Questions & Reviews
Link
Twitter
Facebook
Digg
Salaries |
| |
Reviews |
| |
Interviews |
| |
Jobs |
| 21 - 30 of 112 Google Interviews | Sort by |
Software Engineer at Google
Posted Oct 25, 2009 — 0 of 1 people found this helpful
|
4.0
|
Overall Positive Experience
|
Interviewed and No Offer
|
Interviewed Jun 2009 in Mountain View, CA (took 2 months)
I got an e-mail from a recruiter at Google. Then, I talked to her on the phone about my skills and other stuff on my resume. I had a technical interview over the phone which I passed. I had a simple coding question and some questions on Java, which I said I was mostly familiar with.
My interview process took a long time because I had to go to a couple of conferences after I passed the phone interview.
For the on-site interview, I reviewed algorithms and common questions on java that I found online, which was really helpful since some of things I did not come across since I have been working on Ph.D. without much programming involved.
In general, the interviewers were friendly and not intimidating as some people might think because they are Google engineers. I thought I had done well specially on the algorithms part, but I did not get an offer. The recruiter was nice enough to give me a call and tell me personally instead of sending one of those generic e-mails "...we have no match for you..."
Interview Questions
Other Details
The interview consisted of a Phone Interview and a 1:1 Interview.
More Google Software Engineer Interviews
Helpful Interview?
Yes |
No
Add a Comment
Share:
Business Strategy at Google
Posted Oct 20, 2009
|
5.0
|
Overall Positive Experience
|
Received and Accepted Offer
|
Interviewed Jun 2008 in Mountain View, CA (took 3 months)
It's been a while, but experience varies widely depending on which position within the company one applies for. Some recruiters really don't get back to candidates for months... Very little feedback is offered in the interview process as well.
People are very nice and very fair, but the bar for getting in is very high and they look for extremely smart people who also demonstrate a very strong motivation to work for this company. If you weren't always at the top of your class you probably won't make it through - that's how high selectivity there is.
Negotiation Details
Offers are usually at set levels, with very little room left for negotiation.
Other Details
I got the interview through an Employee Referral and the interview consisted of a Phone Interview, a 1:1 Interview and a Background Check.
Helpful Interview?
Yes |
No
Add a Comment
Share:
Software Engineer at Google
Posted Oct 21, 2009 — 0 of 1 people found this helpful
|
2.0
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed Feb 2009 in Mountain View, CA (took a day)
I was emailed by a Google recruiter to assess my compatibility for a position in Software Engineering. The recruiter sent a list of questions via email, but the questions were mostly boilerplate -- some of which could have been readily answered with a cursory glance at my resume (which they already had). The better questions were of a "tell me about a time you..." format. I responded to the questions by email and got a canned "thanks" response, but heard nothing more and did not pursue it.
Interview Questions
Other Details
The interview consisted of a Personality Test.
More Google Software Engineer Interviews
Helpful Interview?
Yes |
No
Add a Comment
Share:
Associate Product Manager at Google
Posted Oct 15, 2009
|
3.0
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed Oct 2009 (took a day)
There were 2 phone interviews, mostly asking design questions.
1. Airports are inefficient. What would you do to improve them?
2. It is difficult to remember what you read, especially after many years. Contemplate how to address this.
3. If Google were to offer a TV commercial service, how would you implement this?
The interviewers were hard to read... I still have no idea what would have made stellar answers to these.
Interview Questions
Other Details
I got the interview through a Recruiter and the interview consisted of a Phone Interview.
More Google Associate Product Manager Interviews
Helpful Interview?
Yes |
No
Add a Comment
Share:
Product Manager at Google
Posted Oct 13, 2009
|
3.0
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed Jan 2009 in Mountain View, CA (took 3 months)
Lengthy interview process. I first had two phone screens, one with an extremely rude manager, who thought he was the smartest guy on earth. Next, they invited me on campus. HR was extremely friendly, but most of the six interviewers were anything but. Everyone (including those interviewing for product management roles) must interview with an engineer. Most often, these are young engineers from MIT/Stanford who think they are the smartest people walking the earth. To some, this may be stimulating, but for me this was quite a turn off. Google is a geek haven.
Interview Questions
Other Details
I got the interview through a College or University and the interview consisted of a Phone Interview and a 1:1 Interview.
More Google Product Manager Interviews
Helpful Interview?
Yes |
No
Add a Comment
Share:
System Availability at Google
Posted Oct 13, 2009
|
3.0
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed Jan 2009 in Mountain View, CA (took 1 week)
After initial recruiter phone interview, a technical interviewer informed me all hires at Google must have a technical background. Asked me basic stuff about Apache, HTTP, SSL, and general programming. Then asked me about basic Statistics (variance, std. dev., etc...), ideas on how to manage deployment of new code.
Interview Questions
Other Details
The interview consisted of a Phone Interview, a 1:1 Interview and an IQ/Intelligence Test.
Helpful Interview?
Yes |
No
Add a Comment
Share:
Software Development Engineer at Google
Posted Oct 14, 2009 — 0 of 1 people found this helpful
|
5.0
|
Overall Positive Experience
|
Interviewed and No Offer
|
Interviewed Jul 2009 in Mountain View, CA (took 2 months)
I spoke with two HR people, the first was local but didn't have any positions that fit me. She forwarded me on to an HR staffer at the Mountain View office which led into a phone interview with an engineer who was working on Chrome and O3D. It was pretty exciting to get to talk to engineers who are working on all these cool projects.
I guess I passed the phone interview because the next step was them flying me to Mountain View for an on-site interview. I didn't really blow them out of the water because I was rusty on a lot of stuff, so I heard back a week later with a report on where my weaknesses were, which was very helpful.
The HR staff were both very helpful, and the engineers that I interviewed with were more or less nice folk, some more friendly than others. None were hostile or intimidating. I really enjoyed getting to work through problems with real Google engineers.
Interview Questions
Other Details
I got the interview through an Employee Referral and the interview consisted of a Phone Interview, a 1:1 Interview and a Skills Test.
More Google Software Development Engineer Interviews
Helpful Interview?
Yes |
No
Add a Comment
Share:
Software Test Engineer at Google
Posted Oct 7, 2009
|
4.0
|
Overall Negative Experience
|
Interviewed and No Offer
|
Interviewed May 2007 in Mountain View, CA (took 2 days)
I heard that the interview process was tough to get into Google. Who knew that simply scheduling one would be just as daunting. For a basic phone screen, I was rescheduled 3x, and usually at the last minute. In fact for one of them, the interviewer forgot, and I was rescheduled.
The phone screen wasn't too hard, but they wanted to make sure that interviewers had a solid grasp of web technology and terms like URL (what it stands for, how it works), DNS, what HTTP stood for. While good questions, they had nothing to do w/ testing techniques.
Interview Questions
Other Details
I Applied Online and the interview consisted of a Phone Interview.
Helpful Interview?
Yes |
No
Add a Comment
Share:
Software Development Engineer In Test at Google
Posted Oct 1, 2009 — 1 of 1 people found this helpful
|
3.0
|
Overall Positive Experience
|
Interviewed and No Offer
|
Interviewed Sep 2009 in Kirkland, WA (took 1+ week)
1. I got a phone call from the recruiter who asked me a few questions about what I did in my present job.
2. Next the phone interview was scheduled for a week later.
The phone interview consisted of three parts:
a. Questions about my current job, stuff I worked on and projects I had participated in
b. What is my favorite programming language and what is the most advanced feature of the language that I had used.
c. Questions on multithreading, concurrency, locking. Simple question about race conditions, solutions to the usual concurrency problems. What is the difference between a mutex and a semaphore. Which one would I use to protect access to an increment operation. (i.e. i++)
d. A question on the 'Game of Nim' although it was worded differently.
Interview Questions
Other Details
I got the interview through an Employee Referral and the interview consisted of a Phone Interview, a 1:1 Interview and a Background Check.
Helpful Interview?
Yes |
No
Add a Comment
Share:
Associate Product Manager at Google
Posted Oct 2, 2009
|
4.0
|
Overall Neutral Experience
|
Interviewed and No Offer
|
Interviewed Jul 2009 in Mountain View, CA (took 3 weeks)
Received request for phone interview nearly six months after applying. Had a phone interview with a Post MBA product manager. The interview felt very rushed. Spent the majority of time talking about my favorite Google Product, a technology that excites you and how to value twitter. Received a thank you for applying email 1 week later.
Interview Questions
Other Details
The interview consisted of a Phone Interview.
More Google Associate Product Manager Interviews
Helpful Interview?
Yes |
No
Add a Comment
Share:
|
|
RSS Feed for Google Interviews |
