4 ms·
I would not be surprised if the difficulty relevant to scenarios like the OP is the nature of re-negotiation. She started at what was likely a quite reasonable
by Goladus 11y ago
I would not be surprised if the difficulty relevant to scenarios like the OP is the nature of re-negotiation.
She started at what was likely a quite reasonable $40,000 salary for an unproven undergraduate. Then was hired on shortly after at that rate because it was convenient for everyone.
The problem is that her performance (value) busted the curve and quickly out-paced the percentage-based raise system. Some companies do "corrections" every so often, in fact I have benefited twice from that sort of thing.
It's probably safe to say though, that you probably don't want to sit around waiting for "market corrections" if you're being underpaid.
- eropple 11y agoMan...c'mon. Nobody goes from forty to eighty because they're an "unproven undergraduate." They go from forty to eighty when somebody's screwing them and gets called on it.
- Goladus 11y agoWhat part of this sentence do you fail to grasp? The problem is that her performance (value) busted the curve and quickly out-paced the percentage-based raise system. I figure it was implied that either no one noticed or had the willingness to take any personal risks to circumvent the system to fix her salary.
- eropple 11y agoIt isn't what I fail to grasp, it's that I reject the idea that one's performance can break such a curve in a developer job unless the person in question was underpaid to begin with. That doesn't happen unless the deck is stacked. It just does not.