News for hackers. Stuff that matters.
Re:Interviewing candidates by RogerL on Monday June 08, 2015 @05:24PM (#9682550)
"Red flags often surface at this point. I’ve had candidates with PhDs in computer science, for instance, who did not know that on a 64 bit architecture, pointers are 64 bits wide."

Because learning 64-bit architecture is impossible for somebody that have proven that they can learn a field, perform research, and successfully write and defend a dissertation? '32 < 64' is beyond them?

Re:Interviewing candidates by ericlippert on Monday June 08, 2015 @07:34PM (#9683174)
No, because we are actually building telescopes here, and astronomy PhDs apply, and when they are not actually clear on the difference between a reflector and refractor telescope you realize, hey, this person is going to need to learn so much about the very basics of the field that they're applying for that it's not going to be a good fit.

I've had candidates with PhDs in computer science who thought that pointers on 64 bit operating systems were two bytes wide. Do they believe that there are only 16000 possible allocations before the allocator fails? Not likely, because that's ridiculous. So how could they have that belief? because they understand so little about pointers that they don't understand the implications of their false beliefs.

I need someone who is going to command the salary that a PhD-level candidate will demand to be able to hit the ground running.

Re:Interviewing candidates by RogerL on Tuesday June 09, 2015 @08:20PM (#9689374)
On your latter point (pointers) I've heard that argument before. I work with somebody that turned out not to know about hash tables. I could spin a tale about how this meant they were so wide eyed they'd just be incapable of doing anything valuable (an argument made so many times on here). Instead, I took 15 minutes and taught them about hash tables and how to do them in C++. A few pointed questions about run time and the constants implied by the promise of O(1) (i.e a good question), and from then on every time a hash should have been used sure enough, they used one. Even showed initiative and added a memcache type interface to some of our code that was performing very slowly due to poor access patterns.

I guess it is lucky for us that when they interviewed they didn't have an interview question that involved hash tables, because they would have been bounced for not hitting the ground running.

I bet I know a lot about a field that you don't. I wouldn't bet that you couldn't walk in and pretty quickly become useful, given that you've learned other things, and at one time I didn't know this field either yet somehow, somehow, learned it. I think you would do just fine; and I think somebody that can get a PhD in CS can handle the math that 2^16 < 2^64, even if they haven't thought about the implications re allocations.

Re:Interviewing candidates by zerr on Tuesday June 09, 2015 @12:42AM (#9684126)
Different perspective: I believe for most CS persons this would be a 5-minute-difference... i.e. it would take 5 mins for them to understand/research 64 bit OS pointers size. So basically you're penalizing potential good candidates for just 5 minutes of their life.
Re:Interviewing candidates by raverbashing on Tuesday June 09, 2015 @05:51AM (#9684880)
Yes, it may be only 5 min.

But it tells a lot about the amount of "just 5 min" things they don't know.

I was asked once what load average knows (and I didn't know it). Because my background wasn't in sysadmin.

The fact that you know one fact or doesn't is immaterial, but it's a good proxy.

Your hiring decision should not be based on only that, of course, but let's say it's a pixel in a picture.

Re:Interviewing candidates by vacri on Tuesday June 09, 2015 @02:30AM (#9684358)
Different perspective: I'd prefer to hire the astronomy PhD who knows the basics of the craft over one who doesn't. Reflecting vs refracting is pretty simple - astronomy doesn't really interest me and I'm aware of the differences. It's fundamental to the optics, and understanding the differences helps understanding why real data looks different depending on method of acquisition. Why not penalise the person that doesn't know the basics? You wouldn't forgive a carpenter for not knowing the difference between a hand saw and a table saw, yet they both cut wood and the difference takes all of a few seconds to learn.

For example: I'm a midrange DevOps/Sysadmin/Whatever-it-is-these-days. I will likely never be a senior. The (real) seniors are the folks who go home and mess with hardware and pull new toys apart to see what chips they were made with and so forth. I like to go home and play games. I do my job competently, but I don't have the underlying knowledge that those guys do. If I was up against one of those in a job application, then you'd be crazy to hire me at the same salary as a senior - there'd have to be a pretty big black mark against the senior, like being completely unpersonable or abusive or somesuch. Or the role used some of the other things I'm decent at. Perhaps a colloquial way to put it is that I live these things, but the seniors live and breathe them :)

[dead]
Re:Interviewing candidates by schrodinger on Monday June 08, 2015 @10:55PM (#9683819)
Do you know who Eric lippert is or the work he does? This knowledge is absolutely very important for the kind of work for which he'd be hiring.
Re:Interviewing candidates by dang on Monday June 08, 2015 @11:29PM (#9683927)
> You seem very entitled.

Personal attacks are not allowed on Hacker News.

Re:Interviewing candidates by brobdingnagian on Monday June 08, 2015 @09:57PM (#9683661)
I agree.
Re:Interviewing candidates by patmcguire on Monday June 08, 2015 @07:32PM (#9683170)
Ah, but the company builds static analysis tools. Dinging someone for not knowing the minutia of languages makes a lot more sense when the minutia of languages is your business.
Re:Interviewing candidates by bzz01 on Monday June 08, 2015 @06:10PM (#9682810)
I guess author assumes that if you don't know basic things like that, it is questionable that your degree is a proof that you "can learn a field etc."

Not sure that I agree on the choice of this specific "red flag"; on the other hand, having PhD in CS is a red-ish flag to me per se.

Re:Interviewing candidates by mediocrejoker on Tuesday June 09, 2015 @12:06AM (#9684016)
"... on the other hand, having PhD in CS is a red-ish flag to me per se. "

I would be interested in hearing your reasons for that.

Re:Interviewing candidates by bzz01 on Tuesday June 09, 2015 @12:37AM (#9684105)
So of course I'm generalizing, not everyone is like that, not everyone's CS degree is like that, etc. etc. Also, more true for recent grads.

But in my experience people with advanced "pure CS" degrees seem to be focused on the process not the result. I mean, they went to CS because they like to tinker with type systems, elegant algebraic concepts, nice abstract problems -- and not just as a hobby, they like it so much so they commited several years of their lifes to do that. Not that this is bad area of research, but generally when you look for a software engineer you look for someone not only smart but also pragmatic, who can get stuff done in a simple and efficient way, and this is kind of the opposite.

Of all PhDs, in my experience people who have degrees in areas that use programming as a tool not the goal in it self, e.g. physicis/EE, make the best software engineers.

Re:Interviewing candidates by teraflop on Monday June 08, 2015 @06:17PM (#9682854)
You could say that about almost any kind of knowledge-based evaluation.

If I ask somebody ten factual questions and they know the answers to five of them, how should I interpret that? Sure, it would be easy for me to just fill in those particular gaps in their knowledge. But assuming my questions were well-chosen, it's reasonable for me to expect that they'll continue to hit similar gaps in the future, about 50% of the time.

That's not to say that a good interview consists of drilling someone on facts; more often, they come up implicitly in the context of solving a problem. And as an interviewer, I'll look much more favorably on a candidate who recognizes what they don't know, because I give them the benefit of the doubt and assume that in a real-world situation, they would be able to do the necessary research. But even so, if there are basic things they don't understand, it's a red flag because it tells me they're encountering these concepts for the first time.

Re:Interviewing candidates by kelnos on Monday June 08, 2015 @08:34PM (#9683404)
He's not saying a PhD means you necessarily won't know that 64bit machines use 64bit pointers, he's merely pointing out that he has seen candidates where that's been the case, and that you can't assume that having an advanced degree means you understand the minutiae of computer architecture and how memory addressing & compilers work.