I first had to take a development exam, building algorithms from scratch. I ended up getting an exemption on that, as scripting is more the focus for this role instead of algorithm development.

Then, I went on to a "power day," which was four straight hours of interviews. After that, I received a call from the recruiter regarding the recommendation from the interviewers.

Tech Interview 1: Evaluate a Dockerfile and find the errors and other missed best practices. Then, a sample JSON file was provided, and I was asked to build a script to process it and extract interesting information.

Tech Interview 2: Describe how you would build a CI/CD pipeline to deploy a new component all the way to production. What Git model would you use?

Behavioral Interview: Pretty standard "describe a time" questions. The one I had a hard time answering was "describe a time when your colleagues said something was impossible, but you were able to deliver it."

Case Interview:

• What would be your business case to Capital One for moving to the public cloud?
• Given a diagram of a basic login service running on-premises, how would you migrate it to the cloud? How would you make it more robust and not prone to errors? What about making this service available on a global scale?
• Given the following numbers and usage pattern, what size instance would you use in your autoscaler to optimize the cost of the service during its off-peak times, while still having enough capacity to handle the peaks.