The very fact that we are talking about "DevOps" teams (that do not include dev) is wrong from the very start.

DevOps is a methodology, not a role.

I've always felt that DevOps became a function/team partly because companies and especially SWE's started complaining that they were spending too much time "doing Ops work" and product/business started demanding more features for which they running out of cycles. And add to that the burnout from being on-call (especially if the dev team is relatively small and you have to go on-call every 2-3 weekends).

	▲	verdverm 9 hours ago \| parent [-]
		When I still did on call ops, devs got notified before us if their apps were the problem. We got notified first if it was our infra Having an ops team does not mean devs get to through on call team over the wall to someone else. That's a sure recipe for resentment and turnover

▲

pjmlp 4 hours ago | parent | prev [-]

For most HR departments it is a role, it even has a career path.