[crackinmalackin]

I'm in between jobs at the moment and a lot of people here are commenting with some very reasonable hiring practices that I actually haven't seen out in the wild yet. From what I'm seeing, the take home assignment process is getting out of control.

The take home assignment process seems to vary wildly between different companies. One place wanted me to complete a take home assignment that was estimated to take between 30 - 40 hours. Another startup had me come in for a 3 hour interview, and then asked me to take home assignment after the onsite interview. Hard pass.

I think I still prefer the take home assignments over the leetcode misery. But, candidates like myself will quickly find themselves having to pick and choose which ones they want to complete because some are just asking way too much.

[SauciestGNU]

I just came out of the job hunt, and I disagree about preferring take-home tests to leetcode. I much prefer the timeboxed leetcode scenarios to a project with no defined end aside from the specifications. The expectations for the takehome never seem chasee to me. I might solve the exercise in 4 hours, but how do I know the other candidates aren't pouring days into the exercise? Leetcode with a time constraint allows me to prepare for a known quantity.

[crackinmalackin]

People grind leetcode problems for weeks or months ahead of time though.

Most take assignments are throwaway code, but once in a while they are things you can add to a portfolio and expand on. Also if you finish and need to reaapply to another position you’re already done.

Definitely a time consuming practice, but i like knowing what I’m getting into versus the mystery of leetcode. Short and sweet is the key though. Someone else mentioned live pair coding on some revelant feature , I think those are ideal