To software developers in this thread who are on-call; I&#x27;d like to share some thoughts with you. I&#x27;ve worked at places that do have on-call rotations and others that have none. I will no longer work at a company that requires me to be on-call.<p>Why? It says a lot when a company doesn&#x27;t put the effort into various forms of testing and QA to ensure that production software does not have critical issues that warrant at 2am call. Unit, functional, integration, load, and simulation tests should be written for every single piece of critical infrastructure. You should be hammering these things in staging environments with 10-100x of your normal peak load.Use something like Gore to replay live traffic against a version in staging or QA environments. Yes, that takes work, but to me it&#x27;s better upfront than to wake me up in the middle of the night or to know that when I go home I have to have my phone around me at all times. The business should care about these things too; it&#x27;s their product and they should care enough about you to make sure good processes are in place to ensure quality production software.<p>That said, when I was at non-on-call companies there are definitely times when something does happen that warrants immediate attention. Generally someone in operations would get the first call, they check logs, diagnose the issue, and call a developer familiar with the app that&#x27;s causing the issues if that&#x27;s the case. I don&#x27;t mind waking up because I know it has to be something serious that slipped past our processes.