My thoughts on full-stack is like your thought. It's a developer position. Once you start throwing in tasks that include the word "administration" in the description then that's likely a different job for a different person.

Hell, I thought "full stack" meant all the way down into OS drivers, and ability to debug damn near anything.

I joke that I'm a "full full stack" developer. Writing JS (bare, or in a framework like React or Angular or whatever), backend (Python, Elixir, Go, Ruby, etc...), install the OS or design cloud infrastructure, attach GDB or ptrace to processes if they're misbehaving, use tcpdump to watch packet flows, program kernel drivers, put together a toolchain and JTAG for microcontrollers, and design schematics & board layouts (analog or digital, not great at RF... yet).

Same and that ends up being in the operations wheelhouse.

< Dev who does Operations full time but is not "DevOps"

I agree that full-stack doesn't include ops and furthermore, it only refers to web developers.

I usually use the phrases Programmer / Operator and Computing Engineer to encompass the whole shebang.

I've considered calling my title FullStack++ because I'm full stack + devops, but I don't think any hiring mgr will understand that at later roles..

.. or are we just redefining the stack? I suppose db + api + FE is already a lot to call a full stack, but adding devops (not to diminish it) wouldn't really change the definition of full stack here..

But unless every full stack dev also knows devops, no one will know that I know devops too from my title.

Open to suggestions but until then I'm a "full stack + devops"