How do I manage on-call anxiety as a developer?

CBT for on-call anxiety involves: (1) identifying catastrophic thoughts about pages ('this will be a disaster'), (2) examining your actual page history (most are routine), (3) setting worry boundaries (worry time, not constant vigilance), and (4) building confidence through runbook familiarity. Track page outcomes to calibrate your threat predictions.

Is on-call anxiety a real problem?

Yes. Studies show on-call duty increases cortisol levels, disrupts sleep, and correlates with burnout. CBT helps by distinguishing productive preparation (knowing runbooks) from unproductive vigilance (checking dashboards obsessively). The goal is to be responsive when paged without being anxious when not paged.

How do I stop dreading on-call shifts?

Use a thought record to examine the dread: what specifically do you fear? Usually it's uncertainty ('I won't know what to do') or catastrophizing ('it'll be a SEV1 I can't handle'). Reframe with evidence: how many pages have you handled successfully? What runbooks exist? What support is available? Confidence comes from data, not reassurance.

How do I reduce on-call anxiety?

Three evidence-based approaches: (1) Preparation — run through common alert playbooks before your shift so responses are familiar, not novel. (2) Cognitive reframing — 'on-call is a threat' becomes 'on-call is a skill I am building.' (3) Worry time — defer 'what if I get paged at 3am' worries to a scheduled 15-min window instead of carrying them all day.

Is on-call anxiety a sign I am in the wrong job?

Not necessarily. Some on-call anxiety is normal — you are responsible for production. It becomes a problem when it disrupts sleep on non-call nights, causes dread that avoids complex work, or persists after the shift ends. If it crosses those lines, that is a signal to address the anxiety (CBT) or the rotation (talk to your manager), not necessarily leave the job.

CBT for On-Call Anxiety

Understanding On-Call Anxiety: More Than Just Stress

For engineers, DevOps specialists, and SREs, the on-call rotation is an inescapable reality. It's the backbone of reliable systems, yet it often comes with a significant hidden cost: on-call anxiety. This isn't just general work stress; it's a unique beast, fueled by a potent cocktail of high stakes, sudden disruptions, and the relentless demand for immediate, flawless problem-solving.

Think about it: one moment you're unwinding, perhaps enjoying dinner or finally catching up on sleep, and the next, a blaring pager or urgent Slack notification plunges you into a high-pressure incident. This abrupt shift from calm to crisis is incredibly taxing. The dread often starts long before the first page, manifesting as anticipatory anxiety – that gnawing feeling in your stomach as your on-call shift approaches. You might find yourself catastrophizing: "What if a critical database goes down at 3 AM and I can't fix it?" or "What if I make a rollback decision that causes an even bigger outage?"

The stakes are undeniably high. A SEV1 incident can impact millions of users, halt business operations, or even lead to significant financial loss. The pressure to diagnose complex issues under extreme time constraints, often with fragmented information and sleep deprivation, is immense. This environment fosters a fear of failure, a concern about being perceived as incompetent, or even worse, being blamed for system failures that are often multi-faceted. This "pager fatigue" can extend beyond the active on-call period, making it difficult to truly switch off, leading to hyper-vigilance even when you're technically off duty.

Over time, this constant state of readiness and the emotional rollercoaster of incidents can erode mental well-being, contribute to burnout, and impact personal relationships. Traditional coping mechanisms often fall short because the triggers are so specific and powerful. This is where Cognitive Behavioral Therapy (CBT) offers a structured, practical approach tailored precisely to the unique challenges faced by technical professionals on-call.

How CBT Helps Engineers Navigate On-Call Stress

Cognitive Behavioral Therapy (CBT) is a highly effective, evidence-based approach that helps individuals identify, challenge, and change unhelpful thought patterns and behaviors. For the on-call engineer, CBT isn't about magically eliminating incidents; it's about equipping you with robust mental tools to manage your reactions to them, reducing the intensity and duration of anxiety.

At its core, CBT operates on the principle that our thoughts, feelings, and behaviors are interconnected. If you can shift one, you can often shift the others. Here's how key CBT techniques can be adapted for the on-call context:

Cognitive Restructuring: This is about challenging your Automatic Negative Thoughts (ANTs). When you think, "I'm going to mess this up," CBT encourages you to examine the evidence for and against that thought. What's the realistic probability? What resources do you have? What's an alternative, more balanced perspective? For an SRE, this might mean moving from "I'm solely responsible for fixing everything" to "I am part of a team with runbooks, escalation paths, and monitoring tools to support me."
Behavioral Experiments: Sometimes, our fears are based on assumptions. Behavioral experiments involve testing those assumptions in a controlled way. If you dread a particular type of incident, you might prepare more thoroughly for it, or even simulate it in a non-production environment, to see if your catastrophic predictions hold true. Often, the reality is less severe than the imagined scenario.
Problem-Solving Skills: CBT helps you differentiate between what you can control and what you can't. While you can't control when an incident strikes, you can control your preparation, your response strategy, and your post-incident review process. This shifts focus from helpless worry to proactive action.
Mindfulness and Grounding: During a high-stress incident, it's easy for your mind to race. Mindfulness techniques can help you stay present, focusing on the immediate task at hand rather than spiraling into worst-case scenarios. Grounding exercises can quickly bring you back to the present moment, helping to regulate physiological stress responses.
Setting Boundaries and Self-Care: While not strictly a "technique," CBT principles support the idea of valuing your well-being. This includes consciously scheduling downtime, protecting your off-call hours, and engaging in activities that recharge you. Recognizing that your capacity is finite and respecting that limit is crucial for sustainable on-call performance.

