Why did I decide to stop doing on call rotations?
💭 My first on-call rotation sounded like the ultimate way to grow as an engineer. I wanted to prove I could handle real incidents, stay calm under pressure, and be that dependable person the team could count on. But once I actually lived it, I realized how much no one talks about the toll it quietly takes on you.
At first it felt empowering. I was getting paged for real production issues, fixing outages that impacted hundreds of users, and seeing the direct impact of my work. There’s a rush that comes from solving a problem at 2 AM and bringing a system back online. It makes you feel capable, trusted, essential. But that feeling fades fast when your phone becomes something you dread instead of a tool.
✨ I learned responsibility quickly. On-call forced me to understand how fragile systems can be, how a small configuration mistake can ripple through everything, and how much collaboration matters when you’re firefighting at odd hours.
💻 What no one really prepares you for is the exhaustion that creeps in. You never truly relax because the next alert could come at any moment. Even on weekends, I’d catch myself glancing at my phone every few minutes just in case. Sleep wasn’t restful anymore, it was a countdown until the next incident.
🧠 It taught me that constant availability doesn’t equal dedication. You can love your job, take pride in your work, and still set boundaries. Real growth doesn’t come from burning out to prove your worth; it comes from creating systems that work so well you don’t have to wake up at 2 AM to fix them.
🌱 These days, I focus on automation, better alerting, and stronger monitoring, building reliability into the system itself rather than relying on engineers to be endlessly available. It’s still DevOps, still meaningful, but it’s sustainable.
☕️ I’ll always respect the people who keep on-call rotations running smoothly; they’re the backbone of every tech team. But for me, I learned that I do my best work when I’m rested, creative, and present, not when I’m one alert away from burnout. Choosing balance over chaos was the best decision I’ve made in my career.
What’s one lesson your most stressful job ever taught you about balance and boundaries?
#lemon8partner #careeradvice #salary #jobsearch #careerinspo
Working on-call can feel like a rite of passage for many engineers, signaling trust and responsibility within a team. However, the reality often includes unexpected stressors that aren’t frequently discussed. The exhaustion from being constantly on alert, with the phone buzzing unpredictably, disrupts normal routines and restful sleep, turning empowerment into anxiety over time. One vital lesson from on-call experience is understanding the delicate nature of tech systems. A seemingly small configuration slip can cascade into serious outages affecting hundreds or thousands of users. This reality underscores why collaboration and clear communication during incidents are crucial for quick resolutions and minimizing damage. Moreover, being reachable 24/7 doesn't necessarily showcase dedication; instead, it may lead to rapid burnout if boundaries aren't respected. Sustainable growth involves creating automation pipelines, enhancing monitoring systems, and refining alert strategies to reduce manual interventions—essentially shifting from reactive firefighting to proactive prevention. This approach not only improves system reliability but also supports engineers’ health and creativity. Choosing to step back from on-call duties doesn’t diminish commitment; rather, it reflects maturity in balancing job demands and personal well-being. Many tech professionals find their best work stems from feeling rested and mentally present. This balance fosters innovation and long-term productivity. For those who still participate in on-call rotations, respect and acknowledgment are warranted, given their vital role in maintaining system uptime and customer trust. Yet as the tech field evolves, emphasizing smarter automated solutions and healthier work-life boundaries benefits both individuals and organizations alike. Reflecting on your own experiences with stressful jobs, what lessons did you learn about maintaining balance and setting boundaries? Sharing these insights helps normalize conversations about mental health and sustainable work practices in high-pressure environments.
Have you done an ‘on call’ at your job!?