The interview experience was disappointing. It was a 45 minute interview. The interviewer seemed unsure about what questions to ask, eventually requesting that I write boilerplate code, despite only asking two questions beyond my background introduction. Although I provided the necessary details for implementing the code, the interviewer appeared dissatisfied. This reflects a backward approach to interviewing, focusing on recalling boilerplate code—often handled by frameworks—rather than evaluating problem-solving abilities. An effective interview should foster a conversation that assesses a candidate's proficiency in relevant technologies and their approach to solving problems, not how well they can memorize code typically imported from libraries. No wonder people with strong problem-solving skills often choose not to join such service-based companies. Given the available options, I will select "very easy," though the experience was best described as "strange."