Hatchet News

I’m looking for insights on the types of tickets devs typically handle during on-call shifts and how much of the work could be automated.

At Amazon, I noticed that many on-call tickets were "no-code" solutions—tasks that involved clicking through buttons or toggling settings, which could likely be automated with the right workflows. The full-time devs mentioned this was common for recurring issues.

Here are my main questions:

What kind of tickets do you typically handle during on-call? Are they mostly monitoring, troubleshooting, or tasks that could be automated?

How often do you get paged for on-call work? At Amazon, it seemed like you got paged every time you were on call. Is that the norm, or do other teams have fewer pages due to more automation?

Would a tool that automates some on-call tasks be useful? I’m thinking of building software that lets devs create workflows to automate recurring issues. AI would classify the issue, interact with customers, and deploy a solution. If it can’t resolve the issue, it would page the dev with recommendations. Do you think this could help reduce the on-call workload?

designed and developed by Tommy Chow (source)