# Being on-call at incident.io

DevFeed: [Being on-call at incident.io](<https://devfeed.tech/articles/being-on-call-at-incident-io-11685.md>)

Original publisher: [Read original article](<https://incident.io/blog/being-on-call-at-incident-io>)

Author: Alicia Collymore

Published: 2025-07-18T12:24:47Z

Content type: opinion

Language: en

Sources: [The incident.io Blog](<https://devfeed.tech/sources/the-incident-io-blog.md>)

Topics: [incident](<https://devfeed.tech/topics/incident.md>), [Incident response](<https://devfeed.tech/topics/incident-response.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [culture](<https://devfeed.tech/tags/culture.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [incident](<https://devfeed.tech/tags/incident.md>), [incident-channel](<https://devfeed.tech/tags/incident-channel.md>), [incident-management](<https://devfeed.tech/tags/incident-management.md>), [incident-response](<https://devfeed.tech/tags/incident-response.md>), [on-call](<https://devfeed.tech/tags/on-call.md>), [outage](<https://devfeed.tech/tags/outage.md>), [post-mortem](<https://devfeed.tech/tags/post-mortem.md>), [slack-incident](<https://devfeed.tech/tags/slack-incident.md>), [work](<https://devfeed.tech/tags/work.md>)

## AI overview

This article explains how incident.io organizes on-call rotations and incident response for a product that must remain available around the clock. It covers shared engineering responsibility, weekly pager schedules, onboarding with a buddy, compensation, coverage expectations, and flexibility to rest after difficult overnight incidents.

## Source excerpt

Dive into how incident.io handles on-call - from our supportive culture and smart scheduling to our unique approach to compensation. This post shares our philosophy on keeping our product running smoothly while prioritising our engineers' well-being.