How our data team handles incidents
Data incidents are just like any other type of incident, and having a well defined data incident management process in place makes it a lot less stressful when things inevitably break. Here's how our team does it.
Navo Das
Behind the Flame: Rory
Meet Product Engineer Rory 🔥
incident.io
The Tasty Data Morsel: Data delight as company culture
Feeling hungry? We love to spice up our weekly all-hands meetings with the Tasty Data Morsel: a bite-sized insight covering everything from our sales velocity to the most popular Christmas party dishes. These data treats make numbers not just digestible but downright delicious.
Matilda Hultgren
Scoping week
A few months back, we launched On-call with a solid set of features—but that was just the start. To keep the wheels turning, we recently held a "scoping week" where we paired up, tackled ambiguities, and nailed down our project roadmap. Here's how we did it.
Leo Sjöberg
A tough day for incident responders: lessons from the CrowdStrike update
Today marks a particularly challenging day for incident responders across the globe. As many of you may have noticed, a recent update from CrowdStrike has triggered widespread disruptions, causing chaos in various sectors.
Stephen Whitworth
Time, timezones, and scheduling
Time is tricky, but building our On-call scheduler meant getting cozy with all of its quirks— and lots of testing. No "time" like the present to dive in!
Henry Course
Behind the Flame: Georgie
Meet Customer Success Manager Georgie 🔥
incident.io
The complexity of phone networks
Making a phone call is easy...right? It's time to re-examine the things you thought were true about phone calls and SMS.
Leo Sjöberg
Building a multi-platform on-call mobile app
What it takes to build a greenfield mobile app in 2024? When we launched On-call earlier this year, we had to find out.
Rory Bain
