Ask HN: How do I negotiate a raise and promotion after 1 year at my company?

6 points by dotdi ↗ HN
Dear HN-ians,

this summer I had my first anniversary at the company I work for. I genuinely like it here and I'm a valued member of the department/team I work in.

However, while being a "software engineer" like some other colleagues, and not a "senior engineer" like others, I do more high-level work and have more responsibilities than my peers and seniors. That means I do e.g. architectures and specifications in addition to normal day-to-day work. I'm usually referred to as the technical lead for a very important, company critical project. I have the authority to decide how we are fulfilling customer requirements and I'm making sure stuff moves along (which doesn't happen when I'm sick or on holidays).

I have my 1-year review meeting scheduled and I'm not sure how to approach it. I, probably naturally, feel that a promotion and raise are in order, but there have been little to no signals from my superiors other than "we are so happy to have you on the team". I have a good relationship with my boss and his boss (which is the head of engineering), and I don't want to strain those relationships with, be it real or only perceived, improper demands.

Do you have any tips on how to approach this situation, as in, get promoted with everybody being super happy about what is going on?

Thanks!

20 comments

[ 2.6 ms ] story [ 62.2 ms ] thread
Make a list of all the stuff you do that you feel is beyond the role you are being paid for. Next to each item on that list write down how you think it helps the company.

In the meeting, use those points to illustrate why you think it would be a win-win for both parties if you got your raise and promotion.

Have a clear idea of what you are asking for in terms of money before you go into negotiation.

Negotiate based on facts and goals instead of needs and "time spent" or similar.

I genuinely like it here and I'm a valued member of the department/team I work in.

This statement is a red flag to me. Don’t get attached emotional to any company that you don’t have a substantial ownership stake in. It’s just a means to an end - to put food on your table.

You will know if they feel you are a “valued member of the team” when you get your annual raise. People pay for what they value.

If you look at your paycheck and look at the market and see the two are not in sync, start focusing on building your resume over the next year. If after year 2, your check and the market are not in sync, start looking for another job.

I usually recommend staying on a job at least two years.

I don't want to strain those relationships with, be it real or only perceived, improper demands.

Your “relationship” with the company is that you work for two weeks and they deposit money into your account - nothing more or less. If they don’t pay you at least market value - they aren’t holding up thier part of “the relationship”.

I think I disagree about the red flag part. Why should you not be allowed to like it and feel valued while not being a stakeholder. How do you know that there is no way for him to become a stakeholder at some point in the future? Ever heard of bonus and commission payments?

What's more I don't see how this comment answers op's question? Your general advice seems to be "just do not do it"?

I think I disagree about the red flag part. Why should you not be allowed to like it and feel valued while not being a stakeholder. How do you know that there is no way for him to become a stakeholder at some point in the future? Ever heard of bonus and commission payments?

My main point is not to get emotional over a job or your relationship with the company or your coworkers. I’m not saying that building professional relationships with your coworkers is unimportant, it’s the most important type of influence you have in the company.

As far as him “becoming a stakeholder through bonuses and commissions”, I agree. If they value him, they will place a monetary amount on that value....

You will know if they feel you are a “valued member of the team” when you get your annual raise. People pay for what they value.

———

What's more I don't see how this comment answers op's question? Your general advice seems to be "just do not do it"?

Other people had already posted good advice about how to ask. I’m giving the suggestion on what to do if it doesn’t work.

I’ve been cited as being “contrarian” before so this is another example I guess.....

https://hired.com/blog/candidates/hackernews-discusses-asses...

Can you please share why do you advice to stay at a company for 2 years? If someone is not getting challenging kind of work to push your knowledge and technology beyond limits? And how to portrait your accomplishments in resume for such role when u r just building API's
I did not advice anyone to stay at a company for two years. And I wouldn't advice anything that drastical based on a short HN text and some vague interpretation of what op is up for.

IF someone is unchallenged as you imply I'd say a good first step would be to talk to your superior before following a generic "change company every two years" advice for no reason.

The two years part was the “what works for 90% of the people 90% of the time” type of advice. From what I have read on HN and from my personal anecdotal experience is that a job stint of less than two years looks bad on your resume unless you have a good reason and a good story to tell - layoff, contracting, etc.

On the other hand, if you start interviewing after a year, what’s the harm? There are only two outcomes. You won’t find a job until year two and you won’t be considered a “job hopper” or you will and it doesn’t matter.

