The common staffing pool encourages the developers to create systems that can be operated efficiently so as to minimize the number of SREs needed.
It also means that reliability engineers don't get to enjoy the fruits of their innovation. They don't get to enjoy quiet on-calls if they do their jobs exceptionally well. They get moved to a trouble spot instead. Does this create any pathologies; is there a local optimum that makes ops just quiet enough to tolerate but not so quiet that you're made redundant? Devs, on the other hand, personally derive all benefit.
