I recently went through a 5-step interview process for a Full Stack Developer role. The steps were: CV screening Phone call – to confirm availability Case study – building a full-stack app with Vue and Node.js HR interview Technical interview (if you pass HR) After completing the case study, I advanced to the HR interview. However, I was rejected afterward. When I asked for feedback, I was told that my qualifications weren’t suitable and that they were looking for a more senior candidate. Normally, I wouldn’t have an issue with this. But here’s why it felt frustrating: Job description mismatch: Nowhere in the listed qualifications did it say they were looking for a senior developer. The requirements only included basic technology skills—nothing about large-scale systems, leadership, or senior-level responsibilities. Could’ve been filtered earlier: If seniority was the main criteria, this could have been identified at the CV stage, saving me (and them) the time. Timing of rejection: If they had doubts but wanted to see my technical abilities, it would make sense to reject me after the technical interview. Instead, I was eliminated after HR—after already investing a week into their case study. I’m not the only one who experienced this. A friend of mine applied for the same role. He also spent a week on the case study—carefully planning the architecture and building out a strong solution. In the end, his submission wasn’t even opened before he was rejected after the HR round. This kind of process feels wasteful and unfair to candidates. If the company is truly looking for senior people, that should be communicated upfront, and their hiring funnel should reflect it. Otherwise, candidates end up investing significant unpaid time into case studies that may never even be reviewed.