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

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
[-] originalfrozenbanana@lemm.ee 3 points 1 year ago

It’s a negotiation. Unless you have a lot of knowledge about the industry you’re working in and what market salaries are, you’re at a disadvantage. You don’t have to say a number. They do - they’re offering you a job. If they refuse to offer you the job until you tell them your salary desire, they are trying to low ball you and you likely don’t want to work there.

[-] teichflamme@lemm.ee 2 points 1 year ago

I have never been an interviewer or interviewee where you are not supposed to give a number.

Of course they try to low ball you. You counter act by giving a number that allows you to haggle. That is how negotiation works.

[-] originalfrozenbanana@lemm.ee 2 points 1 year ago

Supposed to? According to who? There is no law saying you have to give a number. They want you to give a number. That doesn’t necessarily make it a requirement.

[-] teichflamme@lemm.ee 2 points 1 year ago

I already answered that in my other posts.

I am the interviewer, I ask the questions. I always ask that question because it is required information for me within the hiring process. I need to make sure your expectation is in my budget.

I don't need to make the process unnecessary complicated by engaging in you not telling me.

If you won't tell me I'll either give you the minimum or ask you to leave because I really don't want to deal with people that make things unnecessarily complicated

this post was submitted on 19 Sep 2023
114 points (91.9% liked)

Programming

17314 readers
30 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

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 1 year ago
MODERATORS