1. Interview with recruiter. I spoke with a nice person, but they did not have a technical background so when asking to describe certain projects they were really just looking for keywords like: micro-service, containers, etc 2. Did a short take home assignment to code a small CLI tool and demonstrated OOP practices, testing, etc 3. Made it to pair programming round. I was given a few reference materials hinting at what the problem would be and then received the actual problem about 1 hour before the interview started. In this case it was to write a deserializer for both JSON and YAML in one hour. For those not familiar, just one of those formats is hard to solve in an hour let alone two. I wrote a parred down version of the JSON deserializer and ran out of time for the YAML part. I think the only way this round gets passed is if you can create/memorize the solution(s) beforehand and then code by memory in the interview. To be honest, I'm not sure what an interview like this tests besides ones ability to memorize a problem. But of course every company has free reign to decide their processes and I respect that. 4. There are supposed to be another set of rounds with HR style questions and another technical round, but I did not make it beyond the pair programming round.