this post was submitted on 19 Sep 2023
106 points (91.4% liked)

Programming

17670 readers
216 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 [email protected]



founded 2 years ago
MODERATORS
 

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
[–] [email protected] 22 points 1 year ago (5 children)

When someone asks what you were paid or what your salary expectations are, ask them what the budget is for the role. They have one. They will not want to tell you, and you shouldn’t tell them your expectations

[–] [email protected] 8 points 1 year ago (2 children)
[–] [email protected] 23 points 1 year ago (2 children)

They offer someone else the job

[–] [email protected] 5 points 1 year ago* (last edited 1 year ago) (1 children)

Yeah, exactly. People upvoted this take that won't work for 99.9999% of people lol

[–] MajorHavoc 1 points 1 year ago (1 children)

Negotiating hard works fantastically well for people who work in information technology.

[–] [email protected] 1 points 1 year ago* (last edited 1 year ago) (1 children)

It doesn't unless you're part of the absolute minority even in IT. You need to be really qualified for this.

I also again want to emphasize that not giving your expectation is not the same as negotiating hard.

Your run off the mill network guy or admin will not have success with this.

Source: Work in IT and manage people

[–] MajorHavoc 1 points 1 year ago (1 children)

I would argue that experienced quality - or even serviceable - IT is the absolute minority, to begin with.

There are organizations that aren't one bad day in IT away from starting a company-ending death spiral, but they're not typical.

Many CEOs and HR professionals underestimate that risk, but that underestimation is a self-correcting problem over time.

IT professionals may lose the current opportunity by negotiating, but their next opportunity isn't (statistically) far in the future.

As a bonus, employers who are averse to having IT employees negotiate tend to be lousy employers

[–] [email protected] 2 points 1 year ago (1 children)

I would argue that experienced quality - or even serviceable - IT is the absolute minority, to begin with.

It is, but the point still stands that you need to be extremely sought after to make it work WITHIN IT.

If you're applying for a CISO position and have 20 yrs experience it might work. That's the level we're talking about.

If you're a sysadmin and are applying for management of 50 windows clients you'll be out the door with that kind of negotiation.

IT professionals may lose the current opportunity by negotiating, but their next opportunity isn't (statistically) far in the future.

In my opinion the vast majority of interviewers will not take shit like that unless you're extremely qualified and money probably wouldn't be an issue to begin with.

I've conducted interviews in multiple countries in several continents.

If it works for you keep going of course. I just don't see that to be realistic or viable advice for most people reading here.

[–] MajorHavoc 1 points 1 year ago

If you're a sysadmin and are applying for management of 50 windows clients you'll be out the door with that kind of negotiation.

Fair point. My experience is with cloud admins. With so much going to the cloud, there's so much unmet demand for cloud administration.

Even so, most Windows sysadmins I've met have been able to land cloud jobs after a few attempts - and they tend to be great at it. The professional principles of a good senior sysadmins translate well to the new cloud ~~bullshit~~ stuff.

[–] [email protected] 2 points 1 year ago

Then you dodged a bullet

[–] [email protected] 2 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago (1 children)

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.

[–] [email protected] 1 points 1 year ago (1 children)

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.

[–] [email protected] 1 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

[–] [email protected] 3 points 1 year ago

even then, a position may not be for a certain level so they’re can be a fairly wide band of pay depending on how the interview goes.

i think most folks vastly overthink it. just ask for the money you want to make. either it’s in the ballpark or it’s not. all this “don’t say a number first” stuff is bullshit imo.

you definitely do want to know if your desired pay matches their range though. that’s very important.

[–] [email protected] 3 points 1 year ago (1 children)
[–] [email protected] 1 points 1 year ago

The NDA bit got me ngl

Truth is this is an antagonistic negotiation oftentimes. You want to be paid more, they want to pay you as little as possible. There’s unfortunately no playbook, just advice and experience.

FWIW if they were that evasive I’d just say “look I’m not going to name an initial number, I’d like you to name a range.” But I’m at a somewhat senior level so I have a different experience than others might

[–] [email protected] 1 points 1 year ago (1 children)

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