The process took 3 weeks. The process began with an initial call with an internal recruiter, followed by a take-home challenge to build a prototype addressing a specific problem statement. The instructions emphasized that UI/design was not the focus, and that the core goal was to demonstrate backend and product thinking.

The next step was a debrief and live discussion of the submitted solution with engineering team members. Unfortunately, this stage felt unexpectedly confrontational and unstructured. While the position was for a backend engineering role, a significant portion of the interview focused on UX-related decisions, which led to repeated questioning and objections, despite the primary goal being backend architecture and functionality. The technical discussion also covered strategy and database design, but unfortunately, the feedback I received included several assumptions that were never discussed during the interview itself.

At times, the interview lacked structure and felt more like an effort to find fault than to explore solutions collaboratively. Some of the personal judgments in the feedback, labeling me as "stubborn" or implying dishonesty, were surprising and disheartening, especially since they were based on perceived expressions rather than actual dialogue. Overall, the process felt biased by interpretation rather than grounded in open conversation or direct questioning. Clearer structure and more objective communication would have improved the experience significantly.

Create an application that helps users find the most relevant recipes that they can prepare with the ingredients that they have at home.