DEV Community


Discussion on: The process of the technical interview - A perspective from CTO's, VP's and Directors of Engineering

scottshipp profile image

Another reason was the time saving that comes with the take home, and engineers not having to spend 30 minutes to 1 hour on a live coding interview.

Unfortunately, it saves the company's time but it wastes the candidate's time in most cases. It'd be valuable for people to consider this from a candidate's perspective. Candidates can do four one-hour phone screens with four different companies and increase their surface area to offers in the same time it takes to do one single "take-home" assignment that lasts four hours.

lukewduncan profile image
Luke Duncan Author

From all my research and talking to these folks, take-home projects come after the the initial phone screen and at least some kind of technical assessment (mostly through conversation with an engineer and explanation of past projects from the candidate). Also to play devils advocate, if they are close to the final stages and it is a take-home, I would think 3-4 hours of GOOD work is worth it for the engineering salary.

If your thoughts were candidates doing take-home assignments right off the initial phone-screen with a recruiter, then I definitely agree with your point. But if they have had a phone conversation with an engineer who can technically vet them and they are on the closing rounds - then I don't think it is a waste of time on both parts. Especially if it is a company the candidate wants to work for.