News for hackers. Stuff that matters.
Re:Google: 90% of our engineers use the software you wrote (... by joshstrange on Wednesday June 10, 2015 @05:10PM (#9695416)
To all of those saying ranting on twitter is the wrong move I couldn't disagree more. Twitter is often the ONLY tool that the average person can use to communicate and/or call out large companies on their actions. This is BS and should be made known. Homebrew is an amazing tool and I'd be falling over myself getting the offer papers in this guy's hands if he came to me looking for a job. The fact that google turned him away only further cements my opinion that google would be a terrible place to work.
Re:Google: 90% of our engineers use the software you wrote (... by philipwalton on Wednesday June 10, 2015 @07:53PM (#9696480)
My main complaint with the tweet is that it's almost certainly speculation.

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.

Re:Google: 90% of our engineers use the software you wrote (... by BinaryIdiot on Wednesday June 10, 2015 @08:38PM (#9696661)
> 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.

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.

Re:Google: 90% of our engineers use the software you wrote (... by philipwalton on Wednesday June 10, 2015 @09:54PM (#9696987)
The tweet starts out: "Google: 90% of our engineers...", which implies that this is information Google told him.
Re:Google: 90% of our engineers use the software you wrote (... by Retric on Thursday June 11, 2015 @12:11AM (#9697468)
Re:Google: 90% of our engineers use the software you wrote (... by BinaryIdiot on Thursday June 11, 2015 @12:04AM (#9697448)
OP was obviously being sarcastic to express his frustration.
Re:Google: 90% of our engineers use the software you wrote (... by Noctem on Wednesday June 10, 2015 @09:31PM (#9696898)
To your second point, there is an official Linux fork called Linuxbrew. http://brew.sh/linuxbrew/

Granted Linuxbrew isn't nearly as prevalent as Homebrew, but Macs are prevalent at Google.

Re:Google: 90% of our engineers use the software you wrote (... by austinjp on Thursday June 11, 2015 @09:32AM (#9699570)
Really? In the UK companies are legally obliged to reveal why a candidate did not get a job, if asked... in my understanding.
Re:Google: 90% of our engineers use the software you wrote (... by Anderkent on Thursday June 11, 2015 @12:11PM (#9700531)
I'm sceptical; I've heard this before but never managed to track down a source; I also don't know if you need some specific wording for this or if it's so vague as to be useful. Case in point: when I've failed my google interviews in London, I asked for the feedback, and got a reply saying something like "Sorry, we don't do detailed feedback. We weren't happy with your performance on the interviews". Which, duh, I got that from the being rejected part :P
Re:Google: 90% of our engineers use the software you wrote (... by mdpopescu on Saturday June 13, 2015 @08:43AM (#9710830)
Huh? I've been rejected by an UK company with just "you're obviously a very experienced programmer, but "we are not able to take your application any further at this time".

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.

Re:Google: 90% of our engineers use the software you wrote (... by austinjp on Thursday June 18, 2015 @03:36AM (#9737242)
Maybe I don't understand the legals fully. My experience comes from being on the hiring side. Our HR department were very keen that we kept detailed notes so that the decision not to hire could be justified in the case of a tribunal or suing situation. For what it's worth, it did make me question my motives and felt that it ensured I gave every candidate a fair shot.
Re:Google: 90% of our engineers use the software you wrote (... by GFischer on Thursday June 11, 2015 @12:32PM (#9700664)
They can offer non-answers :) ... in Germany they got very good writing "recommendation" letters that have some hidden hints:

http://www.goldbeck.com/hrblog/employee-references-germany-v...

Re:Google: 90% of our engineers use the software you wrote (... by joeldg on Wednesday June 10, 2015 @08:40PM (#9696672)
In my experience it goes exactly like this just about everywhere:

job: here is your macbook pro, welcome! you: <install homebrew>

Re:Google: 90% of our engineers use the software you wrote (... by 72deluxe on Thursday June 11, 2015 @05:03AM (#9698531)
I don't have it installed on my Macs - what am I missing? I write C++ daily on them.

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.

Re:Google: 90% of our engineers use the software you wrote (... by nextw33k on Thursday June 11, 2015 @09:01AM (#9699391)
brew is a package manager, I can install a set of applications and libraries that will be kept up to date with a simple command line. If your coding doesn't take you outside of what Apple provide then you are probably not missing anything.

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.

Re:Google: 90% of our engineers use the software you wrote (... by 72deluxe on Thursday June 11, 2015 @10:55AM (#9700065)
I use xcode and use wxWidgets, but I grab these manually and compile them myself. I also use the Android SDK and NDK, cppcheck cloc etc like you

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).

Re:Google: 90% of our engineers use the software you wrote (... by ascendantlogic on Thursday June 11, 2015 @11:57AM (#9700450)
Homebrew is really the default package manager. You don't need it, per se, but for the vast majority of people it'd be like trying to set up a Linux system without using apt-get or yum: an exercise in pain.
Re:Google: 90% of our engineers use the software you wrote (... by 72deluxe on Friday June 12, 2015 @04:46AM (#9704695)
That'll explain my early Debian experiences (installing from DVD and attempting to use dpkg exclusively) and my Slackware experiences then...
Re:Google: 90% of our engineers use the software you wrote (... by baakss on Wednesday June 10, 2015 @05:24PM (#9695550)
We don't have all the details. You might not hire the best computer programmer in the world if he was also a psychopath. Heck, you might skip on him even if he wasn't a good culture fit. I'm not saying this person is / was any of those things, but there's more to hiring than just talent.
Re:Google: 90% of our engineers use the software you wrote (... by sporkmonger on Thursday June 11, 2015 @10:20AM (#9699853)
There's also the committee factor. Google doesn't hire/no-hire based just on one person's opinion. If half your committee says, "90% of our engineers use his thing!" and the other half says, "But he can't code on a whiteboard!" then the committee is already kinda likely to take a pass due to lack of consensus. If there's any doubts at all on culture fit, which Google absolutely does care a great deal about, even more so. That said, when I was there, I interviewed someone who was essentially going to be my partner on something and everyone else (who weren't going to be working with this person) ranked the person poorly and I was the sole voice of (positive) dissent. I wasn't on the committee, so I don't know what their logic was, but the person was hired. And they were great. So it's not always even a majority opinion thing with the interviewers. In a nutshell, not only are we dealing with incomplete information here, we're dealing with VERY incomplete information.
Re:Google: 90% of our engineers use the software you wrote (... by justonepost on Wednesday June 10, 2015 @05:42PM (#9695701)
Yeah, the twitter rant was a little unnerving. Might not have anything to do with inverting the binary tree.
Re:Google: 90% of our engineers use the software you wrote (... by visarga on Thursday June 11, 2015 @01:52AM (#9697854)
He was there and that's what he felt it was the cause of his rejection. We haven't had the opportunity to witness his hiring process.
Re:Google: 90% of our engineers use the software you wrote (... by soup10 on Wednesday June 10, 2015 @07:51PM (#9696466)
That's not what happened at all. Google has an interview process that is designed to weed out false positives(incompetent people getting hired). Because this guy didn't have enough algorithmic knowledge he failed their filter. To work at the borg you must learn and play by the borgs rules!
Re:Google: 90% of our engineers use the software you wrote (... by vacri on Wednesday June 10, 2015 @06:21PM (#9696012)
Ranting on twitter is fucking awful. All it gives is nuance-free soundbites, and there are no 'lines to read between' due to it's brevity. Stuff gets taken the wrong way or out of context all the time.

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.

Re:Google: 90% of our engineers use the software you wrote (... by supergirl on Wednesday June 10, 2015 @05:15PM (#9695472)
maybe Homebrew is amazing, but Google can hire the best people in the world. that day they might've interviewed 10 people better than him who just didn't make a popular tool
Re:Google: 90% of our engineers use the software you wrote (... by leetNightshade on Wednesday June 10, 2015 @05:32PM (#9695621)
"that day they might've interviewed 10 people better than him who just didn't make a popular tool"

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.

Re:Google: 90% of our engineers use the software you wrote (... by supergirl on Wednesday June 10, 2015 @05:55PM (#9695819)
the tweet is made to trigger that discussion. but you can rephrase the tweet to something like: even though I made a popular tool, I didn't get a job at Google because I'm not good at other things they need. Google probably has a lot of factors counted into the final decision, including algorithm skills, other software engineering skills, human skills, contributions to open source projects. It's never 1 reason why you get rejected, it's the total score.
Re:Google: 90% of our engineers use the software you wrote (... by JamesBarney on Wednesday June 10, 2015 @06:44PM (#9696158)
Why do you think white boarding over the course of an several hours would be a better predictor of these traits than years of making very meaningful contributions to software?

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.

Re:Google: 90% of our engineers use the software you wrote (... by seiji on Wednesday June 10, 2015 @06:14PM (#9695961)
because I'm not good at other things they need.

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.

Re:Google: 90% of our engineers use the software you wrote (... by Terr_ on Wednesday June 10, 2015 @06:26PM (#9696047)
It's also aggravating when a Google recruiter "reaches out" to you and but won't (or can't) reveal any details at all about what role they're trying to fill.
Re:Google: 90% of our engineers use the software you wrote (... by supergirl on Wednesday June 10, 2015 @06:23PM (#9696028)
demonstrate under time constraints, lack of references, lack of iterative code/compiler/REPL feedback

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.

Re:Google: 90% of our engineers use the software you wrote (... by seiji on Wednesday June 10, 2015 @06:28PM (#9696066)
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.

Re:Google: 90% of our engineers use the software you wrote (... by sremani on Wednesday June 10, 2015 @06:16PM (#9695981)
Disagree, this is not some PR campaign of a corporate drone, a real person felt frustrated with the process of hiring in Google. Is it to instigate debate on HN, I doubt it. He is just venting out, that his body of work which is public is effectively ignored in favor of a pedantic exercise.
Re:Google: 90% of our engineers use the software you wrote (... by supergirl on Wednesday June 10, 2015 @06:28PM (#9696060)
How do you know it was ignored? It's possible it is one of the reasons why he even got this far.

Also how do you know he didn't fail a great number of other things they evaluate?

Re:Google: 90% of our engineers use the software you wrote (... by aaggarwal on Wednesday June 10, 2015 @06:15PM (#9695976)
I am speaking from personal experience here, 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. They don't even look at your resumes until all your 4 interviews are completed. However, selecting a candidate is a different matter, in that decision they might consider everything.
Re:Google: 90% of our engineers use the software you wrote (... by mvgoogler on Wednesday June 10, 2015 @07:04PM (#9696259)
Does your personal experience include actually being involved in the hiring process at Google?

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.

Re:Google: 90% of our engineers use the software you wrote (... by aaggarwal on Thursday June 11, 2015 @02:30AM (#9697980)
Yes, I was interviewed at Google last year. This was basically what happened. Sure, they have your resume, I am not sure if they read it throughly, the interviewer didn't even know my major until I told him at the end of the interview. While, they don't stop inteview and say you made mistake, it's competitive and it's not possible to hire you. But, you know at that moment that you are not getting hired. I guess, they need plenty of reasons to hire a candidate, but just one reason to reject. I am not complaining, it seems to work for Google very well.
Re:Google: 90% of our engineers use the software you wrote (... by toomuchtodo on Wednesday June 10, 2015 @05:38PM (#9695668)
> maybe Homebrew is amazing, but Google can hire the best people in the world.

Then why don't they? I wouldn't consider "the best people in the world" those that can pass an advanced CS class.

Re:Google: 90% of our engineers use the software you wrote (... by supergirl on Wednesday June 10, 2015 @05:46PM (#9695729)
so for you "best in the world" is not someone good at CS. similarly, for Google it appears best in the world is not someone that made a popular tool.
Re:Google: 90% of our engineers use the software you wrote (... by toomuchtodo on Wednesday June 10, 2015 @05:53PM (#9695794)
And so Google can continue to lose talent to competitors, or have potential hires go off to start their own startups they can then pay a premium for, while keeping "good enough" talent for existing initiatives.

I'm starting to realize why Google is absolutely terrible at any sort of customer-facing product.

Re:Google: 90% of our engineers use the software you wrote (... by supergirl on Wednesday June 10, 2015 @05:58PM (#9695839)
talent.. what is talent? they have a set of skills they look for. this guy doesn't have what they need. for you talent means to be the author of a popular tool, but for Google means more; means also boring stuff like being good at communicating, being good in a team, etc. who knows how many of these this guy failed
Re:Google: 90% of our engineers use the software you wrote (... by georgemcbay on Wednesday June 10, 2015 @07:20PM (#9696328)
Well how do you define "better"?

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.

Re:Google: 90% of our engineers use the software you wrote (... by supergirl on Wednesday June 10, 2015 @07:43PM (#9696424)
Well then I guess it's because Page/Hendrix were much more than expert guitarists. They were also good at composition, lyrics, showmanship, marketing, business. Those academic guitarists will make contributions to the guitar field but seems that you wouldn't value that alone and it's OK. You are free to have your opinion about whom to hire just as Google is. For the sake of the argument, you could imagine 100 reasons why Google wouldn't hire Jimi Hendrix. Even though he produced something very popular he lacks many things that Google wants: he's not respectful of other people so he's going to cause other people problems, he's doing hard drugs so he's unpredictable, good with guitar but not other instruments, and so on.
Re:Google: 90% of our engineers use the software you wrote (... by TheOtherHobbes on Wednesday June 10, 2015 @09:34PM (#9696916)
If Google keeps telling itself it only hires the very best guitarists, and it turns down someone like Hendrix - because he's "not a team player", or he doesn't know how to tap out 13/18 while improvising an Indian Harikhamboji raga, or for some other inane reason - then it isn't really interested in the best guitarists at all.

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.

Re:Google: 90% of our engineers use the software you wrote (... by colinmegill on Thursday June 11, 2015 @03:21AM (#9698150)
I think this is spot on. I have seen 30 person teams composed of 30 one dimensional people, and 3 person teams composed of 10 dimensional people. With few communication barriers and everyone thinking about everything all the time, I take the small tight team. It does depend on the project, though, because a) sometimes the problems can be parallelized and many people working is good and b) 10 dimensional people don't typically like boring problems.