Live data from Hacker News

Take-home interviews

blog.triplebyte.com

251–260 of 295 posts

Re: Take-home interviews

#251

Earlier quoted context omitted.

Agreed (and see the linked comment please): If it's not a replacement for whiteboard bullshit, then GTFO. That's insane and maybe 'the worst'. But it's important to remember that a take home exercise cannot fully replace an interview. It can replace the coding part, the whiteboard "and now we ask useless trivia questions" part. But there's no way for this work to replace the "would you fit the team" interview. Others…

If it replaces the "coding on a whiteboard" part then it was definitely worth it to me.

I would prefer to waste 20 minutes on a whiteboard exercise than 3 hours on a take home exercise.

Re: Take-home interviews

#252
I dont really understand the way interviewing is set up in general. Interviewing in my mind is a two-way street. It’s not just the candidate that’s being interviewed for the job, it’s also the employer being interviewed to determine suitability.

In light of this, I think most interview processes don’t make any sense. I think that a screening phone/Skype call makes sense before either side commits any time/resources etc. In this process, I think there should always be room for the candidate to ask questions of the employer. Any situation that is unbalanced, in which the employer is playing the role of the one with the final decision is a completely skewed setup.

I interviewed a while back with a YC company and although I didn’t get the job, I was highly appreciative of the setup. Firstly, there was a Skype/phone call, which felt really like an open conversation; one in which I was free to ask questions and understand suitability too.

Then I was invited to an in-house hack. Essentially, I spent the day (a Saturday) hacking with the founders on a project. The project was a lot of fun and something that I learned a ton from. We actually ended up working till around 4am the next day. What I really appreciated is that although it was “an exam” for me, the investment of time on my part was weighed equally by their time investment. Also, I was happy to know that they had learned things during the hack too. I was at ease during the whole day precisely because they treated me as though I was their colleague already.

Coming out of that experience, I’ve wondered for a while why employers don’t take the stance that to hire excellence you have to commit time and resources. Most interview processes that I’ve heard of seem to be a cop out on the part of the recuiter/interviewer, in the sense that it seems that the priority is to hire the best people but spend the least time doing it. That to me is the ingredient for a broken process.

So, in a nutshell, I think talk of take-home interviews misses the point. It might not be scalable, but my intuition tells me that it would be much more effective to have the interviewee and company folks hack on something together. That way, the interviewee gets the opportunity to essentially interview the company too. I’d definitely preceed this with a few conversations on the phone/in person, to ensure that the time investment of hacking together is geared towards the best interviewee/company relationships.

Perhaps this is missing the point too, and perhaps it’s not workable in the real world. My anecdoctal evidence is simply that have spent an entire Saturday working on a project as part of an interview process and ultimately not getting the job, I don’t feel I wasted any time, nor do I feel bitter about it.

Re: Take-home interviews

#253

From the employees' perspective: Take home tests are the worst. Company says take home test will take 3 hours to complete. They never do. Schedule 2x or 3x the estimate. Especially if you want to impress the reviewer. You send it over, then the company says no or yes, only to move to new stage. In the worst case you ruined your weekend and received a no. But the company just took 10 minutes to arbitrarily reject your…

That topic ("People do stuff at home for an interview") is a topic that comes up again and again. My last reply [1] is about a month old and feels still valid. Don't state that 'take home tests are the worst'. That is - failing to find better words - crap. If that is the ONLY option, I understand that this might be not for you. But - that's not the case here as far as I can tell. You, as a person interested to interv…

I absolutely agree with your linked comment - I love these small tasks; even when I get rejected afterwards I still enjoy having done them.

Re: Take-home interviews

#254

From the employees' perspective: Take home tests are the worst. Company says take home test will take 3 hours to complete. They never do. Schedule 2x or 3x the estimate. Especially if you want to impress the reviewer. You send it over, then the company says no or yes, only to move to new stage. In the worst case you ruined your weekend and received a no. But the company just took 10 minutes to arbitrarily reject your…

