4 ms·
I had a friend and coworker who was in a similar situation, but not because of a career change. We worked on a piece of legacy software together. He was an incr
by AdmiralAsshat 8y ago
I had a friend and coworker who was in a similar situation, but not because of a career change. We worked on a piece of legacy software together. He was an incredible programmer, and five times the Java/Web developer as anyone else on the team, but because the legacy software was written primarily in C, and he was the "newest" member of the team, he was still the "Junior" dev. Even after being there for ten years. He was more or less consigned to that job title because Management freaked out at the idea that "they can't all be senior developers!"
- peteradio 8y agoThat management had poopoo in there brains.
- lifehacked 8y agoThat guy should have left, but he probably negotiated a salary commensurate with his true experience, with people who just love to code, I can imagine they would not care about the title, the real win is in the bank account. Call me a code janitor if you want as long as I get my 120k 4 weeks of vacation and my co workers are not total wads, I'd be fine.
- AdmiralAsshat 8y agoI'd love to tell you that he did, but no: he was a Steve Wozniak type--incredibly talented but too laid back and passive to know how to fight for himself. He passed away about a year ago from brain cancer and I found out his actual salary from his wife (peanuts, basically). That combination of crappy job title and egregious underpay continued to hamper him when he looked for other work, because the assumption from prospective interviewers was, "You've worked there for 10 years and are still a JUNIOR dev? You must be terrible."