The interview process itself started with a simple phone screening from HR. Simple. Then a takehome which was basically "create a sleep function in JavaScript." Simple. Then a talk with the HM to talk more about the role. Simp--- oh wait. The HM did not even show up for the interview. Some software engineer in their stead showed up (a few mins late) but she did a fantastic job as an interviewer. I couldn't really ask too much since she'd only been at Unannet (or GovPro AI) a while. Then it was basically, how would you make an algo on a ride share program create a route with the best money making ability. We talked about it. And that was that. Fun. Simple. Then, a few days later, came the actual technical assessment. This time the actual HM showed and another software engineer. After some introductions they got into the problem. They wanted me to code an algorithm that took flights and create the shortest path to direct airplanes from which airports to make, basically, an airport routing system. Then we're going to code it. I laughed -- like, are they kidding? It was a leetcode type question. You have to study those types of questions to pass so naturally, since I wasn't ready, I did not pass. Well, actually, after about 45 minutes, I realized that this was not the best way to represent my skills and for the first time in my career excused myself from the interview and I ended the interview saying that you are looking for someone obviously with 15+ years of experience or someone who's studied this problem. I could not believe that they thought this was the best way to assess a candidate's ability. There's a reason that leetcode-style problems are a controversial topic. LeetCode is controversial due to its overemphasis on algorithmic and data structure problems, which critics argue are not reflective of real-world software engineering tasks like collaboration, design, and debugging. The platform also creates significant pressure for job seekers, who often feel compelled to master these problems despite their limited relevance to daily work. Additionally, LeetCode-style interviews are seen as gatekeeping, favoring individuals skilled in competitive programming while potentially excluding candidates with diverse skill sets. The focus on timed problem-solving further exacerbates the issue, prioritizing speed over deep understanding. You're not going to be coding algorithms from scratch. You're going to be creating fantastic software writing great, reusable components in React. Unfortunately Unanet has yet to receive that message and will try to find their unicorn someday...