You make a decision using a baseline, and you can use surveys for that. Yet most of us are not really choosing from a number of jobs -- usually we're considering a specific offer.<p>Insteda, your current salary is a good baseline, because your current job is your BANA (Best Alternative to a Negotiated Agreement)<p>But while you're moving up to your next challenge, why not take a pay bump with that?<p>My question: Roughly how much more should I ask for?<p>It's gotta be >0%, because I've got my BANA, and it's the right time to take some risk.<p>But except in unusual cases, a 50% pay bump would look silly.<p>This article at FiveYearItch http://blog.fiveyearitch.com/2013/01/what-do-software-engineers-want.html says that their average for comfortable, anonymous, definitely non-desperate engineers is about +19%. Does that make sense? More?
Completely ignore your current pay and look at market rates. Go to glassdoor.com, indeed.com, salary.com, government data, anecdotal data.<p>When employers look at compensation on their teams, they don't say, Ok we pay people 19% higher than their previous job so that's our target for candidates. No, they look at their average pay package and what the market is paying to budget payroll.<p>If the company asks about your current pay and why you're asking for such a big bump, you can say simply that you're looking to be compensated fairly at current market value. You can add fluff like you're much more skilled and ready to take on much greater responsibility. Coming from a startup I always said that I placed a high value on my options. Don't let anyone talk you down from market rate.