The first round of the interview was technical, and the interviewer was very friendly and helpful. He asked me a couple of theory-based questions about the MERN stack, which went well. For the second round, they sent me an assignment to complete. However, this is where things got tricky. As a company, it’s important to understand that the person attending your interview is likely already working elsewhere and juggling multiple responsibilities. The expectations for the assignment were quite high—it required building a full-stack application based on a Figma design. While I understand that such assignments are a great way to evaluate a candidate’s skills, building a complete application of this scale in just a few days is unrealistic. Applications like this often take teams months—or even years—to develop. Expecting a single developer to deliver a fully functional solution within a short timeframe, especially when they might also be involved in other interviews, is a significant challenge. Here’s a suggestion: While assignments are indeed an effective tool to judge a candidate’s abilities, they should be designed to be achievable within a few hours. Assignments that demand 3–4 days of work can be overwhelming and counterproductive. A more practical approach would be to create smaller, focused tasks that effectively showcase a candidate’s skills without consuming an excessive amount of their time.