Hacker News new | ask | show | jobs
by Bahamut 3274 days ago
A take home assignment alone is likely more than a work day, if not multiples - I'll take a 7 hour onsite interview gauntlet over that any day.

The only side this process seems to be favorable for is the company interviewing.

To give a flip side, I just finished interviewing with over 10 companies in a rigorous search. Of those, two did take home tests, and ultimately I didn't have the time to complete either, especially since the requirements were written in a way where candidates were encouraged to dump a lot of time into them. My schedule was filled with many high stakes interviews, which was mentally exhausting. It simply is not in my interest to do a take home project, as it reduces the number of companies I can simultaneously interview at.

1 comments

From experience we saw that for most people doing the coding test was only taking ~an evening which seems reasonable as it removes the need for more on site discussions.

I guess that it's true that the take home assignment is not optimal if you interviews with more than 10 companies and in this case we must be loosing some candidates.

They lie. Most candidates will tell you the coding exercise took less than it actually did because 1) they want to appear efficient 2) you said it would take only 3 hours so if they say it took 8 hours it would look like a failure

Source: me, last week, for another company. Plus, programming is not just writing code, most technical interviewers will want to see the global design, unit tests, comments, etc... Which are not accounted for in the expected time