I 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 invol

I 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.