Live data from Hacker News

Google's “Director of Engineering” Hiring Test

gwan.com

481–490 of 969 posts

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

#481
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.

These kind of comments is why I love this site. The guy was obviously 100% joking but the engineers in us are bound to reply nonetheless.

It reminds me of a classic Dilbert. https://goo.gl/images/7DhC9f

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

#482

I'm surprised when people are surprised that Google's interview process is obnoxious. That's pretty well established by this point, both by Google employees and others.

There's literally quite a few people in here, including Googlers, that can't believe Google asks these questions.

(I don't necessarily believe the interview went down as reported, but the questions and the interviewer using a sheet with approved answers definitely are genuine)

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

#483
post #270

Earlier quoted context omitted.

Yup, those are SRE questions, but the fact that Google didn't interview him for the position he applied for makes them out to be even bigger idiots than I had them pegged at for using SRE questions on a director role. Regardless, just having such a stupid process exposed reflects badly on Google. In my own experience, Google isn't even able to call at the scheduled time so, while not the worst interviewers ever, they…

From what I've heard, google intentionally screws with timing, who you will be speaking to, and other factors in order to try to understand how you deal with changes in circumstances.

A counterexample can't prove that that never happens, but I interviewed with Google this year and every interaction on the phone or in the in-person interviews began within 3 minutes of the agreed-upon time. So I have a hard time believing this is a general policy.

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

#484

On #9, is it 16-bit or 64-bit values? Sounds like you may have been answering a different question. Isn't the standard answer to use a 65536 entry lookup table? Edit: oh, are you reinterpreting the array of 10000 16-bit integers as 2500 64-bit integers? But then what operation do you use on each? Either way, if you find yourself arguing with the recruiter, it's probably a bad sign.

I thought the reason it was generally accepted that the 8-bit lookup table is optimal is because it can fit in the L1 cache.

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

#485
post #438
post #368

Earlier quoted context omitted.

So you're saying Google's recruiters don't tell what position they are interviewing for and that they found a 20+ years experienced engineering manager holding patents on computer networking under-qualified for an ordinary site maintenance position. Well, that sounds like a dumb recruitment process.

> they found a 20+ years experienced engineering manager holding patents on computer networking under-qualified for an ordinary site maintenance position. To be fair, I've interviewed people at previous companies that had patents and 15 years at IBM on their CV and completely failed even the most basic system / coding questions. (fizzbuzz style). There are a lot of people that read great on the CV but then it turns o…

Perhaps that suggests you're giving them the wrong interview.

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

#486
post #438
post #368

Earlier quoted context omitted.

So you're saying Google's recruiters don't tell what position they are interviewing for and that they found a 20+ years experienced engineering manager holding patents on computer networking under-qualified for an ordinary site maintenance position. Well, that sounds like a dumb recruitment process.

> they found a 20+ years experienced engineering manager holding patents on computer networking under-qualified for an ordinary site maintenance position. To be fair, I've interviewed people at previous companies that had patents and 15 years at IBM on their CV and completely failed even the most basic system / coding questions. (fizzbuzz style). There are a lot of people that read great on the CV but then it turns o…

Agreed.

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

#487
post #385
post #338

Earlier quoted context omitted.

How can you imagine Google being totally right here? The disconnect between the questions being asked and the interviewer's lack of knowledge made the interview a waste of time no matter WHAT role they are interviewing for. Take, for example, the sorting question. "Why is QuickSort the best sorting algorithm?" The answer being looked for was, "It has the best Big O." And this is wrong. Its average case is O(n log(n))…

I can imagine Google being totally right because I can imagine the interviewee not accurately remembering the conversation here. (I expect, for instance, that he did not write down the interview as it was happening.) In fact, conditioned on the assumption that Google is right that this guy's experience is better suited for SRE than director-level, it is pretty likely that he did not understand the questions being ask…

You are right that several of these questions could be due to his misunderstanding the questions asked at the time, answering the wrong one, and then remembering what he thought he was asked. But it is beyond my imagination to reconstruct a plausible conversation that could result in the one recorded without there being considerable ill will on both sides.

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

#488

FWIW: As a director of engineering for Google, who interviews other directors of engineering for Google, none of these are on or related to the "director of engineering" interview guidelines or sheets. These are bog standard SWE-SRE questions (particularly, SRE) at some companies, so my guess is he was really being evaluated for a normal SWE-SRE position. IE maybe he applied to a position labeled director of engineer…

Just FWIW, about 5 years ago someone also contacted me for a google interview. The questions were very similar, so I'm not surprised. I don't know what's going on behind the scenes, but after a few mins I didn't took the call serious any more and in the end after 30 min it felt more like a way too long prank call.

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

#489

I'm amazed he knew things in such detail. I mean who would know just how long a MAC address is? Or what the actual SYN/ACK etc tcp flags are? You just need to know what they're used for, and if you need the specifics, you'll find out with a single search. He seemed to know that as well though. Kernighan for bit twiddling algos, that kind of thing. It's a bit strange to have someone non-technical interviewing a techie…

Medical Recruiter: "What are mitochondria?" Applicant Doctor: "They're double membrane-bound organelles found in all eukaryotic organisms, commonly between 0.75 and 3μm in diameter, that generate most of the cell's supply of adenosine triphosphate" Recruiter: "No. They are the powerhouse of the cell".

Perfect analogy. And you just jogged a bad interview memory - "thanks a lot."
Post reply on HN