|
|
|
|
|
|
by pertminus
2504 days ago
|
|
|
I've done one take-home project for a job and it was a terrible experience. They gave me an overnight challenge that in their words was meant to confuse you and was impossible to complete. They informed me I should have realized this and focused on one specific area of the challenge. I spent all night trying to complete it, focusing on a "pace over perfection" approach and then was torn about by their dev team. Of course I explained there would be a difference between a DB, Server, & UI I implemented overnight and what I would do at work. They informed me I was too defensive, attempted more of the challenge than anyone, and that I wouldn't get the job. tl;dr: I feel you completely and will never waste my time like this again. |
|
|
Come on. It's not completely unheard of to be given confusing or impossible requirements while working for some companies and while in those situations I would probably just communicate back to the Business Analysts what's broken about the ask, you aren't given that opportunity in a take-home with a new company. Presumably a bunch of other people have been given the task and successfully completed it, so I would probably try to power through it.
I'm sorry, but that's an asshole thing to do to someone. In an interview setting it's more okay, because you have a chance to mention it after a few minutes and talk it out and get feedback on it or they can stop you if it's clear you're not pointing that out and you waste a bunch of time, but with a take-home you won't get that quick feedback, even if you send them an email, and can waste hours and hours on that thing.
Interviewers reading this, don't do this, please. It would leave a very bad impression on me and probably a bunch of other people about your company.