I've heard that once before and it always puzzled me. Basically you're telling the candidate that you want to underpay them now, so you can eventually pay them what they are worth. The math is in their favor even if they don't get a raise next year. And of course, next year they will be worth more anyway because they will have another year's experience plus additional domain knowledge.
I'm curious if anyone has ever fallen for that line.
The quote is saying that the employee will be at the top of the budgeted pay range for that position, so their salary won’t grow much at all year over year.
I’m unclear on where you’re getting “underpay” from. Perhaps you’re assuming that the budgeted salary is below fair market value, and there’s a vague promise to increase the budget/salary in the future? Not sure why anyone would take the position in that case.
That said it feels kinda nice if the company gives you a raise without you even asking but it does mean you were basically underpayed vs. what you might have gotten.
I'm not sure where "The assumption is that the candidate is already worth the top of the pay range for the position" comes into this. As a potential employee, i want to maximize my $$$. How much the employer thinks i'm worth is the employer's problem not mine. If the employer gives me a choice that i can either (a) make more money or (b) make less money, i am going to choose (a), and i don't know why anyone would chose (b), all other things being equal.
I think its good to communicate that they wont be getting raises. I've taken a few jobs where I've been paid well above average, it feels great then you dont get any pay rises for a few years which makes you feel like you're aren't doing a good job.
Stared at this for a while, and can make no sense of it.
1. Bend policy at hiring. $250k. $250k. $250k. $250k. $250k. $250k (no raises)
2. Follow salary brackets. $200k. $210k. $220k. $230k. $240k. $250k (low initial salary, catch up over time)
Having been on both sides, it's nearly impossible to make the case for bending policy further at annual reviews. Over time, employees converge to pay brackets. If you were hired with a on-off exception, you're getting no raises for a long time.
No raises feels shitty to a lot of people. It also brings risks.
True story: I was hired by a not-for-profit doing good work. Pay was maybe 1/3 of Google, and I'd be the top tech person at the org (not by ladder, but by skills). Pay was about 85% of what I needed to cover cost-of-living. They stretched brackets to get up to covering my cost-of-living exactly, so I was almost 20% over the upper cap of my pay bracket. Come next re-org, what do you know, they re-jiggle salary brackets standardize things, and my salary comes down 20%.
Fortunately, in the meantime, my cost of living had come down, so it worked out okay. I'm doing important, fulfilling work, and it's fun. So long as I'm doing that and making ends meet, I'm not tempted to jump ship to FAANG.
And no, my employer wasn't simply f-ing me; I understand the organizational structure, psychology, and dynamics well enough to understand what happened, how, and why. These were dynamics well above anything my boss, their boss, or their boss has any influence over, and I'd rather spend the social capital of going to their boss on something more important (e.g. making sure everything I do is open source).
A common career mistake people make is to assign intentions to places where the other side has no control. If you're worth $350k on the free market, and you receive a $180k offer, odds are the other side isn't low-balling you or doing anything mean or improper. They're operating from their constraints. You're operating from yours.
If you need $350k, and they can spend up to $500k, you'll be hired, and how well each side negotiates sets at where you'll get paid. If you need $350k and they can spend up to $200k, you're not getting hired, period. It's good to discover that earlier rather than later, but in practice, that usually comes up after the interview. In the no-hire $200k/$350k case, although you might not get a job now, things might change in five or ten years, and it's good to leave without bad feelings, and I'm not just talking about expressing bad feelings, but about what you're actually feeling. If you come out thinking "low-ball exploitative !@#$%," that's not very healthy; if you come out feeling "good people; no fit; difference in expectations; maybe next time," that is healthy.
I generally want to understand what someone's ask is first.
After that I'm usually very upfront (ie, immediate verbal feedback) on how that falls into the position vs their apparent skill set etc.
If they have come in low (not uncommon for non bay area folks) I'll let them know that there are opportunities for growth beyond where they would start at. If they are someone we want we'll generally beat their ask as well to get them where they should reasonably be. Then usually there are two years of substantial pay increases. My own experience, these tend to be great folks to have on team if you can give them 3 years of nice growth.
If they are too high I'm usually upfront that at that rate they'd be flat compensation wise for a number of years or that the amount is simply too high relative to skill for position and our needs.
It used to be market was so tight, that if you found a great person you could go 2x what the planned budget was. Not sure if all orgs have that flex so that makes it a bit unusual.