Can you please share why do you advice to stay at a company for 2 years? If someone is not getting challenging kind of work to push your knowledge and technology beyond limits? And how to portrait your accomplishments in resume for such role when u r just building API's
Generally, it's easier to get a raise by joining a new company than to get a raise at an existing one. Staying for 2 years seems to be the sweet spot between raising suspicions about job hopping and prolonging the stay in an underpaid position, whether or not it's really underpaid.
I'm not emotionally attached to the company. There are things I like, and those things outweigh the negative parts, so I'm not sure how this comes across as an emotional thing.

I'm not being paid below market, actually, I'm above market for a software engineer, but I think I'm doing more than "just a software engineer".

What I'm looking for is how to strategically do what I'm about to do keeping in mind that I see myself staying more than just another year to make it to the 2 year mark.

I'm not being paid below market, actually, I'm above market for a software engineer, but I think I'm doing more than "just a software engineer"

If you are more than “just a software engineer” and still an individual contributor with no reports, maybe you should look at salaries of “software architects”, “team leads”, etc. and see if your salary is still in the range.

What data did you gather to come to the conclusion that you are making above market? I’m not implying it’s not true, just confirming the data sources.

Your employment at the company being just a business arrangement between you and your employer, means that when you try to negotiate for more money, you both have a BATNA (Best Alternative To a Negotiatied Agreement). Your BATNA is finding another job and thiers is to replace you for someone who is willing to work at a rate they are willing to pay and lose the institutional knowledge you possess.

Finally, when I’m looking for a job, I have three priorities - technology, environment, and money in that order. There is nothing wrong with focusing on technology and environment over more money. That is a personal choice.

> see if your salary is still in the range.

From that angle, I believe I'm paid below market rate and you are right. I haven't clearly stated it in the Ask text.

> Finally, when I’m looking for a job, I have three priorities - technology, environment, and money in that order.

I completely agree. Technology and the environment are very good here, especially because I'm responsible a big part of the tech stack right now. My bosses listen to my arguments and do not oppose just because they can, i.e. we have healthy discussions on many levels.

BATNA is pretty good in my region because of significant engineer shortages even though I haven't talked to any other company while at this company. When I switched here, I had 6 offers lined up.

So wait for them to praise you, then immediately use it to ask for a raise.

If you want a real raise, and not some bullshit 2% adjustment, change your job.

It's strange that a tech lead would even ask a question like this. Which country are you in and how much do they pay you now?

I live in central Europe where inflation hovers between 1.5 and 2%, so anything in that ballpark would be just laughable, i.e. keeping my salary where it was until now.

I'm looking for something along the lines of "you are informally the tech lead, and starting with September you are also formally the tech lead, along with benefits and salary".

That brings up another interesting tactic that I’ve used. At one job that I was working contract to perm, when it was time for me to be made permanent, there was a hard cap on what they would pay me. I knew I would be leaving in a year anyway, so I asked for a title of “lead software architect”. The entire department of permanent developers was three people. I then used the title to apply for jobs making more.

In other words, even if you can’t get the raise you want, negotiate a title change. Companies generally don’t mind throwing around BS titles to make their employees feel good.

Go through the review and let them recognize your achievements. See what their action is first, they may already have a title and pay bump planned for you. If they announce your raise and it’s under your desired amount you need to ask for exactly what you want.

“I really appreciate the gesture and we’ve had a great year but I’d like to be earning $X/yr and be recognized with a promotion to Senior, which is more in line with the market and my responsibilities. I’ve felt this way for a while considering my work on x, y, z, but I’ve waited to ask since I know the review is the most appropriate time to ask. Is that in line with the salary band for Senior Engineer?”

.. frame it this way and it will preempt the most common rebuttals. Try to think about your boss’ potential responses and have a plan for them. Account for the fact that your boss may need further approval from upper management but ask for a specific plan and nothing loose like “keep working hard and I’ll see what I can do.” You want to timebox it. Same day would be great. It’s review time, the company is ready, this isn’t a surprise ask.

Your manager very likely wants the same thing you do so be courteous, appreciative, but also confident and direct.

List your achievements and ask for the promotion and raise. Do a couple mock reviews with your partner or friends to smooth out your pitch. Don't rely on them to recognize you, they are busy with their own jobs and may not notice all the work you actually put in.
This is not sales; programmers don't get "raises". The good thing is you can give yourself a raise by applying for a job at another company.

If you want more responsibility (i.e. a promotion), then you can sometimes get one by asking for it, but just be warned that this usually does not come with a raise in compensation.

Put counteroffer on the table in front of your boss.