Re:How to write a developer resume that will get you hired
by kasey_junk on Monday November 10, 2014 @12:15PM
(#8584769)
When I'm on either side of the desk, I don't assume that it is the employers job to get a candidate to work for peanuts. The marginal cost difference between what a good candidate is worth to me, and what I can effectively negotiate is tiny in comparison to getting the candidates I want.
That is, it is much more expensive for me to get the wrong candidate, than to pay a little too much for a good one.
Re:How to write a developer resume that will get you hired
by JoeAltmaier on Monday November 10, 2014 @01:51PM
(#8585432)
But do you offer what they're worth? Or do you have some plausible equation of position and experience. Then you tell the candidate about pay ranges and bonuses etc. Then you pretend to haggle over a 1% bump and some one-time perks.
If we're being honest, early Engineers on a project can create millions in wealth for the investors. That they're paid a few percent of that is where the 'peanuts' come in. It all seems reasonable the way its laid out.
As a consultant, I charged many times what I'd earn as an employee. And they paid - because they were in a tight spot, and the only way to get the job done was to pay what it was worth. And that's arguably what their own Engineers are worth too, but have been negotiated down from.
All the talk of respect and time wasting and efficiency is missing the point. Arrogance is a tactic and if it works for you at your level, then more power to you.