Like most things in life, it depends.

I've been in IT since the '90s, cutting my teeth as a unix sysadmin and network engineer. Funnily enough, I fell into DevOps to get out of being on call, haha. And yes, DevOps is all that rolled into one. There used to be a distinction between Dev and Ops people, but as companies cut costs, they made Dev people take on more Ops tasks, and Ops people more Dev tasks. Eventually DevOps was born. There are still dedicated Dev or Ops teams for companies that are big enough.

But it depends. I hated my previous DevOps role. I was in R&D with about a hundred others, and we busted our butts to make cutting edge tech, which the company then applied to marketing and sales, helping other companies bilk more money from their customers. It's not exactly a fulfilling job. The world doesn't get better because I managed to more efficiently query petabyte-sized databases of marketing info.

However, I love my current DevOps role. My work directly impacts patients lives and I architect solutions that make my corner of the world a better place. I design from scratch, then I package it all neatly and deliver it to the ops team that then run/support/maintain it. If something breaks or new features are needed, the jr people take first crack at it. Then, if they can't handle it, it gets dropped in my queue whenever I have time. The center I work for literally saves lives, and I'm happy to be a part of it. Job satisfaction can be more than just the day-in, day-out tasks you do.