Role names in most software companies that I've worked at and know of are almost completely arbitrary.
They're useful if you have an organization that pays a specific rate for a specific job title, and they're useful in a hierarchical sense (e.g. managers, CTOs, etc). That's about it.
I install and maintain servers and desktops, databases, run backups, build infrastructure, source control servers, do low level programming, high level programming, frontend, backend, ... etc, it's too long to even enumerate.
As far as I'm concerned that's just being a (non-junior) software developer. It's all ultimately the same thing with different names to me, barely anywhere really needs people who are at the forefront in a tiny niche (i.e. _real_ specialists).
You can call me whatever you want as long as you're paying the bills.
They're useful if you have an organization that pays a specific rate for a specific job title, and they're useful in a hierarchical sense (e.g. managers, CTOs, etc). That's about it.
I install and maintain servers and desktops, databases, run backups, build infrastructure, source control servers, do low level programming, high level programming, frontend, backend, ... etc, it's too long to even enumerate.
As far as I'm concerned that's just being a (non-junior) software developer. It's all ultimately the same thing with different names to me, barely anywhere really needs people who are at the forefront in a tiny niche (i.e. _real_ specialists).
You can call me whatever you want as long as you're paying the bills.