3 ms·
I'd recommend reading Patrick McKenzie's (patio11's) article on salary negotiation for engineers: http://www.kalzumeus.com/2012/01/23/salary-negotiation/ http:/
by Pyxl101 10y ago
I'd recommend reading Patrick McKenzie's (patio11's) article on salary negotiation for engineers: http://www.kalzumeus.com/2012/01/23/salary-negotiation/ http://www.kalzumeus.com/2012/01/23/salary-negotiation/
Yes, they may all get squirrelly when you refuse to give that information, but this is often simply a tactic to pressure you into giving the information up. Stick to your guns.
One tactic I would recommend is to say, "I'd prefer not to discuss previous comp or comp expectations at this stage. I'd first like to get to know the company and learn about the opportunities for me there. If we decide that we're a mutual fit, then we can figure out the comp. I can be flexible on the comp, and it's only one factor I'll consider alongside others like how passionate I am for the project, my team, and the company mission, and the opportunities I see for further personal growth."
Your objective at this phase is to get past recruiting and into the interview process with potential fellow employees and hiring managers. Once there, if you do well and are a good fit, then they will start pulling for you. The force that a hiring manager brings to bear on that outcome is much greater than recruiting, and if the HM thinks you're awesome and wants to hire you, then the fact that you haven't given previous comp or expected comp to recruiting probably won't matter.
Recruiting may respond to this tactic by asking, "OK, let's say we match you with a completely ideal job, project, team, etc. What would your expected compensation be in that best-case scenario?" This question is a trick designed to get you to reveal your lowest comp number, i.e., the lowest compensation you'd accept if all the other aspects of the job were awesome and made up for it.