The process started with an interview with the recruiter. It was a standard screening interview – questions about my experience, expectations, and a brief overview of the team. The recruiter was pleasant to talk to. The next stage was a test on the HackerRank platform. Unlike some of the previous reviews, I actually think the test was well put together and covered the essentials of JavaScript, React, and general web technologies. There wasn’t a single question that felt irrelevant to the role. The next stage, however, was the technical interview, and that was a complete disappointment. First, I had to find and fix bugs in a React application, all done in CodePen.io. One of the “bugs” was that the endpoint URL started with “htpps” instead of “https.” I honestly don’t understand what kind of skills this is supposed to test. To me, that’s just silly—there are plenty of more meaningful ways to test API-related knowledge. But what disappointed me the most was that I applied for a React role, yet I was interviewed by an Angular developer who asked questions that were far more relevant to Angular than React. For example: “Explain what the ‘D’ in SOLID stands for and how it’s used in React.” I strongly believe that for a React position, candidates should be interviewed by someone who actually works with React. In the end, I was rejected and received no feedback whatsoever—just silence, even after I asked for it.