How to: Work at Google — Example Coding/Engineering Interview
Video Statistics and Information
Channel: undefined
Views: 5,802,779
Rating: 4.7301016 out of 5
Keywords: google, life at google, google jobs
Id: XKu_SEDAykw
Channel Id: undefined
Length: 24min 1sec (1441 seconds)
Published: Mon Nov 07 2016
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
Except that you're deathly nervous trying to remember all the tips you read in "Cracking the Coding Interview" and you're wondering why the hell they let you get this far...you definitely don't remember the efficiency of the algorithms, except for the really crappy ones like the nested for loop because you remember doing that shit in college. In the end it goes horribly and they tell you they'll call you back and you never hear from them until a month later when they send you an email saying that they're exploring other options at this time.
Except I would kill myself before the interview ended if that music never stopped playing in the background.
People think that these seems too easy, but I'm pretty for the most part they are analyzing how you approach the problem, and how you can vocalize your process. This guy does that very well.
Lots of obsession about the response here. I think the point is just to show they're not asking engineers about manhole covers or how many golf balls fit in a bus. These fake "Google interview questions" are so widespread they've even made it into business books.
Edit: Okay, clearly some Google employees ask these kinds of questions. But try a little Googling:
https://www.washingtonpost.com/news/on-leadership/wp/2016/03/29/companies-turn-to-quirky-interview-questions-even-after-google-says-they-dont-work/
http://abcnews.go.com/blogs/business/2013/06/google-skips-waste-of-time-brainteaser-interview-questions/
As someone who started out in Comp Sci and then switched majors, this still makes me feel very inferior as a human being. Family members keep approaching me with coding-related jobs, but doing this type of thing fills me with so much anxiety. I can't imaging it doing it on-the-spot for someone.
This kind of optimisation is very rare. Almost never seen in the places I work. Most developers don't have the time to optimise like this because most systems are never put under the kind of stress that Googles are. When you can just throw on some extra CPU's and solve the problem who cares.
I hate coding interviews like this, brings the worst out of a person. I prefer if they just give you a test to do at home, and tell you to return it to them the next day. That's what real coding is going to be like, you'll show your real skills.
All that just to hire a gardener?!
That guy wouldve been rejected btw (assuming google isnt poaching him from a unicorn or the big 4 or hes not an mit stanford grad). They expect this shit to be done in 15 minutes so they can move on to the next question. This industry has gone full retard in terms of interview expectations.
Source: my friends and i who have interviewed with them (some were accepted, what i said above isnt salt, its an unfortunate truth)
Edit: on second thought, this isnt even an in person question, this is a question they use for their phone screens, and you can be sure youll get some one who cant speak english like that lady. This might as well be marked as an ad