No Leetcode style questions. Phone screen, then 1 hour coding interview. You will receive a small repo and be asked to find and fix bugs. The final round is four interviews. A few days before the interview, I was given a prep call to answer any clarifying questions I had. The interviews in no particular order: 1. 1 hour coding. You will be given a repo of code, but instead of debugging, this time you will be asked to implement a new feature. 2. 1 hour system design. I was told in an email that this would be a front end design, and when I asked the recruiter about this in the prep call, they said that it wasn't a system design/system architecture question, but would be more about front end components and how they would work together to create a cohesive front end. However, when I got to the interview, it was a standard system architecture/API question that was all backend and no frontend at all. When I brought this up to the interviewer, they said that they are looking to hire more senior people and therefore all their system design questions are backend, and that the frontend task I was expecting was miscommunication. Interesting, since there was only 1 business day in between my prep call and interview. 3. A 45 minute behavioral "company values" interview, where you answer specific questions outlined in a prep document that you are given beforehand. 4. A 30 minute behavioral with the head of engineering or someone of similar level. This was the most chill interview. I was asked to talk about a project I worked on. Also expect a few more company values questions if there is time. Overall I liked how their interview process is based more on real life coding, and didn't require an insane amount of prep. They also moved very quickly since they knew I had an offer deadline coming up. But the miscommunication with the system design should be smoothed out, especially since for more junior engineers, that is the hardest interview to prep for.