The online interview process was overall positive, starting with an take-home-assessment conducted prior to the interview. The assessment itself was straightforward, and I performed WELL on it. However, it felt pointless to invest time and effort into it, only to find that doing well didn’t translate to receiving an offer. It raises the question of why the assessment was even necessary if it wasn't going to be a significant factor in the selection process. What’s even more frustrating is the reliance on basic technical trivia during the interview, such as being asked about the differences between let and var. These types of questions seem out of touch with the realities of modern development. Who remembers such nuances off the top of their head when coding? In practice, developers rely on their tools, write functional code, and turn to resources like ChatGPT or documentation when needed. These questions don’t reflect problem-solving skills or practical abilities, which are far more critical for success in a role. Instead of focusing on trivia, it would be much better to evaluate candidates based on their previous portfolio and real-world experience. Reviewing past projects, contributions, or solutions they’ve worked on gives a far more accurate picture of their capabilities and potential fit for the role. The current approach feels like it’s designed more to trip candidates up than to assess their real-world skills or potential contributions. If the process continues to focus on theoretical or outdated knowledge, it risks overlooking strong candidates who could bring real value to the team.