14 ms·
This was posted previously, in October 2016: https://news.ycombinator.com/item?id=12701272 https://news.ycombinator.com/item?id=12701272 An actual Google dire
by geofft 9y ago
This was posted previously, in October 2016:
https://news.ycombinator.com/item?id=12701272 https://news.ycombinator.com/item?id=12701272
An actual Google director of engineering pointed out that these are individual-contributor SWE/SRE questions (and I can attest I got very similar questions as a new college grad).
As I commented previously: "Reading more closely, it sounds like they are not interviewing him for a director of engineering position; it just sounds like he thinks his current role, CEO-who-writes-code of a very small software company (http://www.gwan.com/about http://www.gwan.com/about), qualifies him for a director-of-engineering-level position. He's probably being interviewed for an SRE team lead or thereabouts."
Also, a ton of this conversation makes a lot more sense if you make the assumption that the interviewee is misremembering the questions: https://news.ycombinator.com/item?id=12702726 https://news.ycombinator.com/item?id=12702726 (Which is a very gentle assumption, if the interviewee also mistakenly thought they were being interviewed to be a director of engineering.)
In which case, screening out someone with an inflated sense of their own experience and overconfidence that the stupid person on the other end of the phone is stupid is exactly what this process is supposed to do.
- DannyBee 9y agoand i just commented the same thing i did then, because i completely didn't notice this was from 2016 :)
- waisbrot 9y ago> He's probably being interviewed for an SRE team lead or thereabouts OK, but incorrect/inflexible quizzing about tech questions is inappropriate full stop. If this was an interview for SWE summer intern it'd be a badly-run interview. > exactly what this process is supposed to do You can't ensure that there will be no hurt feelings ever, but ideally the candidates you fail don't go around talking about how poor your interview process is. > make the assumption that the interviewee is misremembering the questions In your post you imagine slight differences that might make the questions more reasonable. I think the main problem here is the responses to the answers. For a non-engineer quizzing someone, the response to an answer should be "OK" and then you note down the answer and show your notes to an engineer at the end. This solves both the "that's not what's written on my sheet" problem and also allows the interviewee to form a more nuanced impression of your recruiting process.
- Voloskaya 9y ago> The response to an answer should be "OK" and then you note down the answer and show your notes to an engineer at the end. This kinds of defeat the purpose of the screening interview though doesn't it? The point is to not disturb an engineer when 99% of the people that are being screened are unqualified.
- fjsolwmv 9y agoIf your engineering managers can't be disturbed than maybe you don't have time to hire.
- Voloskaya 9y agoTo be fair we are talking about Google, not the local shop at the corner of the streets. Each recruiter must do tens of screening a day, and they have tens of recruiters assigned to each department, we are not talking about reviewing 2 applications a day during coffee break.
- tomhallett 9y agoNot entirely: the answers written down by the recuiters can be reviewed in batch, while the phone screen has a lot more overhead.
- geofft 9y ago> incorrect/inflexible quizzing about tech questions is inappropriate full stop I don't disagree with this, but (to the best of my memory - this was in 2011), when this initial phone screen was presented to me, it was presented with some amount of "We want to figure out what you're good at so we're having the right people interview you for the right roles." Which is to say, I suspect that him failing out halfway through this screen was because of combativeness / personality, not phone screen performance per se. > You can't ensure that there will be no hurt feelings ever, but ideally the candidates you fail don't go around talking about how poor your interview process is. I think I disagree with this though - there are certain people who are going to be predisposed to complaining about things that don't go their way, and you want to make sure you fail them as early as possible. At a company small enough that its strength is the CEO's coding abilities, a curmudgeon with significant raw technical talent can do very well. At a Google-sized company they just can't.
- dvt 9y agoNot sure why this is so highly rated when it's so blatantly wrong. There are literally dozens of director-level interview samples online (as well as people discussing these on Quora and other platforms) and they all start with the recruiter screening process. To say that only SREs get screened is incredibly misleading.
- geofft 9y agoCan you post a link to one of these? The first Quora answer I find says, "First interview was on the phone with a recruiter. The questions were typical recruiter screening. Nothing hard or detailed. Questions about background and feeling out my interest." I definitely believe there's a recruiter screening process - I would just be surprised if it's the same screening process they give to new college grads, with the same slate of questions. (Even if you're going to give them technical questions, at least give them harder technical questions!) I obviously have no real information having not interviewed for a director-level position, I'm just stating that these questions seem like the same slate I got as a college grad.
- dvt 9y agoI read a similar screen a few years ago (some guy with a math PhD, also applying for a director position at GOOG). I'll try to find the blog post. Even if the screens are different, I'm not sure they're that different.
- aje403 9y agoDoesn’t sound like the interviewee has an inflated sense of worth from what’s written and it sounds like the interviewer cheated off someone to get his degree
- aje403 9y agoWhat did I fart or something
- draw_down 9y agoThat actually doesn’t make a difference because the replies to his answers are basically absurd. Nobody should go through this.
- jiveturkey 9y agoHa! I remember this from back then. Interview process aside, did you see the guy's technology page? Which process has led to TrustLeap's technology? Instead of trying to add something on the top of a multi-layered construction done by many different persons in a period of time exceeding 30 years, TWD has resolved the problem from scratch in a few months. riiiiight
- pjc50 9y agoFrom their linkedin? > TrustLeap, the security division of TWD Industries AG (founded in 1998), protects digital assets with cryptanalytically unbreakable technology (safe against unlimited computing power as it is proven mathematically that no key leaks can be exploited). Riiight.
- jiveturkey 9y agoit is actually possible. one time pad
- geofft 9y agoKey leaks of a one-time pad can be exploited.
- crdoconnor 9y ago>Also, a ton of this conversation makes a lot more sense if you make the assumption that the interviewee is misremembering the questions. Which is a very gentle assumption. No, that's a pretty insulting and disturbingly koolaid flavored presumption. This conversation makes sense to me because of the number of people who have commented that they ended up being unwittingly considered for position that they did not apply for and did not actually even necessarily want. There's at least two in the comments section here and I know two more personally (one of whom is a very talented director of HR, ironically enough). I actually even said this to that director of engineering's comment you mentioned two years ago. He neglected to respond.
- geofft 9y agoI admit that this is certainly possible (Google recruiters wildly underleveling people, at least relative to their expectations if not their actual qualifications, and not clarifying this before passing the candidate onto other recruiters). If it's happening, it's a very different problem (no less real of a problem, though) and process fixes at this stage wouldn't help. Also, this interview performance should have been enough to disqualify this candidate for the role he envisioned, too. If only because, if he was actually intending on applying to be a director of engineering, the right answer to question 3 is something like "I think there's been some sort of mistake."
- crdoconnor 9y agoIt's not only possible it's likely if they are setting general hiring quotas for their recruiters. And, they almost certainly are setting quotas because they're currently being sued by one of their own recruiters over their quota policy. >Also, this interview performance should have been enough to disqualify this candidate They neither qualify him nor disqualify him. Correctly or near correctly answered trivia questions tell you almost nothing about a candidate other than that they're probably a software engineer of some kind.
- geofft 9y ago> They neither qualify him nor disqualify him. Correctly or near correctly answered trivia questions tell you almost nothing about a candidate other than that they're probably a software engineer of some kind. Please read the entire sentence you quoted halfway - by "interview performance" I don't mean the correctness of the answers, I mean his a) expectation that UNIX trivia quizzes are a normal part of a director-level interview (and that it's not more likely that there was a miscommunication in scheduling) and b) attitude.
- guilt 9y agoYeah, try discrediting the article than fix your mistakes. Real mature, Google.
- geofft 9y ago... Sorry, are you accusing me of working for Google? My identity is very public, I don't.
- guilt 9y agoThen you're most likely trolling everyone, by commenting that you know more about their processes than most outsiders do. So stop right there and run back into your PR cave.
- geofft 9y agoI do. I've interviewed twice and gotten offers twice (and declined twice). That's what I said in my post. I'm claiming no greater (but no less) knowledge than having gone through the interview process.
- guilt 9y agoAre you implying that because you went through a couple of good interviews with them, and because one director who works at Google said that they don't hire this way, it doesn't happen? That's the worst logic ever. I'm blaming Google for doing this, and you take it to imply that I said you work at Google? Maybe you didn't accept those offers from Google. It still doesn't mean those things didn't happen at Google - and it is extremely shameful that you resort to defending them. Congratulations, what you have done is just free PR for Google. I'd rather listen to everyone else than you.
- dang 9y agoYou crossed into personal attack in this subthread. We ban accounts that do that, so could you please (re-)read https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html and not do that again?
- trisimix 9y agoAssuming he didnt lie about the exchange of words, this guy could be a homeless person make believing hes getting hired as ceo of google and this interview would still be an affront to proper advancement. You cannot possibly justify making a quiz that asks about kill in unix and doesnt accept SIGKILL ~literally kill with SIGTERM the default. If you are looking for the default level (15) you should specify. If this interview actually happened the way this guy says it did, Google is making terrible mistakes. I know first semester 2 year networking degree students that would have scored higher than this guy. Seriously people should be appalled at the inadequacy of that interview. Respect lost.
- deleted 9y ago[deleted]
- nyanotech 9y agoI had a phone screen recently, and got asked some of the questions on this post. However, rather than that sigterm question, I got "What signal does the linux kill command emit by default?", (with the answer obviously being sigterm (I totally blanked out and got it wrong though :P)). Anyway, I strongly suspect they're just misremembering that question.
- geofft 9y ago> Assuming he didnt lie about the exchange of words If it's not clear: I strongly believe he lied. (I don't think he intentionally lied, as in deliberately twisted what the interviewer said to make them look bad: I think he genuinely misheard the questions because understanding questions accurately when asked by someone he considers inferior is not his strength, and then incorrectly reported them, which is still lying.) There are lots of people on the internet (including in the prior thread, including my own memory in the prior thread which I have now completely forgotten) who have reported that the kill question is about default kill command signal and not SIGKILL. It's certainly theoretically possible that the interviewer mis-spoke, but it's very hard to make that sort of mistake if you don't understand the questions you're asking (which is what he's alleging) because you wouldn't know enough to coherently phrase that version of the question.
- SilasX 9y ago>Also, a ton of this conversation makes a lot more sense if you make the assumption that the interviewee is misremembering the questions But (per [1]) then what would be the charitable mis-remembering of the recruiter saying "that's not the answer I have on my sheet of paper." If it were someone technically competent, that would never be the response; it would be a technical explanation of the error. The most likely scenario is that a non-technical person is being expected to gauge technical answers. Incidentally, someone on that thread [2] suggested making a meme of that, where the interviewer regards an answer as wrong, despite being very good, because it's "not what they have". Example from my experience: Interviewer: "What would be the run time if you did it this way [explanation]." Me: "Oh, wow, that's a pretty clever approach! In that case, it wouldn't even depend on the input size. Then it would only be limited by IO." Interviewer: "Wrong. It's constant." [1] https://news.ycombinator.com/item?id=16932260 https://news.ycombinator.com/item?id=16932260 [2] https://news.ycombinator.com/item?id=12701625 https://news.ycombinator.com/item?id=12701625
- killaken2000 9y agoIt's not the derivative of distance vs time that matters but the integral of acceleration.
- geofft 9y ago> The most likely scenario is that a non-technical person is being expected to gauge technical answers. I'm not disagreeing with this - this certainly appears to be the case. But I think a qualified technical person should be able to understand the question that the non-technical person is asking and respond in a useful way. Although, yes, if they immediately respond with "Wrong, it's <keyword>", it's hard to do that. But I feel like a good interviewer (good is orthogonal to technical!) is likely to say "OK, so what is the runtime?", and "constant" and "O(1)" should both be on their list of keywords. My charitable mis-remembering would be that the transcript here skipped these sorts of prompts, or that the interviewer was actually upset at the interviewee's demeanor/attitude already and wanted to cut the interview short by that point and was just trying to finish their block of questions. (Which I think is legitimate. As a technical interviewer, if you start condescending to me during the interview, I'm much less likely to give you the benefit of the doubt and help you along with Socratic hints.)
- fwdpropaganda 9y ago> In which case, screening out someone with an inflated sense of their own experience and overconfidence that the stupid person on the other end of the phone is stupid is exactly what this process is supposed to do. This is obviously an excuse for how shitty the interviewer is. If you want to rule out people with a inflated sense of their own experience, the way you do that does NOT involve telling them they're wrong when they're obviously right ("that's not the answer I have on my sheet of paper").
- geofft 9y agoAgain, my claim is the interviewer did not say exactly that and this man with an inflated sense of his own qualifications is retelling the story in a way that's favorable to him. All available evidence points to him either mishearing or mis-transcribing the question, which was actually "What is the signal sent by the kill command."
- fwdpropaganda 9y agoWhat evidence is there available that points to him mishearing?
- geofft 9y agoAs I and others have said a few times on this thread and on 2016's thread, there are a huge number of sources of people saying "I got the same question" and "The question was 'What is the signal sent by the kill command.'" So there are two possibilities: 1. This particular interviewer actually said "What is the name of the KILL signal," despite other interviewers regularly saying the question correctly. The entire thesis of this article is that the interviewer does not understand UNIX and is reading pre-written questions from a piece of paper, so that's an extremely unlikely mistake for the interviewer to make. 2. He misheard the question.
- socrates666 9y agoAt some point an inflated sense of experience is necessary to succeed in starting your own company. You have to literally believe you are capable of having a real impact. Jeff Bezos, Elon Musk, Bill Gates, etc. All were told at one point "you don't have the necessary experience for that." Or "are you fucking crazy?" Or something meant to challenge their experience. The hard realization is that none of them had the experience...but boy did they sure earn it. Point is: arrogance isn't the curse you might think it is.
- cfadvan 9y agoThere are a handful of sociopathic people who reach those heights, while most of the rest do not. Mistaking arrogance for an active ingredient in success is probably a mistake likely to lead you down a bad road. Ruthlessness, arrogance, greed might be things you need to be a high level founder, banker, CEO or politician, but most people with those traits are abject failures. You need to be smart, and very lucky as well, and even without arrogance smart and lucky should pay off.
- geekbird 9y agoWhereas I think the screener had an overinflated sense of both his knowledge, importance and the "rightness" of the answers that he expected. The questions were narrow, and the right/wrong on the answers was oversimplistic and more suited to a freshman computing college test, not the working world. The guy answered him with more nuance and detail, but he arrogantly told the guy to "learn more about...", when it's pretty obvious that the appicant knew more than the screener.