5 stages: Initial screening, tech interview, and then in one day: 1hr pairing, 1hr system design, and 20m chat with head of engineering. Cassandra was my talent acquisition partner and she was very transparent and helpful throughout the whole process. I was given feedback on each stage too. For the pairing and system design part you are given a codebase to familiarise yourself with beforehand then it’s all based on that. They are looking for proof of test driven development, lots of clarifying questions throughout, showing your thought process, and the ability to keep the customer experience to drive decisions.

First 30 minute screen with HR, general behavioural questions. Then had an hour long interview with engineer that was mostly about deep dive into projects, and some more behavioural questions. The final stages consisted of an hour of coding, systems design and then 20 minutes with a engineering leader, which was just another general behavioural qs. The coding part involved cloning a repo in advance and then making a bug-fix. The actual code change is a trivial one liner, but they really care about doing TDD, so _do not_ change the code first, first write _both_ new integration tests and unit tests which should fail for the existing code, and then do the changes, which is what I failed at as I was focused on updating the unit tests. The systems design is based on making extensions to the repo you cloned, so do a quick overview of the design before the interview. Otherwise q's were pretty standard, focus on high level details, and ask clarifying questions about e.g. rate-limiting etc.