Make observability reliable: Register now
Make observability reliable: Register now
In 2022, we wrote about our engineering interview process to make it more transparent and accessible to candidates. A lot has changed since then: we've grown to 80 people across London, San Francisco, and New York, and naturally, our interview process has evolved too. We thought it was time for an update!
As we've scaled, our interview process has evolved to reflect better who we are and what makes engineers successful here. While technical skills remain crucial, we've found that product thinking and the ability to ship features effectively are equally important for our Product Engineers. This has shaped how we evaluate candidates, particularly in our Hiring Manager interview.
The overall structure of our interview process for engineers remains similar:
Let's dive into what's changed.
You'll chat with one of our internal talent partners and our VP of Engineering, Norberto. This conversation is all about getting to know each other—your background, what you're looking for, and whether incident.io might be a good fit.
We'll also cover practical things like location, timing, and any questions you have about the role or company.
This is where things look quite different from 2022. Instead of a traditional technical discussion about past projects, we now run this as a product-focused session with two of our engineering managers. We'll walk through how we approach building and shipping features at incident.io, putting you in the driver's seat of a theoretical project.
You'll get to demonstrate:
Don't worry—we'll send you a detailed prep guide beforehand so you know what to expect. We believe interviews work best when candidates can showcase their real thinking and decision-making rather than having to guess what we're looking for.
This stage is now run by two senior engineers, but the core remains unchanged. We'll give you a real-world problem to solve, complete with tests and a clear objective. You can use your preferred language (we support Go, TypeScript, Ruby, and Python), and we encourage you to treat us as teammates you can bounce ideas off.
What we're looking for hasn't changed—we want to see how you approach problem-solving, write clean code, and communicate your thinking. And yes, Google is still absolutely allowed!
Also run by two senior engineers, this interview explores how you approach designing larger systems. We'll present you with a real product challenge (the kind we've actually had to solve) and work together to design a solution.
We'll discuss things like:
Don't worry if distributed systems aren't your specialty—we're more interested in your thinking process and how you work through problems collaboratively.
Our Company Values are now a core part of our Culture interview. You'll meet with one of our founders (often our CTO) and another team member (we call ourselves incidentios) for a conversation centered around our core values: Raise the pace, Make it magic, Find a way, Trust by default, and Win together.
These aren't just words on a wall—they're how we actually work. We might discuss how you've demonstrated resilience in tough situations (Find a way), or talk about times you've gone above and beyond to delight customers (Make it magic).
A few things stand out about our current process:
We're always iterating on our interview process based on feedback from candidates and our team. As we continue to grow, we'll keep sharing updates about how we evaluate and hire engineers.
You can read more about our interview process across roles over on our Candidate Hub.
If you're interested in joining us, check out our open roles. We're hiring across all our locations and would love to hear from you!
P.S. We still believe in moving fast—while our process has evolved, we try to run the entire thing within a week or two.
Moving fast does not happen by accident. Here is some of the intentional things our engineers do to move so quickly!
Cutting through the hype and dollar signs, why should you actually join incident.io? And also, why might this not work for you
In the past year, we've reimagined how we build AI products at incident.io, moving from simple prompt based features to now building full-blown AI-native systems end to end. Learn why we’re hiring AI Engineers, what that work looks like, and how it’s changing the future of incident response.
Ready for modern incident management? Book a call with one our of our experts today.