114
what's the highest increase in salary you've had or seen? (programming.dev)
submitted 3 years ago* by to c/programming@programming.dev
107 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
[–] 24 points 3 years ago (35 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

  • permalink
  • fedilink
  • source
  • hideshow 35 child comments
    •
  • [–] 10 points 3 years ago (21 children)

    So, what happens then?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 21 child comments
    •
  • [+] 24 points 3 years ago* (last edited 2 months ago) (7 children)
    [deleted]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 6 points 3 years ago* (5 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 1 point 3 years ago (4 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 years ago* (3 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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 1 point 3 years ago (2 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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 3 years ago (3 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 3 years ago (2 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 3 years 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

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 3 years ago (8 children)

    A stare and patience contest begins.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 8 child comments
    •
  • [–] 2 points 3 years ago (7 children)

    As a manager that contest would be ended instantly and I'd tell you to give me a number or get out

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 1 point 3 years ago (6 children)

    Then you’re a bad manager, that’s not how negotiations work lol

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 1 point 3 years ago (5 children)

    You're not negotiating by refusing to give a number. At this point you denied the negotiation that was started by me asking for your expectation.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 2 points 3 years ago (4 children)

    Unless you have enough knowledge of pay for your position and industry you are operating at a disadvantage. You are not obligated to provide a number to start the negotiations, and asking them what the budget is is not “denying the negotiation”

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 1 point 3 years ago (3 children)

    You are interviewing and the interviewer usually asks the questions. After all the interviewer already has a job and you are supposedly looking for one. In this scenario you are always operating at a disadvantage, because I know the budget and you don't.

    You are not obligated to provide a number by law or anything, but if I ask for one and you go "no you" that is just... Weird and unprofessional.

    I'll end the discussion here though and wish you all the best with your future negotiations. I just wanted to provide a counter point from the perspective of an IT manager.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 2 points 3 years ago (2 children)

    I’m also an IT manager. I lead a large team and manage managers and engineers from entry level to staff engineer. If I interviewed with you I’d skip out the door and tell everyone to avoid your company like the plague.

    It’s dishonest to say “it’s ok for me to ask the candidate to name a salary but not ok for them to ask me.” That’s how we get pay inequity and ensure that workers’ power is diminished. “Usually the interviewer asks the questions” is WILD. I make sure to give candidates multiple opportunities to ask questions and provide honest answers. The idea that they would begin to ask a question and I’d say “well thanks for your time but we’re done here” is legitimately hilarious.

    Maybe you’re hiring for extremely entry level positions (like…cashier) or something where the job is extremely well defined and you’re looking for a pair of hands to do a job but I want to hire the kind of people who ask these questions.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years ago (1 child)

    The idea that they would begin to ask a question and I’d say “well thanks for your time but we’re done here” is legitimately hilarious.

    Lmao I did never say that. You can ask questions but I cannot tell you about confidential information, e.g. the exact budget. After all you could just be someone sent from a competitor.

    Something you probably should know as a manager.

    That’s how we get pay inequity and ensure that workers’ power is diminished.

    Ehm no, as a manager you can circumvent that very easily by just paying people the same amount or offering the same amount at least.

    Maybe you’re hiring for extremely entry level positions (like…cashier) or something where the job is extremely well defined and you’re looking for a pair of hands to do a job but I want to hire the kind of people who ask these questions.

    That is a very euphemistic way to describe a lack of roles and responsibilities within your company. That is something I would avoid like the plague.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [+] 8 points 3 years ago (5 children)
    [removed by mod]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 4 points 3 years ago (4 children)

    Why not be pushy? Why not be willing to walk away? Everyone’s situation differs but a server tech is not going to be lacking for work opportunities. If it’s calculated individually, you say “ok what would it be in my case?”

    If they say “it depends on what you’re paid now” that’s a HUGE red flag and you should walk

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 3 years ago (1 child)

    this is a conversation you usually have before the technical stuff. you’re making sure your ideal pay and their band is in sync.

    being pushy early in the process is terrible advice.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] [S] 1 point 3 years ago

    Yeah, in my case, the decision to hire me had been made, but HR would of course onboard me. I got kind of blindsided as the person who asked me wasn't the person who would be making the decision, she was basically a proxy. I asked what the range was and I got some generic "it depends".... I checked most of the boxes for skills but I don't have a degree and for some reason that's off-putting to large companies. Anyways yeah it didn't feel right to be pushy so early

  • permalink
  • fedilink
  • source
  • parent
  • [–] 4 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] [S] 3 points 3 years ago (1 child)

    https://www.tiktok.com/t/ZT86J7mpN/

    That was basically how the meeting went lol

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 3 years 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

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 3 years ago (3 children)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [+] 2 points 3 years ago (2 children)
    [removed by mod]
  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 3 years ago (1 child)

    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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent