The process was generally fine and the questions weren't extremely difficult. But the environments where technicals were done were very frustrating. I was asked code in a Google Doc and design a system in another massive multipage doc. The only place I did have a coding environment did not allow any sort of execution, and this was a UI heavy problem. Some people are visual executors, and need a feedback loop to perform well. I think it's silly to handicap someone this hard in an interview - it's not reflective of day-to-day work and it's unnecessary friction. Some of the interviewers need more training - sometimes the "shadow" interviewer was better and could follow my flow. The main interviewer for the system design was very judgmental and couldn't grasp the idea that I start at a draft and iterate on it. They hyper focused on initial solutions and stopped me and prodded way too much during the iterative stage. The recruiter was the highlight of the process probably.

A recruiter reached out to me on LinkedIn and invited me to schedule a call. They asked me about my experience and background. Then I moved to the next stage, which is basically the same, but with another recruiter. Then they told me that the next stage would be a call with the hiring manager and they would ask behaviour questions. The interviewer asked me one behaviour question and then proceeded to a technical interview, in which I was asked to write React code and they also asked me questions about JS (what a function would return). The process seems to me disorganized. If you are going to do a technical interview, you need to let the candidates know, so you are not surprised by the questions.