Yeah, even middle-tier systems admin types can approach that range (80k is more typical, higher if you manage to sell yourself as DevOps), and it's higher in larger cities/tech hubs (e.g., Boston, Atlanta, NYC), albeit with worse cost of living.
Senior-level niche software dev positions usually pay absurdly well; 150-200k is not unheard of for things like, say, COBOL finance software maintenance, legacy Java EE stuff that hasn't been migrated off JEE2 or whatever, and vendor-specific ERP shit, although those tend to be on a contract basis while the company in question brings you on to get them the hell off of an expensive-ass outdated legacy platform.
Those old-ass billing and finance systems just refuse to die. And, weirdly enough, the COBOL spec keeps getting updated by Fujitsu and IBM -- they added classes and objects back in 2002, so there's at least some semblance of potential for (non-module-bullshit) code reuse and unit testability. But it's still goddamned fucking COBOL. And if you're maintaining a legacy COBOL system, you'll be lucky if they've even moved off of COBOL-85 yet, since that code usually stays untouched for decades.
Yeah, even middle-tier systems admin types can approach that range (80k is more typical, higher if you manage to sell yourself as DevOps), and it's higher in larger cities/tech hubs (e.g., Boston, Atlanta, NYC), albeit with worse cost of living.
Senior-level niche software dev positions usually pay absurdly well; 150-200k is not unheard of for things like, say, COBOL finance software maintenance, legacy Java EE stuff that hasn't been migrated off JEE2 or whatever, and vendor-specific ERP shit, although those tend to be on a contract basis while the company in question brings you on to get them the hell off of an expensive-ass outdated legacy platform.
deleted by creator
Pretty much, but hey, if it's a 9-5 with no overtime expectations, you can support a surprisingly expensive
gamingdrug habit on that kind of salary.deleted by creator
COBOL in c.e. 2020
Those old-ass billing and finance systems just refuse to die. And, weirdly enough, the COBOL spec keeps getting updated by Fujitsu and IBM -- they added classes and objects back in 2002, so there's at least some semblance of potential for (non-module-bullshit) code reuse and unit testability. But it's still goddamned fucking COBOL. And if you're maintaining a legacy COBOL system, you'll be lucky if they've even moved off of COBOL-85 yet, since that code usually stays untouched for decades.