Live data from Hacker News

Google's “Director of Engineering” Hiring Test

gwan.com

851–860 of 969 posts

Re: Google's “Director of Engineering” Hiring Test

#851
post #161

Google doesn't ask these types of trivia questions. I don't believe that you were talking to a person from Google one bit. Everything documented about their hiring practices and anecdotal evidence from people gone through their interview process is that you talk with a real engineer and write code for your interview.

It does. I have already said it in another thread, but I have been asked the exact same questions at Google (applying for a Java developer job)

Several other people have come out and said the same.

Re: Google's “Director of Engineering” Hiring Test

#852

Earlier quoted context omitted.

You seem to be confusing "I have a smug twitter-sized sound-bite response" for "I have a worthwhile counter-argument". It's a common failing these days, but you should probably look into getting it fixed. That said, yes, Google's hiring process is questionable. The Web is full of horror stories from obviously-qualified people who Google passed on, often very early in the process when no engineer had talked to them, a…

I can expand beyond 140 characters if you like. The OP claimed that in the past ten years, as a result of their hiring practices, Google's product output quality has noticeably declined, presumably as compared to the search product on which their name was made, and gmail, which they launched in 2004. And it's easy and fashionable to knock Google because maps is not as good as you remember it used to be, or because th…

>I can expand beyond 140 characters if you like. The OP claimed that in the past ten years, as a result of their hiring practices, Google's product output quality has noticeably declined, presumably as compared to the search product on which their name was made, and gmail, which they launched in 2004. And it's easy and fashionable to knock Google because maps is not as good as you remember it used to be, or because they shut down reader, or because plus didn't manage to unseat facebook.

I don't necessarily blame them for plus (facebook was clearly a marketing success, not a technology success), but maps' decline isn't anybody else's fault. It has declined in quality and that is plainly an engineering failure not a product failure.

>Well, in 2006 Google was a 10 billion dollar search and ad company with a fledgeling email business without a revenue model, who had just bought youtube. In 2008 they shipped a mobile phone operating system. That's now a thirty billion dollar business which has been built up through talent within google. They undermined Microsoft's office monopoly with an online office suite (okay, some acquisitions underpinning that).

Well, yes. Acquisitions underpinned all of that success.

>I've got no particular reason to stand up for Google, they're quite big enough to look after themselves, but the idea that their product flops in the last decade outweigh those product successes, and can be held up as evidence that there is something deeply rotten in their hiring model, seems to be cherrypicking to me. 70% mobile OS share, 70% search share, and 50% of global online ad revenue... that's a pretty good kind of mediocrity.

All predicated upon outside purchases or the original self-reinforcing search monopoly developed before 2004.

What's worse is that they've often used their search monopoly to try to break into other markets (flights, shopping, etc. - plenty of stuff like this got preferential SERPs treatment) and failed because what they released was crap. That is, they failed even with a huge home ground advantage - the kind of monopoly advantage that let Microsoft make IE6 (IE6!) the industry standard for years and got them slapped by the DoJ couldn't even be put to good use by Google.

I'm not denying that they have some good engineers but the idea that they're the creme de la creme of the industry with the best hiring process is way way off base.

Re: Google's “Director of Engineering” Hiring Test

#853
post #96

To be charitable here: is it possible that this person did not work for Google? Historically, I've known third-party recruiters play fast and loose with their affiliation with the company they're recruiting for. This literally could have been any recruiter in the Valley trying to feed candidates to Google.

No, I have been asked the same questions by a person with @google.com email address that clearly said he was a psychologist and not a technical guy. His Linked in info at the time was Google Recruiter.

Re: Google's “Director of Engineering” Hiring Test

#854

Earlier quoted context omitted.

>Judging an entire recruitment process based on one side of a story from a person who's clearly upset about an interview, It's not just this guy. There have been others: https://twitter.com/mxcl/status/608682016205344768 There's another measure I use to measure the quality of their hiring process. The output. Namely the track record of products Google has developed in house in the last 10 years. I've also heard a few…

Yep, those engineers they took on in the last ten years must suck, they've only managed to develop technologies that grew Google's annual revenue from 10 billion dollars in 2006 to 75 billion in 2015. That's the kind of track record that has to make you question the hiring process, right?

And Comcast has some of the best customer service and engineering because they don't seem to be losing any customers.

Right?

Re: Google's “Director of Engineering” Hiring Test

#855

Earlier quoted context omitted.

When the in house engineers come out with products like Wave and Glass while things like Maps and Android are purchased you have to wonder.

I think you're neglecting the continuous improvement of successful projects, which take quite a bit of engineering effort. Was it software quality that killed Wave and Glass, or was it more of the market not wanting either of those things? (To digress, it seems like both of those products came too early. Do you think that wearable computers will _never_ exist? And Slack seems to be the Wave-like thing that the market…

Funny you should mention that. I was just using maps and thinking "this is worse than it used to be".

From what I've heard from insiders, the adwords code base is an enormous mess. Not surprising for a product that old perhaps, but this points to their engineering practises being about as mediocre as the industry average.

I don't honestly know why people want slack. It seems to just be in vogue - one of those weird network effect things. It doesn't seem to have anything to do with their feature-set or engineering quality because it's not noticeably better than, say, hipchat.

>To digress, it seems like both of those products came too early. Do you think that wearable computers will _never_ exist?

They already exist.

Re: Google's “Director of Engineering” Hiring Test

#858
> Recruiter: that's not the answer I have on my sheet of paper.

That's not an interview. That's a waste of your time and an insult to your intelligence.

This reminds me of the time Google rejected the creator of Homebrew because he couldn't invert a binary tree: https://twitter.com/mxcl/status/608682016205344768

Re: Google's “Director of Engineering” Hiring Test

#859
post #306

Earlier quoted context omitted.

Not sure how much you're kidding, but... that's true for a subtractive colour system, where you start with a white sheet of paper (i.e. reflects every wavelength) and subtract colours (filter out wavelengths) by painting over the paper with crayons. For an additive colour system, where you start with a black monitor screen, and you add wavelengths, the primaries are RGB.

...and, strictly speaking, the subtractive colors that closest match the typical human eye are cyan, magenta, and yellow -- the "CMY" of CMYK printer inks. Using red, yellow, and blue as subtractive colors gets you a big enough gamut for elementary school color mixing, but it won't give you as big a range of colors as CMY.

… and we just add K because a separate black ink is cheaper and more precise.

Re: Google's “Director of Engineering” Hiring Test

#860

Earlier quoted context omitted.

I'd hope it's not too typical, since four out of the ten official answers are wrong, and even one of the questions manages to be wrong. (Specifically, the "why is quicksort the best?" is just completely ridiculous.) It's one thing to blindly apply a simple questionnaire without thinking about the answers that come back, and yet another thing to do it with a questionnaire that's doesn't even get stuff right.

I was asked the "what syscall returns an inode?" question (and agree with DannyBee that this is extremely similar to my successful SRE screen) and I answered stat() without the clarification because I understood what the screener was doing and the parameters in which she was operating. That context on how phone screens work is missing from this transcript, but it's also unfair to expect that sort of context from a ca…

No software can perform better than the hardware allows it to. End of argument. Even if you make 100% optimized ASM tailored to the hardware and workload, and you can still kill it hard with enough requests. For all we know he hosts the website on a free tier of whatever to show how well it performs. It being down doesn't tell anything useful other than the current workload exceeds its capabilities.
Post reply on HN