Come build the future of Incident Response

We’re nearing the end of Q1 2025, and I’m very excited about what’s next for Q2 and beyond.

The product is growing, and hiring is ramping up rapidly right now - it’s an incredibly exciting time for us at incident.io.

I think it’s going to be one of the most impressive years for incident management overall. By the end of the year, incident management will look very different from today, specifically due to the AI explosion that’s happening.

We think AI can make a significant difference to incident response, therefore we’re making a significant investment in it - I’ll talk more about AI further below.

One thing I noticed in recent conversations with smart and ambitious candidates, people always ask me: “Why incident.io, and why now?”

If I were in their shoes, this post is the answer I’d give myself. It covers our product vision, our engineering culture, and the company.

Let’s take a look on how I personally think about the product. And because a great product can only exist with great people, I’ll then focus on the calibre of team we have and why joining this team would be an incredible career choice for you.

The Product

The Product is where you’d make the biggest impact if you were to join, so let’s go a bit deeper.

Curious about how 2025 has gone so far, I checked our Changelog and counted 13 entries already. We’ve shipped over 200 fixes, features, and improvements; deployed around 2700 times to production; and engaged more than 3000 times with customers to ensure we’re building the right things.

And we’ve done all of that while building what I genuinely believe is one of best AI products: Investigations. It’s wild to me that this is now becoming a reality.

For the purpose of explaining what’s coming in Product, I’m going to stay with the three main areas that guide our goals: AI, On-call, and Response.

AI

AI has been in the news, and every SaaS company wants to be “AI-ready”. We’re big believers in AI as well but we’re taking a slightly different approach.

We’re making a huge investment in AI, and we’re not starting with “We think the Product needs to have AI.”, we’re starting instead with “We believe that AI can make incidents easier to handle.” and go from there.

In terms of magical AI products, we’ve launched Scribe but honestly that’s the beginning of something, not the end. Every time I describe what Scribe is, in meet-ups, interviews, or with customers, they all go “Where was this all my life?”.

It sounds simple: “someone to transcribe”. If you think from the experience of the user, it’s a lot more. It gives you peace of mind. You no longer need to think about who should take notes. Or finish a call and realise no one was taking notes. Or finish a call, and someone needs to go over all the notes and extract key takeaways, figure out the right follow-ups and who should be assigned.

With Scribe, that’s all taken care for you and synced back to the incident channel for others to follow-up. If you’re an executive trying to follow along on an incident, long gone are the days you had to write “Can someone update me on what was discussed on the call?”. It’s just there!

I want you to think of yourself as one of the engineers that shipped Scribe. It would have felt amazing to know you built it, wouldn’t it?

In 2025, you'll help us take AI even further. Our next leap, which I mentioned before, is Investigations - imagine waking at night, logging on, and discovering AI has already completed initial investigations. You simply review and act.

You'll also focus on contributing to:

• Developing AI-driven analysis of logs, code, and past incidents to pinpoint root causes faster
• Implementing rich, cited information searches during active incidents
• Building proactive AI that suggests timely internal updates and helpful actions: think of an internal incident update being written if it detects you have forgotten to do so
• Creating intuitive chat interactions - e.g., typing “make Norberto incident lead” instead of navigating complex interfaces

If AI is the big investment, let’s take a quick look at the investment we made last year, which has had a lot of traction with Enterprise customers: on-call.

On-call

We launched our on-call product last March and just celebrated its first anniversary. From day one, we've aimed to create something much better than existing tools: prioritising human-centered design and functionality.

Our engineering team tackles exciting, complex technical challenges every day: high-scale alert ingestion, intelligent alerting, global telecom reliability, and generating deep insights at scale.

This year, you'll help us make on-call a true wonder of a paging system by:

• Building actionable alert insights to cut through noise and pain points
• Extending global reach to page anyone, anywhere (a deceptively challenging goal!)
• Scaling alert ingestion into billions? of events
• Adding thoughtful enhancements, such as prompting teammates to support colleagues after a rough on-call night

