[ro_bit]

One note that might be good to highlight in the article is that the take-home is expected to be 2 hours long. From my experience, they are much longer so I was initially surprised to see take-home's being given before an initial call until I looked at the assignment itself.

[kassner]

I still consider this a red flag. The company wants me to put time into the hiring process, but they can’t be bothered to do the same.

If there is at least a recruiter screening first, I’ll apply and ask about “Bring Your Own Code Examples”, mostly when their daily work would use tools that I have some code published.

[joshdavham]

> I still consider this a red flag. The company wants me to put time into the hiring process, but they can’t be bothered to do the same.

Exactly this.

It costs a company nothing to give you a take-home, but it will cost you (the candidate) potentially many hours. On my last job search, I got burned a number of times where I'd work for hours on a take-home only to get ghosted. I don't think they even looked at my solution.

Now I have a personal policy where I will refuse to do a take-home unless the interviewer sits there with me while I do it. This demonstrates to me that the interviewer is actually serious and respectful of my time.

[resonious]

> but they can’t be bothered to do the same

They will need to review your submission, which absolutely does take time.

[matusp]

I can see both perspectives. If you are a skilled hiree, this seems like a waste of time. But if you are hiring online, you will inevitably get a lot of terrible candidates and you need to filter them out. If you are a small team, you can't spend weeks interviewing randos with little to none coding experience for a SE role. The problem is that online hiring is full of noise, but both sides suffer from the expenses this creates.

[preciousoo]

Click the link of the take home and tell me if you expect it to take you more than 20 minutes. I don’t understand the resections here