I was invited to complete a technical assessment as the first step in the process. While I appreciated the opportunity to showcase my skills, the experience was frustrating due to a lack of communication. I had several questions about the task, including whether I should generate my own sample data, but received no response — only later discovering that the team was out of office during the key period. This information wasn’t communicated ahead of time, which led to unnecessary time spent making assumptions and solving problems that might not have been needed.
After submitting the task by the deadline, I received a generic rejection email with no feedback. Only after I followed up and expressed concerns did I receive a more detailed response. While I appreciated the eventual feedback and acknowledgment of my effort, it shouldn’t require prompting from the candidate to get it.
The process felt disorganized and left me wondering whether my work had been properly reviewed before the decision was made. If you’re asking candidates to invest significant time in technical tasks, it’s important to provide timely guidance, set clear expectations, and ensure that feedback is a standard part of the process — not something that happens only when someone pushes for it.
