|
|
|
|
|
by oaththrowaway
525 days ago
|
|
I know some people hate take-home assessments, but for me it's a total life saver in interviews. I don't "think" out loud while I'm working, and there's no way in hell I'm doing it nervous while someone is looking over my shoulder. Using Leetcode as a filter is great if you're looking for someone who interviews often, but in my experience it's not a great gauge if someone is a good engineer or not. As a hiring manager we've tried implementing different strategies. On my team, we hired 4-5 engineers doing live coding exercises similar to leetcode, and none of them made it more than 6 months. We switched to a take-home project for the last 3 we've hired and they've all been with us for 2+ years and have been great. Of course with the take home projects you're filtering for people who are willing to take a few hours of personal time to work on something, but over the interview process it seems like it washes out? Of course this is just anecdotal data on a fairly small team, but I hate LeetCode style interviews. |
|
I ended up not taking the job due to the combination of a counter-offer from my employer as well as being a little weirded out by their culture. But I was thankful to get the opportunity to show my skills in a way that worked for me.