First round was a technical screener - some basic react and JS algorithm questions. Nothing too difficult. Second round was the recruiter screening. The entire call was fully dedicated to my questions, so be sure to go in with many of them tailored specifically to show that you're excited by what they're building. Third round was the technical assessment - 1 hour call with a senior engineer, ~15 minutes dedicated to talking about your background/why you're interested in ElevenLabs, then the rest of the time dedicated to a "fully practical" live React coding challenge. I put fully practical in quotations because, while yes it is definitely more practical than leet code-esque interviews, you're not actually building something in anything close to a normal working environment. As a matter of fact, you're not actually building anything at all. You're given the skeleton of a React component which renders another component which you're told to assume just works. You're also given a fake ElevenLabs service which exposes a couple of methods via fake types, and nothing more. You're tasked with setting up the fake service in a way that the predefined fake child component will "work" based on the props it's already been set up with. In reality it's much closer to solving a leet code logic puzzle than it is an actual practical build. You're not producing or running any actual working React code, and as such you have no means of experimenting or testing anything to get to the solution you need - it's a lot of theoretical psuedocoding and asking the interviewer for more information. Not particularly enjoyable or applicable to real world working scenarios. Both the recruiter and the engineer I interviewed with were very nice and I enjoyed chatting with them.