Interview Experience – Disappointing and Inconsistent Feedback Interview Process: Initial Call: Screening with a recruiter. Technical Discussion: A conversation with the team lead. Take-Home Assignment: Implementing a feature within a suggested time frame. (Would Have Been) Assignment Review: A discussion on the take-home assignment, which unfortunately never took place. My Experience: Unfortunately, my experience with the interview process was quite negative due to inaccurate and inconsistent feedback on my take-home assignment. Incorrect Review Comments: The reviewer incorrectly stated that I had used Material UI when, in fact, I had used Tailwind CSS. This raised concerns about the accuracy of their evaluation. Conflicting Expectations: The assignment instructions explicitly stated to implement "at least one feature" within 3-4 hours, yet the feedback criticized me for implementing only one. If the expectation was to complete multiple features, it should have been communicated clearly. Lack of Awareness of Given Constraints: The reviewer seemed unaware of the constraints shared during the assignment, including the explicit mention that tests were not required. Given the 3-4 hour limit, expecting a fully tested, production-ready implementation felt unreasonable. Misjudgment of Implementation Choices: The use of useShallow from Zustand was labeled as "over-engineering," despite the fact that removing it would break the app. This suggests that the review process lacked technical depth and proper evaluation. Key Takeaways: I left with the impression that the review process was not well-structured and that the feedback was neither fair nor aligned with the given instructions. Advice for Future Applicants: If you're considering applying, here are some things to keep in mind: Write a Detailed README: Document everything explicitly, even the most obvious decisions, to avoid misunderstandings. Over-Deliver on the Assignment: The PDF instructions say to implement at least one feature—ignore that and implement all features if you want a fair shot. Ignore the Time Limit: The official guideline says 3-4 hours, but to meet their unstated expectations, be prepared to spend 8-10 hours implementing all features and writing tests, even if they claim they are optional. Clarify Tech Stack Usage: If you're not using Material UI, explicitly state it in the README—apparently, assumptions will be made otherwise. Final Verdict: Based on my experience, I would not recommend applying. The interview process felt misaligned, and the feedback lacked accuracy and depth. If you do apply, be prepared for unclear expectations and ensure you go above and beyond the stated requirements.