3 ms·
I always thought the idea of a take-home sounded appealing, especially when I first heard of them ~15 years ago. The first time I found a bug in a company's ta
by majormajor 4y ago
I always thought the idea of a take-home sounded appealing, especially when I first heard of them ~15 years ago.
The first time I found a bug in a company's take home project spec rather spoiled them for me. And sadly, that's not the only time that happened! A candidate who puts more effort into it than the person who created it gets rewarded by feeling confused or like they're missing something because it doesn't add up? Nope, not great.
And now, 15 years further along, the idea of investing 4+ hours of my own time without even a human to ask questions of or discuss things with just has no real appeal (I've seen some that expect 8+, even).
- wombatpm 4y agoWhat is a waste is interviewing for a Sr backend python role and being given a timed online test to implement a linked list class scratch. IF I ever needed a linked list, I’d use collections.deque like a professional.
- coffeebeqn 4y agoSeems like these days it’s that or 4 hours of leetcode which is even worse
- Aeolun 4y agoHmm, yeah. I updated some assignment with a super legacy library to a new one, then got dinged for issues this highlighted in the original code… Oh, and they took issue with the fact that my files were named in CamelCase instead of smake case. Overall I think any form of take-home/leetcode is just depressing.