Ok, I'll be honest, some of these are great questions but a lot of them are just insane. This is more like a certification exam than an interview. This is complete overkill for like 99.9% of devops positions. That being said, it does accomplish exactly what you probably want bc if I was ever in an interview and someone asked me some of these questions, I would just politely decline the position and save us all some time. More on reddit.com

Google has a very nice video on doing interview with them - https://www.youtube.com/watch?v=XKu_SEDAykw Note that the most important part is not to give the right answer right away, but to talk through how you are thinking about the problem. Also keep in mind that in most of the places it's totally acceptable to ask interviewer a question if you forgot something, some places are even totally cool with you googling your way through the question. If interview is remote (which it most likely is), you will be doing with peer programming site - like codeshare or something similar, make sure you are familiar with how it works. Some of them have quite good web editors with support for common shortcuts, some will run your code for you - just make sure you are comfortable with technology before the interview. More on reddit.com

I was asked questions specific to the product and design pattern I was developing, that I brought to the interview. As a hiring manager I would always recommend you bring something to the interview with you to discuss. This leads the discussion and makes you the expert. A pure DevOps role is not a role where tasks are assigned to you with finite solutions. A DevOps engineer needs to be able to develop multiple solutions to a number of problems and weigh the pros and cons of each. Being able to speak cogently about something you have built and the trade offs and decisions you have made is the best possible route to putting this skill set on display. More on reddit.com

What will my onboarding look like, and what would the milestones for me be at day 30, 60, and 90? This question will give you a sense of whether they're organized or if you're gonna have to wing it What does the on call rotation look like, and how often do incidents occur? Do you track the number and severity of incidents and work to reduce them over time? This question will tell you whether they're focusing on putting out fires (bad) or preventing them from happening again (good). Tell me about the relationship between the "devops" folks and the rest of the devs. How much of a devops engineer's time is spent supporting devs directly (i.e. in a support desk "please help me with this task" kind of way), vs. working on infrastructure improvements (e.g. improving CI/CD, deploying cloud infrastructure, building tools, etc.)? More on reddit.com