Earlier quoted context omitted.
And they can do all of that just because everybody still wants to work at Google. Let's say the have 100 applicants for a position, out of which 10 are qualified for it. Then they can still screw 9 of them and hire the one person that for one reason or the other had the luck of interviewing with the right people and talking to the right recruiters.
Many people don't want to work at Google. Yes, they can fill their spots, but the reality is that hiring bullshit means that over time their candidate pool progressively filters to "the people who will put up with bullshit", and while it takes years to filter through, in the end you up becoming Microsoft. There was a time when Microsoft was the bee's knees and was the elusive dream employer. Then they started various…
A Wretched Google Interview Experience
291–300 of 359 posts
Re: A Wretched Google Interview Experience
#292Earlier quoted context omitted.
> As for the calculus interview, that sounds like fair game. PMs are supposed to have some PM interviews and some SWE interviews, and math is a perfectly acceptable area to ask SWE candidates I upvoted you because it's not fair to down-vote people who are on topic, but you're not correct when you assume that of all things calculus (!?) should have anything to do with hiring a PM. I honestly fail to see how solving so…
managing a bunch of programmers The OP says his friend was interviewing for "product manager", which is not that. Product management is basically coming up with ideas for new products and seeing them through to the end. That includes helping design the actual computer program, which is why they ask software engineering questions. (There are a ton of jobs called "PM", but they're all very different. None of them manag…
Re: A Wretched Google Interview Experience
#293An acquaintance of mine applied for a product management job, did two interviews in NY that went fine, then was flown out to MTV for a series of interviews. When this person got there, two of the people they were supposed to meet with were traveling on business and hadn't notified the recruiter. A third was out sick. The supposed-to-be fourth, now first interview walked into the room and said, "Look, I don't have any…
It's not any better if you get hired. Google recruiters will tell you whatever you want to hear, including things that are not necessarily true. I was assured that a minor issue in my background would not be an issue multiple times (I have email proving this), then Google hired me and let me work for more than two months. I got comfortable, I moved to Mountain View, began real honest work and set about making an impa…
Re: A Wretched Google Interview Experience
#294An acquaintance of mine applied for a product management job, did two interviews in NY that went fine, then was flown out to MTV for a series of interviews. When this person got there, two of the people they were supposed to meet with were traveling on business and hadn't notified the recruiter. A third was out sick. The supposed-to-be fourth, now first interview walked into the room and said, "Look, I don't have any…
I've interviewed at and worked for a number very very large companies before, and none of them have been as disrespectful at interviewing and hiring as Google sounds from these stories. I'm not defending this practice at all, but I think I can understand it. It sounds like the typical problems involved in scheduling 10 people to all perform together at once. Nobody can prevent people from getting sick. Going out of t…
I'm not defending this practice at all, but I think I can understand it. It sounds like the typical problems involved in scheduling 10 people to all perform together at once. Nobody can prevent people from getting sick. Going out of town and missing an interview is pretty flaky, but it happens.
Except it doesn't at other companies. Or if it does, it's corrected before a candidate shows up at the door. In other words, you value a candidate's time. I interview people all the time, and if I have business travel come up, I look at my calendar and make damn sure I don't have any interviews when I'll be out of the office (and if I do, I reschedule. If an emergency happens, I get someone equally qualified to cover). Heck, I even send personal apology emails when I have to reschedule phone screens.
You know why? Because it's polite.
It's certainly human nature to be bitter about someone fucking up an important day for you, but ultimately, bitterness gets you nothing. It's no problem if you want to complain to your friends or on HN, but why not come back for the second try?
Again, I can't ascribe motive to someone else's actions, but it's because it's disrespectful. It's not like, btw, google was apologetic, or said, "You know what, let's do these next round of interviews over video chat", or "We're going to make this up to you in some way". If I recall these events correctly, it was, "Sorry, you didn't get the job because you didn't do well in your interviews". Then a few hours later, "Oh no, wait, you have to do them all again". That's just disrespectful.
Your friend could have had another free trip to Mountain View to actually be interviewed properly, and maybe get the job he wanted.
Who wants a free trip to mountain view? Bear in mind, this isn't a college grad who is just excited to get to go to california, this was someone who was already an experienced product management executive in a leadership position at a middling-size startup. Going out to mountain view messes with their schedule and their work, and again, it's disrespectful.
As for the calculus interview, that sounds like fair game. PMs are supposed to have some PM interviews and some SWE interviews, and math is a perfectly acceptable area to ask SWE candidates.
If the questions had been in the technical area in question, even from a software engineering perspective, I'd be in agreement. But arbitrary knowledge of calculus seems unkind and unnecessary. That's clearly a style preference, though, as you say.
The point I'm generally trying to make isn't about my friend's experience exactly, it's just to add on to what many many people here have said: that google as an organization may treat employees very very well, but treat candidates very poorly.
Coordinating interviews really isn't that hard. Tracking candidate progress isn't that hard. And when you as an employer screw up, picking up the phone and making an apology isn't that hard. Failing at all three shows a fundamental lack of respect for the people you're hiring. You can't just say, "The system is broken".
Re: A Wretched Google Interview Experience
#295Earlier quoted context omitted.
My recruiter failed to call me at the scheduled time. Twice. I wasn't too terribly dismayed, as I was already home at the time anyway, but that put me in a pretty bad mood to begin with. I failed the first phone interview spectacularly because he asked about data structures and estimating powers of two, and I haven't done any of that after 4 years in the industry. I guess fair enough; if that's what they expect of th…
My experience of those interviews that ask CS or “puzzle” questions is that they are sincerely trying to determine that you are capable of dealing with inherently novel/theoretic problems or problems you've never seen before. Unfortunately this notion is misguided because the problems aren't real problems, and the context in which the problems are solved is entirely different to what it would be in the actual workpla…
Re: A Wretched Google Interview Experience
#296Ok, the RealTimeCounter problem got me thinking. It's a great question. It seems very simple, but as the author notes even PhD's are stumped by it. Here my solution. One very important purpose it serves is to see how well you can identify problems in algorithms. Probably I'm guessing it's not even important that you get it perfect, just that you can recognize and talk through the challenges. One challenge relates to…
var second = 100000000
, minute = second * 60
, hour = minute * 60
, day = hour * 24
, current = 0
, lastIncrement = 0
, increments = [];
function increment(){
current = timer.time();
increments.push( current - lastIncrement );
lastIncrement = current;
}
function getCountInLastSecond(){
var copy = increments.slice()
, total = 0
, count = 0;
while( ( total Re: A Wretched Google Interview Experience
#297Earlier quoted context omitted.
I think this is being relatively unfair in assessment. Google hasn't had a hit product in a while? Search and Ads are dominant. Android is the #1 mobile smartphone OS with 80% of the market. Chrome is now the #1 browser. Google Maps is the #1 mapping application. Gmail is now #1 in active users. G+ now has 190 million active posters now monthly now (Twitter only has 110 million active posters) YouTube is the top vide…
I would consider Maps, Gmail, and G+, CRUD applications. What does it take to not be a CRUD application? I'm not sure. I think every web-based application in which enormous amounts of data are stored and manipulated qualifies as a CRUD application, even if they involve lots of intelligence and batch processing on the backend. Many of them are CRUD with a Big "R," as they mostly involve consuming data. Maybe my defini…
CRUD to mean has traditionally meant traditional database applications, CREATE, UPDATE, and DELETE, after all come from SQL keywords. These apps are primarily table oriented.
Google Maps isn't even close to being a CRUD application in the traditional sense. How many CRUD applications have you worked on that used Octrees? And why does "web based" make something CRUD? Is a native Android app that does SQL RPC calls and just manipulates a typical entity-relationship database quality as CRUD?
Anyway, back to hit products. Google Now was released only 1 year ago and is a new hit product. How many new hits per year do you want? ;-)
Also keep in mind that Google has moved from launching lots of tiny apps with separate branding, to unifying their various platforms and implementing things as features across app. For example, the neural network based image search is a really a service that appears inside of Drive, G+, etc, just like Hangouts appear in multiple apps, as well as Google Local data.
The general thrust is to get away from launching an array of dozens or hundreds of sites, and to make stuff just "work" within the apps you use already.
Re: A Wretched Google Interview Experience
#298Earlier quoted context omitted.
I think this is being relatively unfair in assessment. Google hasn't had a hit product in a while? Search and Ads are dominant. Android is the #1 mobile smartphone OS with 80% of the market. Chrome is now the #1 browser. Google Maps is the #1 mapping application. Gmail is now #1 in active users. G+ now has 190 million active posters now monthly now (Twitter only has 110 million active posters) YouTube is the top vide…
Actually, I'm not sure if you are rather not contradicting yourself as most of the more technical projects - or the core technologies used by them, for example, webkit for chrome, dalvik for android and so on - (which the parent was presumably talking about) - correct me if I'm wrong here - were not developed at Google but at other (i.e. the developers of these projects, typically, didn't come through the Google's re…
These days, most software isn't developed in a vacuum. WebKit was a fork of KHTML. Does Apple get no credit for the changes made to it?
Google Maps and Google Earth were acquisitions as well, but the state of those products when they were acquired compared to where they are not is completely different.
Re: A Wretched Google Interview Experience
#299Earlier quoted context omitted.
My recruiter failed to call me at the scheduled time. Twice. I wasn't too terribly dismayed, as I was already home at the time anyway, but that put me in a pretty bad mood to begin with. I failed the first phone interview spectacularly because he asked about data structures and estimating powers of two, and I haven't done any of that after 4 years in the industry. I guess fair enough; if that's what they expect of th…
In my experience, my Google recruiter simply did not respond to emails. The only way to get in touch with him was to email HR. Scheduling the first round of interviews? Email HR, wait for the recruiter to email me. Scheduling the second round? HR. Finding out results - you guessed it, emailing HR to get the recruiter to call me. This stretched my process to two whole months.
I was head-hunted by them initially. Had a casual phone interview within the week. Then scheduled and re-scheduled a technical interview (their fault, three more weeks). Then two weeks later I had another casual phone interview. Then waited two weeks for the on-site six-interview bonanza. I finished those 4th thru 9th interview two weeks ago, and recruiter just told me yesterday to wait for the hiring committee to give a decision in another week.
Re: A Wretched Google Interview Experience
#300Earlier quoted context omitted.
If you're at liberty to share : did your acquaintances also disclose the incidents during the hiring process, only to be terminated randomly once employed? If so, that is utterly appalling. Bad enough that it should happen once (to the parent), but repeated incidents would point to some gross organizational dysfunction.
I asked the HR Manager point blank if Google made a mistake here, waiting two months to act upon information available to them before they extended me an offer. She countered that I was the one who had made the mistake in 2007. I served my probation sentence and am beyond tired of being punished for the same thing. If hiring people are reading this and understanding just that last sentence that I typed, then I'm happ…