By applying these techniques, engineers can transform their on-call experience from one dominated by dread and anxiety into one characterized by preparedness, resilience, and a greater sense of control.

A Worked Example: Conquering the Pre-Shift Dread

Let's walk through a common scenario for an engineer: the anticipatory dread before an on-call shift. Meet Alex, a senior DevOps engineer. It's Friday afternoon, and Alex just received the calendar invite notification: "On-Call Rotation Starts: Monday 9 AM." Immediately, a wave of anxiety washes over them.

The Trigger & Automatic Negative Thoughts (ANTs)

Trigger: Notification of upcoming on-call shift.

Alex's ANTs:

"My entire week is going to be ruined. I just know it." (Fortune Telling, All-or-Nothing Thinking)
"I'm going to get slammed with pages all night, every night. I won't get any sleep." (Catastrophizing, Fortune Telling)
"What if a critical microservice goes down, and I can't pinpoint the root cause quickly enough? Everyone will be waiting on me." (Catastrophizing, Personalization, Mind Reading)
"I'm not as sharp as the other engineers. I'll probably make a mistake and cause a SEV1." (Self-Blame, Comparison, Low Self-Esteem)
"I wanted to work on that side project, but now I'll be too exhausted and stressed." (Emotional Reasoning)

Challenging the Thoughts (Cognitive Restructuring)

Using CBT, Alex would pause and apply a structured approach to challenge these ANTs:

"My entire week is going to be ruined."
- Challenge: "Is it truly *every* week I'm on-call that's 'ruined'? Last time, I had a few pages, but I also managed to get some project work done and even enjoyed a quiet evening. Ruined is a strong word."
- Alternative: "This week presents challenges, but it also has opportunities for learning and contributing. I can plan for downtime."
"I'm going to get slammed with pages all night, every night."
- Challenge: "What's the actual historical data? Looking at incident reports, the average number of pages per shift is X, and critical incidents are Y% of those. It's statistically unlikely to be 'slammed' every night, and even if it's busy, it's usually not 24/7."
- Alternative: "It's possible I'll get some pages, especially after hours. I'll make sure my alert routing is correct and my phone is charged. I'll manage them as they come."
"What if a critical microservice goes down, and I can't pinpoint the root cause quickly enough?"
- Challenge: "Have I ever truly been in a situation where I was completely helpless? I have access to logs, metrics, runbooks, and escalation paths. I've handled complex incidents before. Even if I don't know the *exact* root cause immediately, I know how to gather information, involve others, and implement mitigation steps like rollbacks."
- Alternative: "If a critical microservice goes down, I will leverage my skills, our tools, and the team's collective knowledge. My role is to respond effectively, not to have all the answers instantly."
"I'm not as sharp as the other engineers. I'll probably make a mistake."
- Challenge: "This sounds like imposter syndrome talking. I've been recognized for my contributions, and I successfully navigated that complex database migration last month. Everyone makes mistakes; the key is learning from them. My value isn't tied to perfect execution."
- Alternative: "I am a competent engineer with valuable experience. I will approach incidents with focus and diligence. If I encounter an unfamiliar problem, I will use it as a learning opportunity and collaborate with my team."

Behavioral Action Plan

Beyond challenging thoughts, Alex creates an action plan to reinforce positive behaviors:

Pre-Shift Prep: Review critical runbooks and recent incident reports. Ensure monitoring dashboards are accessible and understood. This reduces uncertainty.
Proactive Self-Care: Plan a relaxing activity for Sunday evening before the shift starts (e.g., a long walk, reading a book, a favorite movie). This creates a positive anchor.
Communication: Inform family/friends about the on-call schedule to manage expectations and reduce guilt if disrupted.
During Shift: Schedule short breaks, even 10-15 minutes, to step away from the screen, stretch, or grab a healthy snack. If a page comes in, take three deep breaths before diving in.
Post-Incident Review (Personal): After a challenging incident, take a few minutes to reflect: What went well? What could be improved? What did I learn? This transforms perceived "failures" into growth opportunities.

By actively engaging in this CBT process, Alex doesn't eliminate the on-call shift, but significantly reduces the anticipatory anxiety, feels more prepared, and approaches the week with a sense of control rather than dread.

Try the Free Tool: Your Personal CBT Toolkit for On-Call

You don't have to navigate the unique stresses of on-call engineering alone. Applying CBT principles can make a tangible difference in your mental well-being and performance. To help you get started, we've developed a free, easy-to-use CBT toolkit designed specifically for mental health in tech.

This interactive tool allows you to practice cognitive restructuring, track your mood, identify thought patterns, and access guided exercises that can help you manage anxiety and stress. It's a practical, private resource that puts the power of CBT directly into your hands, whenever you need it most – whether you're preparing for a shift, in the middle of an incident, or unwinding afterwards.

Take the first step towards a more resilient and less anxious on-call experience. Start building your mental toolkit today.

Access Your Free CBT Toolkit Now