My wife is not a technologist. In fact, she's a biologist & nurse who's worked in pharmacoviligance for a series of pharmas & CROs past ~15 years. She was laid off this spring after her company was purchased and went through the whole interview thing. One company had a writing assignment as part of their process. It was after both the phone screening and the in person interviews, and they only gave it to candidates they really liked/wanted, AND it was literally a mini version of the kind of data analysis and reports[1] she'd be doing in the job.

But ... it was something that took about 40 hours to complete, and ruined about a week and a half of family time. Thankfully she got the job, but if she hadn't it wouldn't have been pretty.

[1] http://onbiostatistics.blogspot.com/2013/07/periodic-safety-...

Re: Take-home interviews

#255

From the employees' perspective: Take home tests are the worst. Company says take home test will take 3 hours to complete. They never do. Schedule 2x or 3x the estimate. Especially if you want to impress the reviewer. You send it over, then the company says no or yes, only to move to new stage. In the worst case you ruined your weekend and received a no. But the company just took 10 minutes to arbitrarily reject your…

My wife is not a technologist. In fact, she's a biologist & nurse who's worked in pharmacoviligance for a series of pharmas & CROs past ~15 years. She was laid off this spring after her company was purchased and went through the whole interview thing. One company had a writing assignment as part of their process. It was after both the phone screening and the in person interviews, and they only gave it to candidates t…

As an outsider, that sets off red flags for me. Sounds suspiciously like unpaid work rather than a take home assignment.

Re: Take-home interviews

#256
post #228
post #194

Earlier quoted context omitted.

My co-worker once found that someone had posted the take home problem on one of those freelance job sites. Needless to say we didn't move forward with the candidate.

If they can get the take home problem solved for a reasonable cost and in short time on the freelance job site, hire them as a manager.

I'd even say: if they can get the problem solved for less than their salary and in reasonable time, hire them anyway - you're hiring them to solve programming problems, not to type them.

Re: Take-home interviews

#257

Earlier quoted context omitted.

"Problem the 1st: how do you verify the example project is actually the candidate's own work?" Have them discuss the code in depth. Architectural and design decisions, coding conventions, alternate approaches they rejected, etc. Pretty hard to fake this if they didn't write the code. "Problem the 3rd: evaluating a large, unfamiliar codebase is actually really hard." Good chance to assess the candidate's ability to do…

Yes, but that switches the cost back onto the company instead of the employee.

That's how it should be.

Re: Take-home interviews

#258

Seems good, I like the choice. In discussions on this topic I see a lot of: "Programming on the spot is hard, let people program at home"! But then other people say "Why should I program for free at home, my resume clearly shows I am already a skilled programmer. All this will do is cater to young people without families, or those fresh out of school". I am not looking to hire devs right now, but I am thinking about…

I recently graduated from college and started looking for my first programming jobs. I ran into a ton of these "take home" interviews and they were some of the most stressful things I've ever done. The first one, they asked me to solve an incredibly complex math problem that I had no idea about so I struggled with it for 5 or so hours before giving up. Probably good that they didn't give me the job; if they were expe…

I'm sorry that people are reluctant to name companies in these messages; I would absolutely love to know the companies in your first two examples.

Re: Take-home interviews

#259
Why don't interviewers just have a conversation or is that so totally lost these days? I find it a whole lot easier to just ask the right technical questions in the first 2 mins. to decide on hiring.

I keep seeing more and more dis-associative non-communication being presented where the interviewer attempts to do less and less. Its lazy and a crap way to treat people.

Re: Take-home interviews

#260

From the employees' perspective: Take home tests are the worst. Company says take home test will take 3 hours to complete. They never do. Schedule 2x or 3x the estimate. Especially if you want to impress the reviewer. You send it over, then the company says no or yes, only to move to new stage. In the worst case you ruined your weekend and received a no. But the company just took 10 minutes to arbitrarily reject your…

I've had an opposite experience, but with just one company: CloudMine. They gave me a personal and technical interview, then a project to add a feature to their existing codebase. They paid me $300 for my work. I was way over time estimates and I didn't get the job, but I will always respect them for that.
Post reply on HN