←back to thread

1764 points fatihky | 9 comments | | HN request time: 1.242s | source | bottom
Show context
DannyBee ◴[] No.12701869[source]
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 engineering, but they decided to interview him for a different level/job instead.

But it's super-strange even then (i've literally reviewed thousands of hiring packets, phone screens, etc, and this is ... out there. I'm not as familiar with SRE hiring practices, admittedly, though i've reviewed enough SRE candidates to know what kind of questions they ask).

As for the answers themselves, i always take "transcripts" of interviews (or anything else) with a grain of salt, as there are always two sides to every story.

Particularly, when one side presents something that makes the other side look like a blithering idiot, the likelihood it's 100% accurate is, historically, "not great".

replies(28): >>12702181 #>>12702207 #>>12702219 #>>12702265 #>>12702346 #>>12702460 #>>12702555 #>>12702650 #>>12702692 #>>12702698 #>>12702714 #>>12702888 #>>12702998 #>>12703034 #>>12703135 #>>12703156 #>>12703184 #>>12703554 #>>12703778 #>>12704177 #>>12704657 #>>12705201 #>>12705560 #>>12705982 #>>12706518 #>>12707763 #>>12708151 #>>12714459 #
falsedan ◴[] No.12703554[source]
This looks like a typical pre-interview recruiter phone screen… they're looking for shibboleths that identify the candidate as a genuine computer person who took CS 101, and exclude candidates who spam every job with bogus CVs. I'd start every candidate with this screen, unless I personally knew them & was familiar with their technical ability.

  > none of these are on or related to the "director of engineering" interview guidelines or sheets
They'd be internal to recruiting, so you wouldn't see them unless you were heavily involved (doing interviews and recruiting trips isn't being heavily involved). They're for any recruiter to use to quickly eliminate bogus applicants.

  > Particularly, when one side presents something that makes the other side look like a blithering idiot, the
  > likelihood it's 100% accurate is, historically, "not great".
You can just outright call him a liar… I'd expect this to be a fairly accurate report. It looks like the recruiter misused the screen; instead of eliminating obviously bogus candidates, they used it to eliminate a candidate who may or may not get an offer (and thus a commission). They should have proceeded to the technical phone screen stage. If the guideline on the recruiter screening is: drop anyone with <100% correct, then I think that's silly.
replies(4): >>12703642 #>>12704245 #>>12706142 #>>12707139 #
1. Klockan ◴[] No.12707139[source]
> They'd be internal to recruiting

I managed to find them and I don't work in recruiting, they are for SRE pre-screens. The guy misunderstood most of the questions which is why he failed and then worded them incorrectly on his blog, it wasn't the fault of the questions or the interviewer.

replies(3): >>12707291 #>>12707398 #>>12708729 #
2. ZoFreX ◴[] No.12707291[source]
That's a big claim. Can you share some of the actual wording of the questions?
replies(1): >>12707462 #
3. muse900 ◴[] No.12707398[source]
The recruiter misunderstood the answers and or he is not qualified to ask those questions. Usually when you ask someone something that is not literal as in "what is 1+1?" You can't expect them to be literal. Questions like: Why Quicksort is the best sorting method? Guy gave very good answer showing that he has perspective and he is able to make a valid argument. The recruiter on the other hand just read the paper and completely disregarded the fact that the person he is trying to recruit is a valid candidate.

Also at the end the recruiters attitude aweful. Like what is that, he was reading answers from a paper, couldn't make valid arguments back to the candidate and at the end turns and says to the candidate "sorry my paper says you don't know this and that, and goodbye?"

replies(1): >>12707416 #
4. Klockan ◴[] No.12707416[source]
No, I meant that the interviewee misunderstood the questions/answers given by the recruiter and thus misrepresented them when he wrote the blogpost. Since he couldn't even get the questions right I highly doubt that he gave a correct representation of the recruiters attitude as well.
replies(1): >>12707647 #
5. Klockan ◴[] No.12707462[source]
If you work at Google you can find them by searching for it.
replies(1): >>12707491 #
6. dgacmu ◴[] No.12707491{3}[source]
Maybe not such a good idea to post an internal link? :)
7. silentmars ◴[] No.12707647{3}[source]
Which of the following seems more likely?

A recruiter who was already giving the guy the wrong interview, and whose job revolves essentially around HR and sales, made mistakes in asking a series of technical questions.

An expert with decades of relevant technical experience misunderstands and confuses basic networking and system topics.

replies(1): >>12712868 #
8. plandis ◴[] No.12708729[source]
Do you have proof of this?
9. Klockan ◴[] No.12712868{4}[source]
Which of the following seems more likely?

A person fails to read a question verbatim.

A person who has been the "smartest person in the room" for decades has an inflated view of his fluency on a topic and makes mistakes in his favor when he tries to reconstruct the questions from memory.