The process seems normal at first: recruiter screen then chat with a manager. It takes a turn at the coding assessment, which is by far the strangest and most difficult. There is zero collaboration, the interviewer will even turn off their camera. I believe this is more of a psychological test than a coding one, because the only tests you need to get passing are the end result of a lot of work. There are no tests along the way like you would actually write when working. So it feels very pass or fail and an intentional stress point while you are working on the solution.

Recruiter screening, then VP of engineer, then they will request that you schedule a cultural and technical interview at the same time. Seems like a bad practice and a bit of a waste of time. If you do bad on the one, there would be no point in completing the other. I setup the scheduled to do the cultural and then technical. Should've done the technical first so I wouldn't have wasted my time with the cultural interview. Cultural interview was pleasant enough and made me believe that they would be able to actually look beyond random leet code challenges to understand someones skills and abilities. I was wrong lol. Technical interview they ask to write two classes for a sudoku solver. Anyone solving that within the interview window has already solved it and is just copying their code over. I solved it ahead of time and it took me beyond the 1 hour time window they give you (actually you have less time because you are doing the greetings and reading the instructions). Still didn't finish it in the interview because I was trying to show how I solve problems and go about trying to break down the problem and troubleshoot different issues. This was the wrong choice, they want someone that will just run through it and solve to their tests. Don't waste any time logging anything out and showing your process, just write out all your methods correct the first time. Honestly your best bet is to probably just copy the code you write ahead of time to solve it. They don't really communicate with you during the challenge so they are not trying to get to know how you work, or go about problem solving, or understand your process, they are just looking for the end result.