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. :)
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
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.
>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.
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".
(And hash map are not even that difficult, but I got asked stuff much more complex than that...)
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.
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. :)
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.
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.)
Sorry, that's against company policy.
1) You want your experts to be spending their time solving problems, not interviewing people.
2) As the size of the organisation grows and it becomes a more attractive target for lawsuits (fair and otherwise) it becomes crucial to make all of your decisions in a defensible way. 'The tech lead doesn't like this candidate' will get you sued for discrimination if it's the only thing you can say when accused of prejudice.
While saying that, just because one is an expert does not mean they are an expert at identifying other experts. It is it a skill set in it's own right.
Yes there is still a tiny possibly that it is just a talker, but such possibility seems much smaller than the possibility that it pass a coding interview on a whiteboard and then he is not that good.
The college project thing applies to the workspace as well; in a team or a project there's always going to be only a few or one that does the most and best work, and a lot of hangers-on.
That is actually a source of impostor syndrome for me, because if I look at my CV there's a lot of really interesting and varied stuff on there, but it was always me as part of a team. How much of what I contributed was original thought vs just copy / pasting someone else's work and changing some values?
That's said impostor syndrome speaking of course, I know I'm a competent developer and ATM I'm working solo on a project. Slowly.
1. Asking them to talk to you as if they know you is implicitly asking them to reveal quite a lot about their personal life; a life which you, as a prospective employer, has absolutely no business poking your big nose into. Don’t ask about their personal life.
2. As “JMTQp8lwXL” pointed out in another reply, this also opens your selection up to selection bias to prefer your personal preferences, not what would be good for the role. This kind of thing is, unfortunately, rampant, and leads to enormous monocultures where everybody who works at a certain place seems to be the same person; they all dress the same, like the same things, talk the same, and look the same. This is the very opposite of diversity.
And of course diversity for diversitys sake is the highest principle there is.
Also, all people with similar interests are carbon copies of one another.
As you sarcastically pointed out, diversity for diversity sake is a false virtue IMO.
I’d rather hire for those skills plus code reading ability because I’ve honestly never used a single “algorithm” in my entire working life.
Employers seem to be entirely ignorant of the power relationship in job interviews; interviewers all want to talk to the candidates like a peer, even though this is not at all appropriate.
I've come to the conclusion that nothing does, and that the place to think about scaling and repeatability is in training, not hiring.
I know it's weird, but I just ask them what they're learning, if they have personal projects and just use that to see if they have experience writing software.
Some people are super-excited about what they're learning, want to talk about the technology and end up making a good impression. Some people are only able to talk about what they're doing at work, the technical challenges and usually make a good impression as well.
Whiteboarding is usually kept to high level concepts like normalization, data flow, logical architecture and things like that.