The interview process was pretty straight forward: * Initial screening call * Technical test to write a client library (with no time limit) * A 90 min tripple header interview The tripple header interview was the most interesting part as it was split into 3 30 min interviews with differing interviewers. Part 1 was a quick overview of how the company adds value, an overview of their system's design, and some questions about implementation choices in the coding test. part 2 focused more about how applicable I was to the role, asking some general technology questions such as explaining tcp/ip, explaining http. We talked about the benefits and drawbacks of 100% remote working. To finish we talked about my experience with cloud compluting, IaC, and messaging systems. The final stage was the most surprising. Having to rollplay at debugging an issue. I only realised this the night before so didn't have much time to fret but I thought I would have to read some logs and identify an issue with a section of code - a pretty tall order without domain experience. Luckily it was a much more relaxed affair. The interviewer roleplayed as the system so I viewed the system diagram and asked about system metrics or system logs. We then discussed how I would implement CI/CD on my coding submission and I think we then went onto my questions. Overall it was a very quick and painless process. The interviewers were great, the interview didn't start asking silly algorythm questions or getting bogged down in domain questions. The rollplaying debugging was the most troublesome, I was happy to describe my general checklist but I had to rephrase it into queries to the logs/metrics that I was probably being too general about.