Takehome projects are typically one of the first steps in the frontend/mobile/full-stack recruitment process, after a call with the recruiter or hi...
For further actions, you may consider blocking this person and/or reporting abuse
From half a century of interviews in past 11 months, I'd also like to add that one should definitely if it really qualifies as a take-home task I've had several with me and my juniors that all they wanted was a base code repo for their product. Though I know I shouldn't cry but such bad experiences have put me in a emotional turmoil
In my experience reviewers also look at things other than just how well someone can code. Coding can be learnt but having good attention to detail and a solid problem solving attitude is harder to come by. At Rexlabs we ask the interviewee to make notes and have a few questions around how they plan to complete the test. We also look at; problem solving skills, the reasons behind which problems were solved first and why in a particular order, which external libraries were added and how they decided upon a specific library, how comfortable are they with git and what kind of commits have they made.
The code is a good indication of how comfortable they are with a language or framework, but it doesn't cover if they are a good fit. Also, a senior might be a great programmer but not under a time restriction which will essentially cause them to make more mistakes than usual.
So to recap, I think having extra questioning as apart of the code test is key, the answers should be submitted with the test so that it's fresh in their mind. Answering these questions during an in-person interview can be daunting and they might have forgotten by that point.
Welp literally just submitted a takehome project and now I wish I could redo the whole thing 😩
Fingers crossed, Lynn! Regardless of how a takehome project goes, you usually learn a lot from it, when you get feedback. If you get to the next round - hooray! If not, then hopefully you get specific feedback on what parts to improve on. And if no feedback, it's fair to ask about what parts were missing.
I hope it goes well for you.