SRE + On Call Dev Engineer. Basically SRE takes the page - if they can't troubleshoot it or restore it to normal service, then the on call engineer gets called

SRE + On Call Dev Engineer. Basically SRE takes the page - if they can't troubleshoot it or restore it to normal service, then the on call engineer gets called. In our case, we're still small enough that one on call engineer has to take the load regardless of feature/product. The exception is the aforementioned Rust code base which calls myself or the other engineer. But this is because it's not running on our infra - it's running on customer boxes so that's a different support story. Re: > How do you respond to emergencies when your people don't own projects or code bases? Who gets woken up at midnight? The person responsible for the latest release? Wouldn't that discourage people from deploying new releases? Culturally, our engineering team doesn't really tolerate "not deploying". That's not to say that you're being measured by number of deploys like some sort of perverse "IBM Lines of Code" metric - but you're expected to be deploying code as it's ready via PR + Tests. It's not a perfect system but we've tried pretty hard during hiring to select folks that are well aligned with how we think about this. No one gets to own their space and no one is immune from rolling their sleeves up and figuring it out. If that isn't someone's thing, we try to find that out during the interview because it doesn't fly internally with the team.