Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
I hate those kinds of assignments. I had one that was 12 hours too.
It involved some tasks to implement a number of different end to end features with some rules about how to do them. Estimate them before hand and keep a log of what issued I had found and updating the remaining work on each task as I committed.
It was basically impossible, and to top it all my keyboard packed in half way through.
The exercises are supposed to show them how you work.
But if they are a two way thing and that is an indication of how they work then they must be working under a load of pressure.
Related Rants
Stackoverflow.
I was given a take-home assignment during the interview process of a startup.
They gave me a vague 24 hours to complete it and submit it the day after.
The instructions read like - most candidates don't complete the assignment, so if you finish 70%-80%, that's good enough.
I read the instructions; I was supposed to follow the "mock design" they sent me. It looked a tad bit ridiculous. But still, I thought I'd be able to finish most of it.
I worked on it for around 10-12hrs total (including procrastination because it was such a slog). I finished most of the "features" they mentioned, so about 70%-80% done.
I submitted it the next day. They got back to me saying they're not moving forward because they expected more features considering 24 hours.
🤨
They didn't expect me to spend 24hrs on it, did they?
I learned a few things, so I guess it wasn't a complete waste of time.
rant
some bs
interview
frontend
job hunt
assignment