←back to thread

369 points surprisetalk | 1 comments | | HN request time: 0.413s | source
Show context
iLoveOncall ◴[] No.45064655[source]
> take-home assignment

That's the point at which I would have stopped the process personally.

replies(1): >>45064790 #
whatamidoingyo ◴[] No.45064790[source]
> That's the point at which I would have stopped the process personally.

Why is that? I love take-home assignments. At least, if it's just an initial get-to-know-you interview, and then the assignment. What I utterly despise is the get-to-know-you interview, then a tech interview with the entire dev team, then a take-home, then a meeting with the CTO.

I will never, ever, ever go through with any job that has an interview process like this again. I always ask up-front what their interview process is like.

replies(2): >>45064922 #>>45064993 #
iLoveOncall ◴[] No.45064993[source]
Because it's time theft?

Why would I spend 4 hours (in the best case scenario, otherwise days) on the very first step of the application process, where, regardless of my resume, I have an extremely high chance to be rejected, while the company puts literally no time in?

replies(1): >>45065081 #
whatamidoingyo ◴[] No.45065081[source]
Well, that's different. If it's a super challenging take-home, with requirements that exceed 1 page, then yeah, I'd agree. Most take-homes that I've received have been super simple, though. And they're usually not the first step, but the final step, in my experience.
replies(2): >>45065116 #>>45069222 #
1. stackbutterflow ◴[] No.45069222[source]
A take home should come with a project already set up that you're asked to modify.

Most don't and they waste your time setting up all the boilerplate.