16 ms·
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 k
by lordnacho 10y ago
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. You end up with stupid discussions like the one about Quicksort. If you point out qs is one of several things with the same big-O, you'll probably also get it "wrong". But the real problem is that a guy who is just reading off a sheet can't give any form of nuanced feedback. Was the guy blagging the sort algo question? Did he know if in detail? Does he know what the current state of research on that area is? There's no way to know that if your guy is just a recruiter, but I'm sure even a relatively junior coder would be able to tell if someone was just doing technical word salad.
I wonder what would happen if ordinary people recruited for medical doctor jobs? Would you be comfortable rejecting a guy who'd been in medical school for 10 years based on his not knowing what the "funny bone" is? Wouldn't you tell your boss that you felt a bit out of that league? It's amazing you can get someone to do this without them going red in the face.
- drewg123 10y agoIt tends to be incredibly helpful to know details like the length of a mac address and what tcp flags mean what if you're looking at an unformatted memory dump. One example of how this can be handy is when doing low-level NIC bring up, I've read PCIe TLPs from a logic analyzer to correlate them to network traffic.
- tptacek 10y agoI knew all these answers too, because I was a developer in the 1990s. There is absolutely no purpose to knowing off the top of your head how long an ethernet address is, or even what system call will retrieve an inode (his bickering over stat() "filling in" rather than "returning" was bogus, for what it's worth). The top Google search result for each of these questions has the answer. Knowing these things isn't part of being a practicing programmer; knowing how to find out is.
- mox1 10y agoThe question was what function "returns" an inode. Those functions return a error code, you pass in a stat structure and the function populates that structure. He was saying (correctly), that they don't return (in the classic C sense) the inode. They return an error code. To me that is a big difference... int lstat(const char path, struct stat buf); vs stat* lstat(const char *path); 2 completely different functions.
- edanm 10y agoThis strikes me as an entirely trivial point, the meaning of the question was pretty clear. It wasn't "what is the literal return value". Many APIs will return error codes, and people still talk about them as "returning" certain values colloquially. Of course, if the OP's answer would've been "it returns an error code :) but I assume you're talking about..." I would think that's fine. Btw, that is the only thing I really disagreed with OP on, the rest seemed just ridiculous.
- StavrosK 10y agoYes, but the recruiter should have said "oh, you're technically right (the best futurama), next question".
- jknoepfler 10y agoThere's a precise distinction, and thinking about it as "returning" anything other than an error code is chummy human thinking rather than the sort of precise knowledge the test was (supposedly) looking for. The question was actually worse than asking "I'm thinking of a number between 1 and 10, what is it?" because rather than applying a random filter to candidates, it punished the candidate for having precise knowledge.
- segmondy 10y agoPeople that have been around know such things. At one point, Richard Stevens (RIP) was god. Every programmer had a copy of TCP/IP illustrated, Advanced Unix Programming and Unix Network Programming. If you wanted to do anything network, you had to write your own servers, you had to understand the details. The breath of knowledge was wide and the depth was just as deep. Ask around on HN, and you will probably be shocked how many that know such things. :-)
- henrik_w 10y agoUNP is excellent! Haven't opened it in a long time though.
- pjlegato 10y agoAnd then, the world developed robust, well-maintained, open source libraries that do all of that for you. Now, in 99% of commercial software engineering, you don't actually need to know any of those details, in the same sense that you no longer need to know exactly how many transistors and diodes are used to build the adder on the CPU. It simply no longer matters in almost all cases. Your time is much better spent moving on to higher level problems. If you're interviewing for the rare 1% case where the job will actually require you to tinker with a TCP stack, then by all means ask about those details. For 99% of programming jobs today, it's irrelevant trivia used as nothing more than an ego measuring device.
- vvanders 10y agoNone of that matters, until it does :). I feel like I've seen 2-3 articles alone in the last month that has rediscovered head-of-line blocking and UDP. I'd say 1/10 engineers I talk to even know what cache aware datastructures are. The thing that separates someone who can just string together whatever they find on npm to people who build real systems is this deep understanding. You're not going to need this for your standard LoB apps. However if you're in the business of building software you're definitely going to want people like this.
- pjlegato 10y ago
- jackweirdy 10y agoMedical 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".
- ryandrake 10y agoWhat are the components that make up a color? "Well, it depends what color model you are using, which differentiates between additive and subtractive color mixing, the medium used (print, screen, etc.)... No. It's Red, Green, and Blue.
- chrismorgan 10y agoBut hang on, the primary colours are red, yellow and blue! I know, they told me so in primary school.
- cwilkes 10y agoThose primary colors are real to me dammit! /colorblind
- madamelic 10y agoI legitimately had a huge argument with my (former) roommate over primary colors. She was more artsy, I was insistent that the primary colors were RGB, she was insistent that they were RYB. We googled. We were both right in some senses.
- snovv_crash 10y agoCMYK would be right. RYB means you can't produce cyan or magenta or vivid purples or pinks.
- tomsaffell 10y agoGood job you didn't have a third roommate who worked in printing...
- mgkimsal 10y ago"I mean who would know just how long a MAC address is? Or what the actual SYN/ACK etc tcp flags are?" This isn't even my domain, but I remember some of this stuff. I had to dig in to this area years ago, and was knee-deep in that level for several months debugging and configuring stuff. Some of it stays with you, even if you're not there any more. For someone applying for a director of engineering, I'm kind of split as to whether this should be required "off the cuff" knowledge. Would certainly help, but seems it would depend on the culture of the company - how hands-on they expect director-level folks to be - some companies seem to want that, some don't.
- imh 10y ago>...but I'm sure even a relatively junior coder would be able to tell if someone was just doing technical word salad. In interviews, I've had people give answers I'm not familiar with. The easy thing to do is to ask them to explain how their answer works. You get to vet whether it seems legit, and as a bonus see how good they are at communication in a genuine teaching moment.
- walshemj 10y agoAnyone who's done any networking will know how long a mac addresses is
- SomeCallMeTim 10y agoI've had questions that drilled down into what bytes are in a TCP/IP packet on an interview. If you say you know about TCP/IP on a resume, it's fair game. FWIW I got all the bytes but the checksum; apparently no one ever remembers the checksum byte. :) What's completely wrong with the situation is that the recruiter was saying "wrong" when he was giving detailed answers. The right solution is to have a non-skilled recruiter take careful notes, asking the candidate to repeat if necessary, in the cases where the candidate insists they know the answer. Then only in cases where the candidate can't answer a question should it be marked as "wrong." In other cases the answers should be run past someone knowledgeable. I've gone through a phone interview with Google myself, and it was nothing like this: I spoke with a real, skilled engineer, and there was nothing like a "gotcha" question where I had to guess the exact term he meant. Well, except where he asked "I bet you know what my next question is" and I didn't guess "How can the algorithm be faster?" But he didn't count that against me. :)
- sidazad 10y agoThe right solution is to have a technical person conduct this test.
- deleted 10y ago[deleted]
- rockdoe 10y agoThis costs money. As long as Google receives plenty of acceptable candidates, false negatives are free. (Assuming they get no false positives, which, thinking about it, is a big assumption)
- SomeCallMeTim 10y agoMy presumption was that, for whatever reason, they couldn't or wouldn't do screening at this level by technical interviewers. Obviously having a technical person do the interview is always better. I may have gotten a technical interviewer because I can list a half dozen people who know me who work at Google, most of whom can directly vouch for me. Not sure why the OP got an unskilled reviewer, but if they didn't list references inside the company, they may have been thrown in the "random unknown applicant" bucket.
- smoyer 10y agoI've been responsible for writing network code on embedded systems, you do end up memorizing lots of the structures and constants from the specification because you're constantly looking at them "on-the-wire" to make sure it's write (or debug it if it's wrong).
- user5994461 10y ago> I'm amazed he knew things in such detail. I mean who would know just how long a MAC address is? Not surprised by the questions. Most are [somewhat] common and not particular challenging. I am surprised by the stupid counter-answers from the recruiter thought. This guy should not be giving phone interview.
- dkonofalski 10y agoI'm just reaching here, but is there a chance at all that the test wasn't really about whether or not he knew the correct answers but more that he knew the correct answers and was able to simplify them to the extent that a non-technical user could understand and compare them? I have a feeling that Google is far more interested in someone being able to get their point across than someone that just wants to sit there and argue about whether or not an answer is right. Just based on reading his responses, I got a condescending vibe and a vibe that this guy always has to be right and would work terribly with people of different levels of skills. At a Director-level position, that kind of skill is the most basic skill you need to have.
- justicezyx 10y agoThat's not the problem, a non-tech recruiter cannot assess the correctness. Even the simplification can be done, which I disagree, the answer will be rejected because it's not a literal match. That, is the problem.
- CoryG89 10y agoYeah I agree. I think one issue is also the test. For a lot of these things, as with most things, there is a short answer and a long answer. I think by the second or third question I would have picked up on the fact that the recruiter didn't really know what he was talking about and was looking for the short textbook answer. Seems like the author refused to or couldn't do that.
- dkonofalski 10y agoThat's not the point of the test. The point of the test is to see whether or not the person attempted to get on the level of the person they were talking to. I have a feeling that the interview would have kept going had the author not started to argue. They're looking for someone that can translate, not someone that will talk down and argue just so that they can be "right".
- justicezyx 10y ago
- user5994461 10y ago> I wonder what would happen if ordinary people recruited for medical doctor jobs? Would you be comfortable rejecting a guy who'd been in medical school for 10 years based on his not knowing what the "funny bone" is? Wouldn't you tell your boss that you felt a bit out of that league? It's amazing you can get someone to do this without them going red in the face. The medical recruiter asks to see the diploma. The doctor shows his degree and gets the job.
- lordnacho 10y ago"Diploma says DO, not MD. You don't get the job." https://en.wikipedia.org/wiki/Comparison_of_MD_and_DO_in_the_United_States https://en.wikipedia.org/wiki/Comparison_of_MD_and_DO_in_the...
- inopinatus 10y agoGiven that osteopathy is pseudoscientific dogma, that's not an unreasonable outcome.
- alfalfasprout 10y agoEh, that's really oversimplifying it. Yes, DOs are taught some fringe-ish things. But the rest of their education is very comparable to that of an MD. I expect in the long run that many of these quacky aspects of the osteopathy curriculum will quickly vanish.
- trelliscoded 10y agoIf you've had to troubleshoot network corruption at scale, you memorize packet details real fast :)
- lucb1e 10y ago> I mean who would know just how long a MAC address is? Uh, my main languages are PHP and Python (high level stuff) and I'm a student (not someone with 10 years of experience) but I knew that. 3 bytes for the vendor block, 3 bytes for the device. > Or what the actual SYN/ACK etc tcp flags are? Yeah the actual bytes, who ever uses that? A MAC address I've seen plenty of times in my life as hex, and I've seen the TCP setup flags being exchanged plenty of times in Wireshark and looked up the hex once when I was implementing TCP from scratch, but I still wouldn't expect anyone to know that. > You just need to know what they're used for Agreed on that. I wouldn't blame anyone for not knowing the size of a MAC address, I just didn't think that one is that obscure.
- throwaway2016a 10y ago> I'm a student (not someone with 10 years of experience) but I knew that. 3 bytes for the vendor block, 3 bytes for the device. That is why you know the answer. Come back in 10 years and let us know if you still know it. What you think might be mainstream in a computer science class are rarely used in application. And if they are they can be easily looked up. I used to know the exact effective distance of a CATV cable when I was a student. Useful? Sure. Something I need to remember for the rest of my life? Definitely not. As another example, in 17+ years writing ISO level 7 programs, I have never once needed to use the Mac address.
- wpietri 10y ago> Come back in 10 years and let us know if you still know it. I've never taken a CS class, and I still know it. I've just stared at enough packet dumps and debugged enough issues that it happens to stick. I think it's a stupid question to ask as a screener, as it tests familiarity with trivia. It's the kind of thing I'd be happy to see that somebody knew, but it's never something I'd downcheck them for not knowing. It could just mean, as in your case, that there deep knowledge is somewhere else.
- throwaway2016a 10y ago> I've never taken a CS class, and I still know it. I've just stared at enough packet dumps and debugged enough issues that it happens to stick. We are all a product of our environment. And there is certainly a chance in 10 years the OP will still know how many bytes are in a MAC address. I only mentioned computer science based on the "student" part of the quote. Personally I've been spoiled by working on higher level stuff so if I do look at a packet dump I usually filter the packet headers out. But again, we're a product of our environment and asking questions that a reasonable skilled engineer might go their entire career without knowing the answer to except in that interview is a bit suspect and will likely disqualify people that would be otherwise great for the job.
- noufalibrahim 10y agoMy father is a civil engineer and late in his career, he interviewed for a senior position at a construction company. He figured out that the interviewer didn't know what he was talking about early on the interview and confronted him with that. The interview came to a end, he was put in touch with a senior engineer at the company. He didn't take the job for other reasons. I don't think this kind of rubbish would fly in any other industry.
- eternalban 10y agoA civil engineer is a professional engineer. I would assume your father is a certified PE [1]. This rubbish flies in our industry since we are not professional engineers. [1]: https://en.wikipedia.org/wiki/Principles_and_Practice_of_Engineering_Examination https://en.wikipedia.org/wiki/Principles_and_Practice_of_Eng...
- dilemma 10y agoNonsense. It's because your industry is relatively new and hasn't established the same institutions.
- eternalban 10y agoA professional engineer is not someone who professes to be an engineer. S/he is a "professional" per certification by "established" "institutions" within an "industry". > Nonsense. s/\./:
- noufalibrahim 10y agoThis is interesting. Is this similar to things like the bar council for lawyers? I don't know if there is something similar to this in India where I'm from.
- WillPostForFood 10y agoI'm amazed people actually believe the account is accurate. The guy failed the interview, and goes to write a blog post to lash out at google (and try to mess up future interviews for them), So of course he write it to make him look good, and the questioner bad. We will stop here because it's obvious that you don't have the necessary skills to write or review network applications. You should learn the Linux function calls, how the TCP/IP stack works, and what big-O means to eventually qualify if you are interviewed at a later time. Come on Hacker News, I know you hate recruiters, but do you really think that happened?
- deleted 10y ago[deleted]
- rockdoe 10y agoIt's true this is probably not exactly what happened, but Google does certainly ask these questions in phone screens and the interviewers read the correct response off of a cheatsheet. The fact that several Google people posting here literally can't believe this is true shows how fucked up their process is.
- WillPostForFood 10y agoThe fact that several Google people posting here literally can't believe this is true also may mean it isn't true. Not that the questions weren't asked by a recruiter with a cheat sheet, but the quality of response and the attitude of the recruiter has been grossly exaggerated.
- nickpsecurity 10y ago"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?" I was more impressed by how simply he explained many of them in real-world terms. Especially countering Big O. That plus what he's already built indicates he's exactly the kind of person to direct the sort of projects they're building. That they filtered him with this garbage Q&A speaks volumes about Google's ineffective hiring. Plus, indicates what kind of people might have made it into the organization.
- rcarmo 10y agoActually, most people with a networking background would know this kind of detail (and more). It's the relevance (and appraisal of answers) that is shocking.
- meshko 10y ago1) His level of knowledge is reasonable for someone who does networking programming full time 2) We are getting description from him. When I interviewed at Google, they asked me to prove that P is equal to NP, and I did, but they said that it took me longer than allotted 45 minutes and I didn't get an offer.
- vmasto 10y agoOh hey what are you going to do with your million?
- gautamdivgi 10y agoYou proved P = NP??? In a little more than 45 mins or did you misunderstand the question?
- mcphage 10y agoHis point was that, hearing only one side of the story, the OP could claim whatever they wanted.
- deleted 10y ago[deleted]
- krapp 10y agoIf I were asked that question, my answer would be that obviously P != NP because the former doesn't have an N at the front. The pain of being tossed out onto the pavement would totally be worth it.
- dsr_ 10y ago"who would know just how long a MAC address is?" I've been looking at them on NICs, adding them to DHCP databases and using them for simple authorizations in iptables (and prior equivalents) since, oh, 1992 or thereabouts. They weren't new then. It would take me a moment to count them in my head, that's all. "aa, bb, cc, dd, ee, ff -- that's six bytes".
- deleted 10y ago[deleted]
- pjungwir 10y agoI was interviewed once by someone who would cut me off after just a sentence or two. He asked a fairly open question like, "Tell me about hash tables." I knew I should have just said, "Lookups are constant-time," but I started off with a description of their behavior instead, and sure enough he cut me off and said, "Lookups are constant-time." Some people are just not very good interviewers, but also some tech people's rules are too iron, with no exceptions, like they can memorize but not think. They say interviews are a two-way communication, and that one certainly was. :-)
- AnimalMuppet 10y ago> ... like they can memorize but not think. Which is really bad, when they're trying to hire people for a job where thinking is the fundamental skill...
- federicoponzi 10y agoSame things I thought. His answers are amazing!
- jneal 10y agoIt's actually pretty sad. It seems to weed out the smartest folks so that you only hire those mediocre enough to not understand these problems within the hiring test.
- elcritch 10y agoPersonally, these questions and the way the recruiter asked them reaffirm my view that Google would not be a place I'd like to work at as a experienced software developer. First the recruiter's lack of technical knowledge points toward a beaurocratic or management first mindset common (necessary?) in such a large company. Second, the questions and expected answers seem biased toward just graduating but smart engineers who don't actually have experience to realize the subtleties present in complex systems. The recent lawsuits regarding age discrimination reinforce the notion that this interview setup is biased (intentional or not) toward inexperienced and thus likely younger applicants. Perhaps that's not a bad thing per se as Google's corporate development style likely would handle inexperienced but smart developers who can "mold" into the system better. Or it could be more nefarious as to lower salaries by getting younger devs. In reality, probably a mix of both.
- Periodic 10y agoI wouldn't be surprised if the interview process for experienced engineers is unrefined. At this point in Google's lifecycle most of the qualified, experienced engineers who would want to work at Google already do. There are orders of magnitude more new-grad engineers to interview and so it makes sense that they would lack the practice and refinement on those candidates, even if those are the most valuable candidates to hire. The recruiter might have just been confused and gave him the standard list for any "technical" job that they have to use for new-grads and so cannot ask things with nuance. When I was an interviewer at Google it felt like 90%+ of interviews were with candidates who had less than four years of experience. Probably half were fresh out of college. After the fifth candidate in a row who can't do simple recursion or algorithmic analysis (and I mean simple) you get pretty discouraged. In one phone interview I got to interview an experienced engineer with over twenty years of experience in C. He completed the question I usually have to spend 45 minutes on with a new-grad in <10 minutes. It was probably my favorite interview of all time because I actually got to discuss the subtleties and he reaffirmed that I could maintain high standards.
- Retric 10y agoGoogle is still a tiny company relative to the US economy. They might be slightly above average on some metrics, but that’s about it. Large enough they have plenty of idiots, small enough that most smart people don't work there. As to high standards, you are testing for things that have very little to do with someone being good at the job. High arbitrary standards often remove the most talented people who generally don't have the same background as you. EX: Suppose you where looking for a CEO, well having a collage degree seems like a reasonable requirement. However, a surprising number the best CEOs don't.
- jxramos 10y agoI think the interviewee after realizing the shortcomings of the tester's understanding and the author of said "right answers" should have interrupted or ended the probing after a few red flags and politely suggested something along the following lines... "Look I get the gist of what this screening is trying to do but please write down my answers and feed them to the technical staff who authored this Q&A and have them verify their misunderstandings and have them get back to me please. I am very confident you all have subtle details mixed up and could benefit by a strong candidate who understands such details with a higher level of fidelity." Guess its another loss given to the recruitment focus on avoiding false positives over false negatives.
- skywhopper 10y ago> 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 Depends on what you actually do in your job, I suppose. If you use that information regularly or troubleshoot networks regularly you would soon enough memorize it. > and if you need the specifics, you'll find out with a single search. Someone doing network programming _does_ need the specifics.
- TYPE_FASTER 10y agoUnderstanding SYN/ACK, and what they are used for, can be quite useful in troubleshooting networking issues so I can see why this would be useful in a SRE or other role that dealt heavily with communication.
- esalman 10y agoIt happens because great developers do not do recruiters' job :)
- mirekrusin 10y agoHe's one of the best programmers you can get (in the world) when it comes to networking and friends. Gwan is less known around because it's not OSS but I believe still achieves unmatched performance. This interview must be some kind of a mistake. It's like testing Richard Feynman's knowledge with questions about multiplication table (where you have wrong answers on your table). It's so stupid that it's almost not possible to laugh.
- diakritikal 10y ago>Gwan is less known around because it's not OSS but I believe still achieves unmatched performance. ERR_CONNECTION_REFUSED
- chucky_z 10y agoGwan's performance is the real deal. It's also the least stable piece of software I have ever used in my entire life. That last sentence is important.
- iconjack 10y agoWho would know just how long a MAC address is? Jeez man, these things are literally written as 6 bytes separated by colons. Asking a network engineer this question is about like asking a postman how long a zipcode is.
- ww520 10y agoI would have failed the question. I don't remember how many bytes in a MAC address. That's something that can be easily looked up.
- ci5er 10y ago> 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? It's what happens when you get old. There were commonly C compilers on 8, 16, 20, 24 and 32 bit architectures, some big-endian, some not, and you couldn't google things in 20 seconds back in those bad old days when old farts were building the networks that would be used to connect to us all to google. (And he has apparently been in networking since)
- mfukar 10y ago> I mean who would know just how long a MAC address is? Hmm, let me think. Somebody working with routers for 10+ years. > ..what the actual SYN/ACK etc tcp flags are? Same. I mean, these things are just as familiar to me as grade school multiplication, by now..I bet there's things familiar to you which I couldn't even be bothered to memorise and instead had to turn to a search engine for.