3 ms·

So do you feel the same way about backend developers who use databases? Surely that's two roles: server developer and database developer? Of course, they can't

• RockingGoodNite 4y ago
  It's a commonly accepted view that backend developers know databases. Until it is fixed, there are two major realms now due to Google (Angular) and Microsoft (TypeScript), backend and frontend. I was once a full stack developer but refuse to touch Angular gargabe or TypeShit.
• vsareto 4y ago
  TBH you could add Architect and DevOps if they're doing architecture/writing IaC as well. These all can be individual roles. The formula doesn't necessarily have to be salary times roles, but it should be higher than specific roles like front-end, back-end, DBA, QA, architect which can all ask for high salaries on their own. In my experience, full stack jobs often have salaries on par with the specific roles which is my beef. The biggest personal reason generalist roles should be priced higher is the time you spent to learn multiple things well enough to get a job doing them. If you accept a role as full stack that pays the same as a backend only role, you're essentially devaluing your own time. The other perks are reducing head count and giving the business that extra flexibility and convenience. If your salary doesn't reflect that, you're giving it away for free and we know how much businesses make us pay as consumers for convenience. It might seems strange to consider a lot of factors, but you have to remember that generalists can bring quite a lot to the table.