I don&#x27;t disagree with anything you said here. Organizations should try to hire developers that care about what they build and understand that, as an implied part of the nature of the job, your phone may ring at some unknown time because of an issue. In operations it is certainly implied that you will likely be the first one notified of production issues and you will most likely be the first to know which developer(s) need to be contacted. I am certainly not advocating for a developer to throw their hands up and say &quot;not my problem, I&#x27;m not on call&quot; or &quot;it&#x27;s an ops issue.&quot; Those would be very junior or childish reactions and certainly not the qualities of a senior developer.<p>What my post was getting at more of an observation I have  made during interviews where teams had on-call rotations for developers. When I ask &quot;how often does your phone ring during your time on-call&quot; I would get answers that hinted at a deeper issue. Maybe it wasn&#x27;t always that way, maybe the on-call rotation started with the purest of intentions like you have highlighted, but somewhere along the line management saw that as an opportunity to take shortcuts with testing and quality. So, am I saying that if a company were to make me an excellent offer, but required on-call rotations are they automatically ruled out? No. I am, however, going to be asking some very pointed questions and probing that arrangement quite a bit.