Ambitious? Absolutely. But one can only build ambitious products on top of a solid foundation. That is Incident Response.

Incident Response

Incident Response is where we started and remains our core focus. Customers love features like Catalog (bringing your own data to power automations), workflows (transforming tribal knowledge into consistent, repeatable processes), policies, and more. But there's so much more we want to build.

In 2025, you'll help us:

• Deliver first-class support for security incidents
• Create seamless tools to curate incident timelines
• Develop features to build clearer, more powerful post-mortem narratives
• Simplify managing compliance policies like DORA and SOC2
• Elevate StatusPages from beautiful to incredibly powerful and dynamic

If you’re passionate about reshaping incident response and tackling building magical products, we need to talk. Let me give you a sense for the team you’d be joining.

The engineering team

Our engineering team is genuinely remarkable. It’s a blend of highly experienced, low-ego engineers who’ve tackled massive challenges before, paired with similarly ambitious but more junior engineers eager to accelerate their careers.

We believe strongly in collaboration and community, so we bring everyone together in the office. While it might seem unconventional (I’m going to keep any office-remote-hybrid debate outside the scope of this post) these days, we see it as essential, especially for those early in their careers.

When you join us, you’ll immediately feel supported - there’s an entire group of people that are ready to embrace and support you through thick and thin. Startups are hard work but they also provide rare growth opportunities. Worth reading the perspective of one of our engineers, Lawrence, on why he joined incident.io.

We actively encourage growth, ensuring you face exciting and meaningful challenges, within the safety of your own expertise of course. Here are a few examples of how we do it:

• Managers and peers will actively look out for who is a great fit for any new project, ensuring the opportunity is aligned with their strengths.
• We accelerate people growth in an ego-less way - I quite literally have direct sessions with engineers whenever they find value in spending time directly with me. In most companies, this access would be difficult at best, and at worst actively frowned upon.
• Our most experienced engineers are always delighted to work with other folks and help them grow as much as possible.
• We (quite proudly) encourage folks to share their hard work: the on-call team’s series on building on-call, Martha sharing at LeadDev why we should all be declaring more incidents, Alicia discussing authentic management and driving at pace, Lawrence on starting from nothing, or even hosting our own conference, sev0.

On top of all that, I don’t think a week goes by that I don’t get a message along the lines of “Hey, I’m sure managers and leads are all over this, but I think person X would be amazing on project Y.” from people that want to see their peers grow.

I think this kind of behaviour and culture is amazing, and hard to find. A team like this, combined with our product ambitions, will accelerate your career. How many people get to say they built a product used by leading companies like Netflix or OpenAI?

The company

And the same goes for the rest of the company!

As a company, we're an energetic, tight-knit group, now about 80 strong. Walk through our office, and you'll immediately notice folks passionately solving challenging problems while still finding time for dad jokes, memes, spirited debates, and plenty of laughs. We're proud of our culture and openly share how we operate. Seriously, check it out.

Many startups lose their spark around the 50-person mark, bogged down by process, slower pace, or unclear vision. Not here. At 80 people, we maintain incredible velocity, just enough structure, and a clear, ambitious vision.

Sales, Customer Success, Engineering, Product, Design, Founders, all work together to win.

Conclusion

There's genuinely never been a better moment to jump aboard - we have momentum, clarity, and exciting technical challenges waiting to be solved.

Our product is excellent and mature but that doesn’t mean finished - that means we’re ready for the next ambitious challenge. We have countless exciting problems left to solve.

2025 stands to be our most exciting year yet. Come join us — we’ve got a tonne to do and we’re looking for smart folks to help us do it!

We're actively hiring across Engineering, Design, and have many other roles opening soon. Even if it's early, we'd love to chat:

• Senior Product Engineer
• Senior Brand Designer
• Product Designer

Come join us and help build the future of incident management. Our team is special but we’re always looking for the next special person we want to work with. That could be you.