I fully agree. We don't have anything in place at the moment to stop users from adding private projects that take a huge amount of time to complete, but we are

I fully agree. We don't have anything in place at the moment to stop users from adding private projects that take a huge amount of time to complete, but we are going to spend time on helping to guide customers away from that situation. I think a large reason for people spending lots of time on code projects boil down to two things: 1) the people who create the test never actually do it themselves, and only estimate how long they think it will take, and 2) Companies don't give enough guidance on what is needed and what isn't. If it's too open-ended then how does a candidate know when to stop? We made the decision early on to aim for solutions that work well for both the candidate and the company, but where they conflict, go with what will work best for the candidate. This may seem counterintuitive from a business perspective, but it has served us well and, I think, it is the best way to go long term. Ultimately if we can give a great candidate experience then that's good for the business too.