News for hackers. Stuff that matters.
Re:On Interviewing Programmers by neilv on Wednesday July 08, 2020 @09:55PM (#23776239)
I like this idea of interviewing by talking about interests and things worked on, though it's complicated, and I can't claim to have figured it all out. A few thoughts...

I used to interview people by looking at their resume, and starting asking curiosity questions about things they worked on, and going from there. I didn't have anything in particular I was looking for, just a vague sense from how they talked about it.

That's more complicated when organizations want to avoid the appearance of IP taint, so, it'd help if they had a side project/interest to talk about. But I'm not assuming everyone has time for that. Also, they might be slammed by work, and in project mental space they can't talk about, and temporarily skewing the impression they give about their curiosity about other things.

What's really unfortunate is all the formulaic, going-through-the-motions interviews these days. We used to make fun of the practice of hiring based on firmness of handshake, how well you dressed, and ridiculous standard interview behavioral questions that might as well be shibboleths for the people who prep for them. Now most young developers are told to prep for conveying culture fit, and answering particular kinds of CS101 coding questions/hazing, which seems to be much the same thing.

That said, though I think I can do better at finding great people than that, I still need to remember to add a big dose of humility, to the idea that I can get a sense of a person as an engineer, just by talking with them. I believe I can do a pretty good job of that, with some conscious uncertainty, and I'm self-aware enough not to simply hire people in my own self image. But of course I surely have more biases than I know, and there's a lot unknowns, and our practice is not science. So I should add in extra humility than I'd naturally have about this, and find the right balance between vision of what I think is needed, and being open to seeing things I didn't already see.

I also need to recognize that I'll have people coming to interview, having read the "Cracking the Interviews of FAANGs and All the Other Companies Who Act Like Stodgy Fortune 500 Hiring Large Numbers of Commodity Brogrammers" prep books, and probably seen that in some/most of their other interviews. :) And if someone shows up expecting the current usual rituals, I shouldn't hold it against them, but rather, it's my responsibility to communicate that I'd like to try to do this a bit differently.

One fear is that I'll explicitly tell people I'm looking to do this "genuine", and some will interpret that as an empty platitude or conceit, in interview prep book behavioral right answer terms. :)

