Sorry but I think it's a bad question. What if the answer is "Oh I don't have much spare time these days, I make dinner for our toddler son and put him to bed. My lesbian partner can't help much because she's expecting in a month." It's a trap leading to unwanted information - many of which would be downright illegal if factored into hiring decisions.
There's a reason why all the big companies emphasize never to ask anything about nationality, ethnicity, marital status, religion, blah blah. You don't need to know, you don't want to know.
Oh, congratulations!!! Do you know the sex of the baby yet? What an exciting time, I bet you have lots of preparation going on. I also have a child and (blah blah bit of history)
So we ask this question to get a bit of an idea about the candidates hobbies which tells us about them as a person, - are you outdoorsy or indoorsy? Are you a movie buff or a reader, or a rock climber or a painter or a poet? Or something even more interesting?! before you were so busy, how would you spend your non-work time?
That way:
Puts them at ease, shows you have empathy for their situation, find common ground, explain the reasoning for the question, gently nudge the conversation towards what we were looking for.
It’s not rocket science people it’s just conversation skills.
What the hell man, are you speedrunning the ability to get sued / posterized on Twitter?
They don’t have to work with whoever we hire. But they have to fear unconscious bias and the potential for some lawsuit because we cannot produce some paper trail for why we picked one person over another.
As a result we have an inferior hiring system because we have to ask a bunch of dumb questions from a script rather than having a conversation and exploring who the individual is as a person and as a professional.
Hiring discrimination is a real problem. This is a sad attempt at addressing it.
At it's best we tended to reject too many great candidates because our rubrics were so rigid, and it didn't let us make room for folks that were clearly amazing but didn't answer the questions in just the right way. Seriously, the talent we passed over was truly world class.
There's a lot to be said for all of the non-verbal and subtle information that's conveyed in an interview. I think that throwing that all away is foolish because you're not really doing much better at removing the bias anyway.
They can do this because their prestige ensures a near limitless supply of candidates willing to jump through those hoops.
Wouldn't it make more sense to consider the fastest growing companies, or perhaps the subset of fast growing companies with the most profit per employee?
From a human side, I would hire someone who decides to take care of their kid after hours instead of honing their technical skills. They tend to be a lot more responsible with their work too.
Let the candidate lead the conversation. People love being listened to. Where they take it is way more revealing about them than any fixed interview grid. And they leave the interview with a smile because all they had to do is be themselves.
I don't see how one could be sued for discrimination based on information that people reveal of their own will.
Maybe it would be more appropriate to word it like that? Maybe not?
But if that is their answer, it’s also a gateway to a more natural and relaxed conversation about the tech they care about and what makes them tick.
I’ll often learn far more about a person that way than the typical “tell me about a project/time when…” style questions.
In my entire career the single most talented Programmer I ever knew was a single mother who logged off the computer every day after 8 hours period, and choose to spent her life with her kids.
I'm sure that mother would give amazing answers to the other parts of this interview.
In contrast, the places that have done tech interviews have generally been awful to work at. Less intelligent people, less interesting work, worse management, etc.
I know engineers love open, discussion-y interviews and senior interviewers like giving them, but the evidence just doesn't bare it out. "Work sample tests" and "Structured Interviews" are the most predictive of on-the-job success from the published research I've seen. No matter how much I'd prefer to have a freewheeling conversation as you describe, I have to bow to the evidence.
I've been to work for companies that say anything you build while employed at company belongs to them unless you go through the proper channels of red tape to discuss the projects with them to ensure that anything you are working on does not involve any company IP. This could sound like baiting for a different direction than the other comments are alluding.
I think the idea of the question is sound, but it's sufficient to ask "what drives you?" and dig in there.
Like if someone says their goal in life is to make the best tasting sourdough, ask them how they go about doing that. Researching new recipes? Starting with a base recipe they like and making small tweaks? Optimizing for their own taste preferences vs the tastes of the people they share it with? Etc.
Even if their hobby isn't collecting Github stars, you can still learn a bit about their mindset. Plus I've found that getting someone to talk about something they're passionate about for 5 minutes is a good icebreaker to start an interview.
You're virtually guaranteed to not be terrible given this self-evaluation. You might not be some senior-level elite developer, but I'm not sure I've ever met someone who said this who was truly awful.
I feel it's hard to fake convincing answers to these kind of "getting things done in the real world" questions.
Like if i was to answer that honestly, it was fixing an obscure i18n bug for an underserved language group. I felt it was cool because it was such a small amount of work but made some people inordinately happy. In many ways i am much more proud of this 20 min bug fix than all the big technical projects i've done. But if you asked me any technical questions about it, the answer would almost entirely be - i used the architecture that already existed, because i was fixing a bug not rewriting the code base.
Fixing a bug isn't the same as building something, though.
The point is to see if the experience you claim matches what you have actually done.
I work for a finance company. The vast majority of the devs, including seniors, haven't released any software outside of work. Maybe 10% have. It seems this is true for other non-tech industries too.
Even on here, do you think more than 50% have released something they made by themself, that is more advanced than a simple Android app? Obviously there's a lot of talent here. I would be surprised if the number is higher than that.
If you’re been working 5-10 years or more and you’ve never built anything at all that you’re excited about, that’s a red flag.
Made me think the other questions are follow-ups to these.
Eh, when you work on large systems in a large and highly regulated company, it's not very exciting. There have been some interesting components to those systems, but in general they have been mundane business topics with tight guiderails and little freedom. I mean, the majority of people in the world don't get "excited" about work - it's just the means of survival.
My time outside of work and what I do for fun isn’t your concern, and I don’t want to share those details with you.
You really can't tell anything at all from a conversational interview besides: can this person hold a conversation? And minor inklings of whether or not the person is insane.
But otherwise, people lie, and misconstrue, and misrepresent, and plan beforehand. The only thing these conversations are going to do is confirm your own biases.
I'm more inclined to believe whoever set up your hiring pipeline did the majority of the work, and they gave you pretty all-around good candidates, who you then selected for... social fit.
If I get asked these sort of insincere questions whose sole purpose are to judge, I'm just going to lie to you, to get this interview over with faster.
> Ask them hard questions, but don’t intimidate. Just go deep. The candidate cannot fake this. It’s not possible. People without the experience they claim are painfully obvious here.
It's possible. There are some very smooth talkers out there, and as much as we'd like to think we can spot bullshit: when the sums at stake are large, people will work very hard to do everything they can to get them. It's not that hard to bullshit a project you've never actually made before... you just take bits and pieces from other work and massage it until it all fits nicely (but not too nicely). With some skill, you can do this on the fly rather unconsciously, and just get in the zone.
I've done it before (for shits and giggles; never for employment opps I've ever accepted). It works best when you're talking about something the author clearly has no experience in (perhaps I could even be bullshitting this entire post?).
Personally I never had a problem with it and from the interviewer point of view it helps lighten the atmosphere a bit talking about out of work stuff.
Maybe your first question might work to get more at that idea.
1) When the person who wrote the code is no longer available to talk to. Having even a 5-10 minute chat can massively speed up my comprehension of someone else's code and save a lot of time.
2) Unused code that hasn't been deleted. I think everyone should strive to clean up their codebases. I'm not exactly blame-free here either so it's something I try to apply more and more as the codebases I work on start staying around for longer.
1. What do you do for fun when not at work? … dig into to questions from here. 2. What is the coolest thing you ever built? How did it work? How long did it take to build? What language? What architecture / framework? What was hard about it? … you get the idea. 3. What are your biggest pet peeves when it comes to reading other peoples code?
Question #1 breaks the ice and gives permission to the candidate to be themselves. Look for common ground. Connect with them. Learn who they are as a person.
Question #2 gets you to see their passion. Talk to them on their ground. Give them the benefit of the doubt. Ask them hard questions, but don’t intimidate. Just go deep. The candidate cannot fake this. It’s not possible. People without the experience they claim are painfully obvious here.
Question #3 gives you two things. 1. Is this person openly critical of things looking to improve them? And Is this person a jerk? I call this the Jerk Trap. Jerks jump right in to being Jerks. After all you just kind of game them permission here! — I would ask though you be careful about excluding neurodiverse people who may not be able to control tone or navigate social situations well. These people will tend to be direct. Don’t confuse directness with being a Jerk. They are not the same thing.
I’ve interviewed a lot of engineers in my career, and tried a lot of things. This methodology has yet to fail me.
EDIT: It’s sad I even have to point this out, but in #1 you are looking to connect with the person on a human level. It’s not bait them into talking about coding outside of work. If you do that or think that way you are being discriminatory towards people who can’t code outside of work… you know like single mothers. And people wonder why we don’t have more women in tech. Stop equating passion with > 40 hours a week. It’s bullshit. Stop.