1) Most companies (for legal reasons) don't tell candidates why they weren't offered a job. Maybe it was because of the binary tree question, but maybe it was for some other reason.
2) Homebrew is a Mac-only product, so the likelihood that 90% of Googlers use homebrew is very low. Moreover, Google does not track the software its employees download onto their laptops, so there's no way they would even know the percentage.
So when I was declined at Google I knew people who worked for Google. One looked up my profile in whatever system they used and the other simply asked the interviewer why. OP may have done the same but as you say it's unclear either way but knowing is still possible.
> 2) Homebrew is a Mac-only product, so the likelihood that 90% of Googlers use homebrew is very low. Moreover, Google does not track the software its employees download onto their laptops, so there's no way they would even know the percentage.
Most of the people I know at Google use Macs so I don't see why not. I don't know what the majority of them use but a good chunk at least do.
As far as tracking he could simply be tracking it himself and comparing his results of known Google IPs to employee counts. Not as accurate but might give a rough estimation. He may have further analytics based on data collected (if collected) by each machine.
job: here is your macbook pro, welcome! you: <install homebrew>
EDIT: Seriously, what am I missing that I'd need as a developer? My dayjob is on a Mac Pro writing desktop software and my hobby at night is on a MacBook Pro doing the same; it's on neither machine.
Personally I have the Android SDK and NDK, QtCreator, Qt5, cppcheck, cloc, mongodb, node, wine and others. If you are not using a variety of 3rd party tools to produce/automate your work then you probably don't need to worry.
Having all those kept up to date for me saves me so much time.
I didn't realise that they could be kept up to date with homebrew?? Is that the case?
Last time I looked at MacPorts (and perhaps homebrew) I saw it as a porting of BDS/GNU tools to OSX and therefore making the OS more Linuxy to my mind. I wanted a clean break from Linuxland when I moved to OSX, hence I removed MacPorts etc. (Additionally the ported software all ran under X and not Quartz so it didn't really fit in; also, the fetched packages and compiled systems were massive in size which I didn't appreciate on a laptop that shared space with recorded audio and video etc. so space was at a premium).
Granted Linuxbrew isn't nearly as prevalent as Homebrew, but Macs are prevalent at Google.
http://www.goldbeck.com/hrblog/employee-references-germany-v...
I did get a code review out of it though, and it did point out a few real issues, so I'm ok with it.
One of the reasons why it's so powerful is because it gives lazy journalists a stream of easy reaction quotes. When else in the history of journalism has there ever been a private company that was so heavily promoted, regardless of the media source? And even then, the react quotes are poor quality, single-sentence shit.
This rant on twitter is absolutely meaningless unless you have a heap of context to go with it. And because twitter is popular, it's dumbing down public discourse along with it.
/rant, that I couldn't have fit in 140 characters.
Are you judging this on their ability to invert a binary tree? People here are ranting about having a problem with interview practices not representing whether or not you are good at your job. That's presumably (IMO) why the tweet was posted.
It's not that you're not _good_ at it, but you're not able to demonstrate under time constraints, lack of references, lack of iterative code/compiler/REPL feedback, and while being stared down by someone whose default mindset is "why am I wasting my time on this person?"
It's never 1 reason why you get rejected, it's the total score.
That depends on how far down the interview process you are. Often they'll cut you off at a phone interview if you stumble. Sometimes they'll cut in-person interviews short if they think you're not worth it. So, they don't always get a "total score" to judge against. It's often just summary judgement off subjective feelings.
well that is the interview. for you being good means to know how to invert a binary tree if you have access to a compiler and internet, but for Google it means to know it off the top of your head. they could let you have access to compiler and then make the questions much more difficult. which one is better? I don't know. first one takes less time at least.
Often they'll cut you off at a phone interview if you stumble
I'd guess that's because they have so many condidates to pick from.
Exactly. It's the Big City Dating Problem. There are so many people to pick from, nobody wants to compromise to build a relationship. Just leave at the slightest sign of something not being 100% what you want and on to the next one since there are 20,000 other acceptable people within walking distance.
if you have access to a compiler and internet
It's not exactly that, but you often don't realize how many micro-checks or micro-confirmations you do while programming. In the absence of any "is this okay so far?" feedback, you're left second guessing yourself and reading your solution redundantly to check for any errors your daily automation would catch immediately by default.
Because in my personal experience - as both an interviewer and a hiring committee member - what you said is completely wrong.
> they don't count a lot of factors while rejecting a candidate, you make one > mistake on their particular set of questions, you are out.
Completely false. I have personally seen many people get hired despite doing poorly in an interview or making mistakes.
The hiring committee looks at all of the available information - resume, recommendations, and interview feedback when making a decision. There is no "one-thing" that will make or break a candidate.
> They don't even look at your resumes until all your 4 interviews are completed
I have no idea where you are getting this from. All interviewers receive the candidate's resume prior to the interview. I always review the resume's to get a sense of what the candidate has done so I can ask appropriate questions.
Also how do you know he didn't fail a great number of other things they evaluate?
It seems to me like creating and managing a repository of more than 4800 contributors is a much better signal of a candidates software engineering, communication, and human skills than a couple of people's opinion of a couple of hours of white boarding.
Then why don't they? I wouldn't consider "the best people in the world" those that can pass an advanced CS class.
I'm starting to realize why Google is absolutely terrible at any sort of customer-facing product.
Esteemed schools of music probably produce dozens of guitarists "better" (in any way you would measure it academically) than Jimmy Page or Jimi Hendrix per year who go on to a life of producing nothing of lasting worth.
I'll take the guy/girl who has actually proved they can produce something useful every time over someone who is "better" but hasn't.
It's the difference between an holistic view of talent, and an academic and rather narcissistic insistence on specific limited social signals that are believed to correlate with intelligence.
And this really matters in practical ways. A lot of talented devs will be reading this story and wondering if they really want to work for Google. Negative PR like this is incredibly damaging. Consider the opposite - if Google could say "Yes, the Homebrew guy works for us." How much value do you think that would have had?
Long term, the really smart and inventive people start to stay away. And then you get something that seems to be happening to Google already - declining product quality, a poorer user experience, and diminished reputation. You know - Google's record of hits recently hasn't been that great?
So anyone who thinks Google is fine because it still has thousands of applicants is missing the point. Instead of being the kind of place where Hendrix plays, it's in danger of becoming the kind of place where there are a lot of people with a lot of solid but uncreative technical chops, and no one is making cool and interesting music any more.