I don't think there's a way to resolve a semantic argument like this. Most roles are pretty amorphous, and thinking any title can totally encapsulate job requir

I don't think there's a way to resolve a semantic argument like this. Most roles are pretty amorphous, and thinking any title can totally encapsulate job requirements is prone to error. Even as an EM, I have to find out what a job's expectations are during an interview. SWEs are probably the only engineering role that doesn't have this problem (mostly). It's been very different everywhere I've worked. It's different from other fields that have far more rigorous structure. DevOps started as an idea that the development team should be responsible for operations. Before this, most dev teams created artifacts that got handed to an ops team to deploy and be on call for. That idea went to corporations that wanted to modernize, but you can't just disappear an entire workforce of admins used to doing things differently. It's a similar situation to where graphic designers started being UX designers. These people didn't magically develop a different set of skills...just a different set of expectations.