Note that Checkr is not really an EOE and refuses to provide accommodations to disabled persons, and thus discriminates unfortunately.

Outside of this, I had thoughtful discussions with interviewers. I had some moments to talk about the culture and found that there does seem to be a culture that values employees and has reasonable work-life balance, where employees are highly engaged and collaborative.

You will be asked questions on previous successes, failures, and troubleshooting.

Some of the questions will require you to be familiar both top-down and bottom-up with current operations patterns (DevOps, containers, change config, etc.). You should be advanced in change config, infrastructure as code, and immutable production. You should also know the trade-offs between different tools and patterns.

Understand patterns of deployment and the development life cycle with continuous integration and continuous delivery.

One question I was asked was to architect a solution, including not just infrastructure, but app servers and other backend support resources (databases, NoSQL, queues, streams) as they made sense. This consideration was for continuity (disaster recovery, high availability) and applicable design patterns.

There will be questions on infrastructure as code, cloud-native, immutable production, and general broad knowledge on current patterns in reliability engineering and DevOps. They'll ask why Terraform versus CloudFormation versus others.

Coding Exercise. You'll be given a class with methods, and you should improve upon it. I think you were given Python, Ruby, Go, and Java, maybe others.