The entire interview process took around two weeks. It started with an initial CV screening, followed by a technical interview with one of the developers, and finally a take-home task with a four-day deadline.
While the process seemed structured, the overall experience was quite disappointing. Candidates dedicate valuable time and effort to completing detailed take-home challenges — often outside of working hours — only to receive a generic rejection like “due to the high volume of applicants…” without any specific feedback. That kind of response feels dismissive and shows a lack of respect for the effort candidates put in.
My suggestion to the team: even a minimal amount of constructive feedback would make a big difference. For example, mentioning areas such as testing not being comprehensive enough, missing edge cases, weak error handling, architectural concerns, or over-engineering would at least give candidates some value for the time they invested. It doesn’t take much, but it shows professionalism and respect.
If you don’t have the bandwidth to review submissions properly, please reconsider assigning time-consuming take-home tasks — and avoid spamming a long list of candidates with the same exercise if there’s no intention or capacity to evaluate them fairly. Transparent communication and even a brief, thoughtful review go a long way in leaving a positive impression, even when a candidate isn’t selected.
