Programming

17540 readers

81 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

114

what's the highest increase in salary you've had or seen? (programming.dev)

submitted 1 year ago* (last edited 1 year ago) by thisisnotgoingwell@programming.dev to c/programming@programming.dev

108 comments fedilink hide all child comments

I'm an 8 year data center network engineer who recently broke 100k for the first time. When I got asked my salary requirements I actually only asked for 90k as my highest previous salary was 80k with lots of travel, then I found out they gave me 100k because it was the minimum they could pay someone in my position. I've read before about people making crazy salary increases (150%-300%) and am wondering if I played it incorrectly and how I could play it in the future. I plan to stay with my company for the next few years and upskilling heavily and am eyeing a promotion in my first year as I've already delivered big projects by contributing very early. I've progressed from call center/help desk/engineer etc (no degree, just certs) so my progression has been pretty linear, are people who are seeing massive jumps in pay just overselling their competency and failing forward? Or are there other fields in IT like programming/etc that are more likely to have higher progression scales?

you are viewing a single comment's thread
view the rest of the comments

[–] 0x0@programming.dev 2 points 1 year ago (1 children)

I usually follow it up with a salary range and they end up matching the lower bound.

[+] mrsgreenpotato@discuss.tchncs.de 2 points 1 year ago (1 children)

[removed by mod]

[–] 0x0@programming.dev 2 points 1 year ago (1 children)

A range gives you flexibility. I hope for the high end, sure, but I know they'll go for the low end so I throw a range where I'd be happy with the low.

Since it's a range, it's easy to say No way I'd work for you for less than [low end].

If you give a fixed value they'll low ball it and you'll generally end up in.between theirs and yours, so you'll have to aim high.

[–] mrsgreenpotato@discuss.tchncs.de 2 points 1 year ago

If you give a fixed value they'll low ball it and you'll generally end up in.between theirs and yours, so you'll have to aim high.

Exactly. That's why you say a specific number, which you hope you'll get (which is a high end of your range), but in your mind be prepared to accept a lower offer (which is a low end of your range). If you say a range it's like if you said just the low end of the range, the high end doesn't matter anymore to the recruiter. That's at least what I've been doing recently and it usually works well.