Learn how to help your team build confidently (and securely!) in prod in our upcoming Tech Talk: Sign up here.

SRE Interview Process

Interview Processes
SRE Interview Process

Hi there! 👋 We look forward to meeting you!

Our interview process is structured to simulate typical day-to-day scenarios that you’d encounter at OpsLevel.  There won’t be any gotcha questions, but we have different interview slots that aim to cover the various aspects of your role and craft.  All slots are held remotely and don’t have to be scheduled consecutively, though they can be if you want.

We want to work with the best people at OpsLevel, so while recognize that our interview process is meticulous, it is a reflection of the high bar of excellence we hold ourselves to.

Changing jobs is an important milestone and we strongly believe that interviewing is a two way street.  Throughout the interview process, you will be meeting with lots of different OpsLevelers.  Please don’t feel shy about asking lots of questions.  We’re very transparent about what it’s like working here.

First Contact

1. Intro Call    

A 45 minute intro call with our one of our software dev managers. It’s a chat to get to know you better, learn about some of the projects you worked on in the past, hear what you’re looking for in your next role, and to tell you more about OpsLevel.

Virtual Onsite

1. Take Home Programming Challenge    

We ask you to spend some time deploying a small application using IaC.

Take Home Problem Description

2. Chat about your Take Home Solution    

During this interview, you’ll chat with an OpsLeveler about your solution to the provisioning infrastructure take home programming problem.

3. Scaling Systems    

In this slot, you and another OpsLeveler will pair together on a programming problem and discuss how to scale it.

For this interview, please ensure you have a functioning development environment setup for your favourite programming language.

4. Systems and Debugging    

In this slot, you’ll be given a series of vignettes around various application and system failures.

5. System Design    

In this slot, you’ll be given a business problem description and asked to design a system to support its functionality.

For example, “A system where people can write 140 character messages and share them with friends” or “An online file conversion service”.