Re:On Interviewing Programmers by pantaloony on Wednesday July 08, 2020 @10:45PM (#23776479)
> it's my responsibility to communicate that I'd like to try to do this a bit differently.

Yes, and please, to all interviewers, tell candidates WTF they’ll be expected to do/talk about in the interview, in the greatest detail possible, as early as possible. If FAANG can basically publish study guides you can give more than “here are the people you’ll be talking to, and when.” What about? Will there be exercises. Leetcode? Easy, medium, hard? One of these or is it like half the day? You’ll want to chat about networking? JavaScript trivia most people don’t remember because they use patterns that avoid those parts of the language, and have for years?

Again, if FAANG can give the kinds of guidance they do then Bob’s Mobile Dev Agency can give candidates something about what they should expect without ruining the process.

Like, it doesn’t all need to be scripted but most employers seem to think it’s fun to make candidates come in with no idea whether they’ll be white boarding all day or sitting around singing Kumbaya in rounds

Re:On Interviewing Programmers by rikroots on Thursday July 09, 2020 @07:39AM (#23779078)
> We used to make fun of the practice of hiring based on firmness of handshake

True anecdote time. A few months after starting my first full time job, I asked my boss why he chose me over the other candidates. "You had the driest handshake" was his answer.

In the man's defence, my first job was as a microbiology lab technician. His explanation was that a dry handshake was a good indication that a person would likely have a better aseptic technique, thus leading to fewer false positive results when performing the tests. Utter nonsense, of course.

Re:On Interviewing Programmers by invalidOrTaken on Wednesday July 08, 2020 @10:07PM (#23776309)
>I also need to recognize that I'll have people coming to interview, having read the "Cracking the Interviews of FAANGs and All the Other Companies Who Act Like Stodgy Fortune 500 Hiring Large Numbers of Commodity Brogrammers" prep books, and probably seen that in some/most of their other interviews. :) And if someone shows up expecting the current usual rituals, I shouldn't hold it against them, but rather, it's my responsibility to communicate that I'd like to try to do this a bit differently.

>One fear is that I'll explicitly tell people I'm looking to do this "genuine", and some will interpret that as an empty platitude or conceit, in interview prep book behavioral right answer terms. :)

This seems like a good problem to think about. I don't have a solution, but I think it's a good thread to pull.

Re:On Interviewing Programmers by Google234 on Thursday July 09, 2020 @02:29AM (#23777528)
I personally don’t get what the issue is with expecting serious devs to know their CS101 concepts and how to apply them to problems
Re:On Interviewing Programmers by gedy on Thursday July 09, 2020 @03:18AM (#23777762)
It's more that if that is the primary/only thing you are testing, you can get people who ace that but are crap application & product developers/leaders.

Also I personally really hate it when you are treated like some giant imposter when you don't remember some pet CS quiz question when you are 15+ years out of school, and for supposed "leadership" positions. Attitude is like "ho ho, trying to pull one over on us".

Re:On Interviewing Programmers by siscia on Thursday July 09, 2020 @02:37AM (#23777573)
It is not expecting Devs to know the foundamnetals, developer should know why it is faster to look for elements in an hash map than in a list. It is expecting to code an hash map from scratch in ten minutes on a whiteboard.

(And hash map are not even that difficult, but I got asked stuff much more complex than that...)

Re:On Interviewing Programmers by itsjzt on Thursday July 09, 2020 @05:49AM (#23778517)
Afaik best case of finding an element in a list is fast as anywhere else.
Re:On Interviewing Programmers by partyboat1586 on Thursday July 09, 2020 @09:30AM (#23779934)
Hash map is O(1), List is O(N). Unless it's a really small data set the hashmap will be faster. I don't think OP wanted best case.
Re:On Interviewing Programmers by WrtCdEvrydy on Wednesday July 08, 2020 @10:31PM (#23776422)
> when organizations want to avoid the appearance of IP taint

So we usually try to talk about what they're learning on their spare time, any personal projects, any cool technology they're looking to learn... then follow it up with what have you done so far to start on this, any small toy projects on this new technology.

It's a weird organization because aside from COVID-19, we've had very little turnover (most people are with us 3+ year with an average of 7 years) so we've kinda changed up hiring a little bit over time.

Re:On Interviewing Programmers by neilv on Wednesday July 08, 2020 @11:24PM (#23776656)
I currently think that's trickier than I used to. I'd like to mention a few thoughts on my mind on this idea in general (not criticisms, nor making assumptions about the nuances of how you do things).

I live to work, and have had a bunch of open source involvement, and have had serious side interests, so those interviewer questions are to my advantage, when I'm the candidate employee/cofounder.

But a lot of candidates will have families that take up all their non-work time. (IME, some of them are among the best engineers.) And those candidates with families might've heard that many interviewers will discriminate against them for that, wanting people who can regularly put in 60hr+ weeks and surge to 80hr+ of grunt coding. So, I figure they might cringe at talking about how they're spending their "spare" time. I'm absolutely not going to discriminate against them, nor do I want them to fear that they might be discriminated against, or feel alienated because they keep getting questions like that in interviews.

And for the people who're pursuing cool technology through their employer, I'm really hoping it doesn't sound like they prioritized adding this year's unproven hot framework/buzzword to their resume, over the success/risk of an employer's project. :)

Re:On Interviewing Programmers by WrtCdEvrydy on Thursday July 09, 2020 @12:23AM (#23776920)
There's nothing wrong with focusing on family.

The only people who had serious issues were those who said they were not learning anything at their current and had no interest in learning anything new.

Re:On Interviewing Programmers by neilv on Thursday July 09, 2020 @01:13AM (#23777135)
Yeah, most developer jobs I've seen require constantly learning new things. And I don't think I'd like working very long somewhere that didn't need people to keep learning -- not so much learning the flavor of the month yet-another-framework, but learning a breadth of things, and picking up whatever is needed. I actually emphasized that in a draft job post recently.

BTW, just to be clear where I'm coming from about families, I think people can focus successfully on both work and family, at the same time. (If they're working in an organization/projects that don't end up wasting so much engineer-time that they think they need people who can be typing 80hr/wk.)