4 ms·
Homework interviews are terrible because they cost absolutely nothing for a company to give. You can spend 4 hours on them and perhaps nobody will even take a
by opportune 5y ago
Homework interviews are terrible because they cost absolutely nothing for a company to give.
You can spend 4 hours on them and perhaps nobody will even take a single look at it, they just gave it to you because why not.
They’re also (IMO) pretty low signal because you could cheat on them easily.
Meanwhile a phone interview (even if algorithms) takes only 60m or less and shows the company is at least invested enough in you as a candidate to have somebody spend that time with you. Cheating is definitely still possible, but harder and more awkward. It just seems better overall.
- Fire-Dragon-DoL 5y agoI agree with that statement, that's why we put the coding challenge to _after_ the technical chat. The technical chat (which is just a chat, no algorithms involved) is performed by a developer, it's 45 minutes chat. Only after that there is the coding challenge. The company is definitely invested by that time. I also enforce the rule of providing feedback, as well as invest an enormous amount of time reviewing and evaluating the submissions (at least 1 hour + time to write down feedback, points to further dig through during the next interview step). And yes, when applying for a job it's the worst. I also have no solution. Removing it would mean making the "full day with the team" even longer and more stressful (I'd rather do less live coding than more). Yes it can be cheated, but that would come up in the full day interview (it did happen), so it's irrelevant, there are multiple filters on purpose, however each filter is more expensive for the company or the candidate and balancing between the two is important. That's also why I think a chat with a developer is important to have as early as possible.