If you have a Google account why should they still need to do an interview?
Apparently they are thinking about it (perhaps just a rumor): https://www.thesun.co.uk/tech/3332120/google-creates-jobsite...
Google: My interview experience
51–60 of 164 posts
Re: Google: My interview experience
#52Better than my interview experience. Sailed through the phone interview, went in person for the day long interview. Most were no problem except for one that took longer than it should have. And then... Nothing. Radio silence. No emails. No answered emails. I had ceased to exist. After that colossal waste of time, I decided to only work remote.
Hi, I work at Google. I am sorry for this. This should never happen. How long ago was this? I can try to follow up on your behalf.
Reading people's accounts of interviewing at Google, I would never apply, and I won't cash in on the recommendations I could get from some ex/Googlers I know. Reading the submission, look how many times the candidate has to "ping" people just to keep the ball rolling. In my mind, I'd end up working with a bunch of sycophants who are willing to do that sort of thing, the same sort of people who got a thrill out of the strategy involved in applying to Ivy Leagues. Google does some great work, but man do they carry a stench.
Re: Google: My interview experience
#53As always, remember that even technical interviews like this one have an incredible amount of random chance built into the hiring process. This is especially true at a big company like Google (where I work and do interviews). Do they happen to have positions open right now? Did you happen to get asked questions that clicked with you? Was the hiring committee feeling grouchy that day? Did you get an especially harsh i…
I wonder if google had to reinterview their existing employees, in a blind study... How many rounds of interviews before they eliminated most of their staff?
Once upon a time, a hiring committee was presented some feedbacks and had to come to a yes/no decision for some candidates. All them were rejected. It turned out that the feedbacks were of the hiring committee's members, from when they got hired.
Re: Google: My interview experience
#54Earlier quoted context omitted.
I never got any feedback from a Google onsite, is that new?
This should never ever happen. How long ago was this? I work at Google. I can try to follow up for you.
Are you sure about this? I believe for liability reasons no feedback should ever be given, aside from the generic "you were very good / very close" just to make people feel better about themselves.
Re: Google: My interview experience
#55I'm curious if the people giving the interviews have an incentive to be conservative with scoring. Maybe it looks bad when your score is the highest? As if you're lowering the bar? If true, I could see that contributing to how these interview stories play out (candidates thinking they did better than their no-hire outcome).
Scores are normalized so it doesn't matter. If you always give a low score, that score will count more after normalization. It would be interesting to know how they treat outliers: for example, if you give always scores 1-2.5 and then suddenly a 4.
Re: Google: My interview experience
#56Earlier quoted context omitted.
I never got any feedback from a Google onsite, is that new?
This should never ever happen. How long ago was this? I work at Google. I can try to follow up for you.
If you mean communication over the process, don't worry, I got the "regretfully decline to proceed"-type phone call afterwards.
What I meant is that I can't recall any feedback like "personable, but algorithms needs work" or "code too messy" or "couldn't answer domain questions" etc. Just a general "sorry, please try again later."
To be fair, this was a verbal conversation from 7 months ago, so it may be there was something like that but I was too preoccupied with the bad news to write it down.
Re: Google: My interview experience
#57Earlier quoted context omitted.
I wonder if google had to reinterview their existing employees, in a blind study... How many rounds of interviews before they eliminated most of their staff?
Once upon a time, a hiring committee was presented some feedbacks and had to come to a yes/no decision for some candidates. All them were rejected. It turned out that the feedbacks were of the hiring committee's members, from when they got hired.
Source?
Re: Google: My interview experience
#58Earlier quoted context omitted.
I wonder if google had to reinterview their existing employees, in a blind study... How many rounds of interviews before they eliminated most of their staff?
Once upon a time, a hiring committee was presented some feedbacks and had to come to a yes/no decision for some candidates. All them were rejected. It turned out that the feedbacks were of the hiring committee's members, from when they got hired.
I've heard this before, is there a source for this? It has all the hallmarks of an urban legend...
Re: Google: My interview experience
#59Earlier quoted context omitted.
Once upon a time, a hiring committee was presented some feedbacks and had to come to a yes/no decision for some candidates. All them were rejected. It turned out that the feedbacks were of the hiring committee's members, from when they got hired.
Source?
It was in this video but don't remember exactly when. https://youtu.be/r8RxkpUvxK0
Re: Google: My interview experience
#60Earlier quoted context omitted.
> I hadn't done anything with bits since college. No offense, but then the job probably was not right for you (which does not mean that you would not excel at other roles, of course). It then seems that the interview might have served is purpose just fine and saved both you and Google from being cast into an unfitting position.
I really wouldn't make that conclusion until you knew what job he was interviewing for. Firmware development? Sure, you might be right. iOS developer? Unlikely that low level bit manipulation is going to be a good indicator of his ability to succeed in that role. That's not to say its irrelevant, but, just not a quality indicator for that role in my opinion.
Maybe Google hires firmware developers, but I think they don't hire iOS developers. They hire "software engineers", and throw problems at them. (Or rather, these generic software engineers migrate toward problems that interest them in the long run.)
It prevents Google from having, say, more "iOS developers" than they need when they decide to concentrate on other products. We may debate the merit of this strategy, but as long as Google keeps this strategy, it makes sense to hire engineers who are willing to say "Well I haven't touched bits for a decade but let's see what we can do with them."