5 ms·
I've talked with applicants about their private projects. It gave me great insights. Also take home tasks with a discussion afterwards are a good thing and can
by fileeditview 2y ago
I've talked with applicants about their private projects. It gave me great insights. Also take home tasks with a discussion afterwards are a good thing and can be an alternative if candidates don't have private projects to talk about.
- Paul-Craft 2y agoOh... take home tasks. Theoretically, I agree these are a great way of generating some signal where there's not enough to be found by other methods. But, in practice, what I've found is that most of these types of exercises are way overscoped, and even those which are not put a hugely disproportionate time burden on the candidate with minimal return for most of them. In other words, nobody wants to take the time to properly review these things. I've had much better experiences when people give me code and ask me to review it rather than when they give me a "spec" and ask me to write code based on it. One big red flag for the latter type of assignment is the phrase "production ready," as that can mean so many different things it's a borderline meaningless criterion. I could really go on and on about this, but I'm going to stop here.
- fileeditview 2y agoI absolutely agree with you. There are many take home tasks that are way overblown and expect too much. But I am convinced that you can scope it for say 1-2 hours and I think that's a reasonable time investment for an application. And yes the interviewer has to review that stuff and ask good questions but nobody said this was easy. But for me it showed better outcomes than the usual live leet code interviews.. (I did them too).