Extremely convoluted interview process. Initial hiring screen, then EM call, then pairing exercise with devs, then system design and behavioural, and then what seemed to be an additional call with a senior leader? The recruiter was transparent about it, to be fair. But I wouldn't have proceeded if asked to, the company is operating Meta level interview processes for a product that is barely seen in the wild. As if the red flags from the interview process weren't enough already. The recruiter explained to me that they don't have teams, just lone wolves, working on projects on their own. I think you can imagine what state the codebase will be in. A company in this state, and of this size, cannot warrant a process like this. I was rejected after the hiring screen for not having enough experience.

I think overall it's pretty good. They give you as much information as possible during the interview process so you know what to expect. Everyone was pretty nice and i enjoyed the experience. I got rejected at the technical assessment stage. They act as a pair programmer and will implement the code based on your instructions. My number one tip is: DO NOT try and understand the codebase, they want implementation; focus on excution not understanding. Go bottom up and dont go too far up the component chain. I wanted to understand how the code works from a hollistic perspective but that's not what they're looking for.