4 ms·

This is one of the reasons, I prefer small take home assignments which can be later discussed with the interviewer about the pros and cons of the decisions made

This is one of the reasons, I prefer small take home assignments which can be later discussed with the interviewer about the pros and cons of the decisions made during coding. As an interviewer, you get more insight into what the candidate was thinking and whether they were able to actually implement something end to end. Leetcode style problems rarely give you that signal from candidates.

Trasmatta 6y ago
I've done those before, and found the employer always underestimates how much time they should take. I think it's a good idea, but I've done 3 where the employer said "this should take 2-3 hours", but I actually had to spend an entire weekend on it instead. Felt like a waste of time, especially for the ones I didn't even make it to next phase in.
- deleted 6y ago
  [deleted]
- garbene 6y ago
  Absolutely, every job states it should take a few hours but it NEVER takes a few hours if you want to deliver something that’s remotely competitive. My current role’s take home was suppose to take “a few hours”, took the entire weekend. But hey, it worked out.
bitbuilder 6y ago
As a hiring manager who was once a developer who was absolutely terrified of the typical whiteboard/algorithm interview, take home assignments are my preferred method to judge tech ability. However, I often feel it's not fair to ask the candidate to invest their personal time in the interview process. So I'm glad to see some affirmation that it's the preferred method for at least some. When I have done take homes, I've tried to keep the time requirements minimal and the project itself simple and hopefully even a bit fun. It might even be as simple as "here's a REST endpoint, pick the JS SPA framework of your choice and do something interesting with that endpoint." Even just a simple form with clean code that builds will be enough to get you hired if you're otherwise a good candidate. Because in the real world, most of of us are just building CRUD apps. All that said, I only bother with this if the candidate is incredibly green. For anyone with decent experience I generally assume they're not lying on their resume, and an hour long chat about their projects and technology interests will tell you more than any technical assessment.
deleted 6y ago
[deleted]

Trasmatta 6y ago

I've done those before, and found the employer always underestimates how much time they should take. I think it's a good idea, but I've done 3 where the employer said "this should take 2-3 hours", but I actually had to spend an entire weekend on it instead. Felt like a waste of time, especially for the ones I didn't even make it to next phase in.

deleted 6y ago
[deleted]
garbene 6y ago
Absolutely, every job states it should take a few hours but it NEVER takes a few hours if you want to deliver something that’s remotely competitive. My current role’s take home was suppose to take “a few hours”, took the entire weekend. But hey, it worked out.

bitbuilder 6y ago

As a hiring manager who was once a developer who was absolutely terrified of the typical whiteboard/algorithm interview, take home assignments are my preferred method to judge tech ability. However, I often feel it's not fair to ask the candidate to invest their personal time in the interview process. So I'm glad to see some affirmation that it's the preferred method for at least some. When I have done take homes, I've tried to keep the time requirements minimal and the project itself simple and hopefully even a bit fun. It might even be as simple as "here's a REST endpoint, pick the JS SPA framework of your choice and do something interesting with that endpoint." Even just a simple form with clean code that builds will be enough to get you hired if you're otherwise a good candidate. Because in the real world, most of of us are just building CRUD apps. All that said, I only bother with this if the candidate is incredibly green. For anyone with decent experience I generally assume they're not lying on their resume, and an hour long chat about their projects and technology interests will tell you more than any technical assessment.

deleted 6y ago

[deleted]