What Being On Call in IT Actually Costs You

It is 2:47 in the morning and your phone is vibrating on the nightstand. You have four seconds to decide whether this is the alert that matters or the one that fires every night because someone left a threshold too tight. Your heart is already going before your eyes are open. Nobody put that part in the job description.

The week never really ends

On-call is not overtime. Overtime has an end. On-call is a low hum under everything else you do, and it changes how you live. You stop planning Saturday hikes. You keep the laptop in the car. You think twice about the second beer at dinner, and you feel slightly ridiculous explaining why to friends who never carried a pager. The rotation sounds harmless on paper, one week in six, and then you notice that a fifth of your year is spent in a state of partial readiness. You cannot fully rest; some part of your brain is listening. And the cruel part is that the quiet weeks are not rest either, they are just weeks where you waited and nothing happened, which leaves you more tired than a week you actually worked.

The judgement nobody trains you for

The technical side is usually the easy part. The hard part is the decision you make half asleep: is this a wake-the-team-up event or a check-it-at-eight event. Get that wrong in the cautious direction a few times and people stop trusting your judgement. Get it wrong in the other direction once and a customer notices before you do. There is no runbook for it, because the runbook knows what the alert says, not what it means at 3 a.m. Good on-call engineers build a quiet mental map of what actually hurts the company, and they learn to say a specific thing to themselves about every alert, something like this one has a backup path, or this one is the backup path and it is gone. If you can articulate that sentence, you can go back to sleep.

It takes more than it gives

Ask anyone who has done a long rotation about their life outside work and you will hear the same answer. Partners learn to ask who is on call before they make plans. Sleep debt collects interest. The Monday after a bad rotation you are not hungover, you are just slow, and you still have to walk into the office and be pleasant to someone whose printer is offline. Teams that pretend this is fine end up losing their steadiest people first, because the steadiest people are the ones who answer every call and quietly absorb the damage. When a colleague says they are not good for the Thursday escalation, that is not weakness, that is a person protecting the last of their capacity so they can still do the job well next month.

What to ask before you take the pager

On-call quality is decided before the rotation starts, and mostly by policy. How often does the phone actually ring, and can anyone quote me a number instead of an adjective. Is there a documented escalation path, or do I call a person and hope. Is the person I wake up the person who owns the system, or a stranger in another timezone. Do I get comp time after a night of alerts, or is that a nice idea nobody logs. And the one that tells you most about the culture: when an alert turns out to be noise, does anyone fix the alert, or does the team just learn to ignore it. A company that tunes its alerts respects the person holding the phone. One that shrugs is telling you how the next year will go.

The strangest thing about being on call for a few years is that you forget what unbroken sleep felt like, and then one day someone takes the phone off you for good and you sleep for nine hours and wake up feeling almost like a person. That is the real bill. Not the late nights, but the low background noise of being permanently half-listening, for a job that only remembers you existed on the nights it needed you.