Ask Slashdot: Should You Tell Future Employers Your Salary History?
An anonymous reader writes:
During the interview process for a technology job, I was asked to fill out an application which included questions about my compensation history. When I asked why, I was told that it was part of the background check and wouldn't be used to determine the size of the offer... What is the risk for the employer of not knowing that info? Is this standard procedure or part of a trend at technology companies?
The original submission asks if this is ever a legitimate question -- or more to the point, "Is it anything more than an attempt to gain negotiating leverage?" So leave your best answers in the comments. When you're interviewing for a new IT job, should you tell future employers your salary history?
The original submission asks if this is ever a legitimate question -- or more to the point, "Is it anything more than an attempt to gain negotiating leverage?" So leave your best answers in the comments. When you're interviewing for a new IT job, should you tell future employers your salary history?
If they ask your salary history, then ask the salary history of people who have held the position and the salaries of everyone at the table.
Earlier in my career I never gave my current salary, because I was looking for 20%+ raises each time and giving the information would probably only hurt me. But now that I am in my mid-30's and making far more than most of my counterparts with similar job titles, giving my salary helps ensure I don't waste time with any company which cannot provide similar compensation. Most companies don't realize top IT talent often get Senior manager / Director level salaries even without many if any managerial duties, so I need to weed them out quickly. Either that or they immediately start treating me as a consultant, because many companies are more comfortable with $150/hr full time consultants than $200k "permanent" IT staff members (even for long term gigs).
-- All that is necessary for the triumph of evil is that good men do nothing. -- Edmund Burke
Been at this since '81 or so, several jobs (scary to think of the percentage of companies I worked for that no longer exist). I've never once been asked for a salary history. They usually ask for the desired salary, which I leave blank. Let them throw out a number and start negotiating.
Works for me, every job I've ever gotten had a higher salary that the one I left.
Most interesting? I was interviewing at a company when rumors started to fly my company was going to have a layoff. I went to the manager in charge of my job (not my supervisor), asked to be laid off if the rumors were true. Got hired by the company across the street (not kidding, I walked to both of them, they were 1 mile away). Held off on turning in my 2 week notice and, sure as snot, got laid off a week later. Got all the benefits of being laid off, plus after a 1 week vacation I started my new job.
Another technique that works is: when a recruiter calls you, ask for $30k more than you really want. If the recruiter seems happy, then you asked too low (which means you should ask for $50k more next time). If the recruiter sounds a bit terrified, then you asked for the right amount. The last time I got hired, I scared away a lot of recruiters this way, but not all of them. The ones who weren't scared away were the ones I wanted to work with (and I got within $2.5k of my asking price).
to persuade people in a negotiation you need to be able to get some kind of source to be able to prove your claims.
No, there are plenty of techniques you can use. I strongly suggest reading this book, because you are going about it the wrong way. In fact, if you go up to your boss and say, "My salary is below average, here is proof," he'll probably look at your proof for a while, then say, "You are right, my boy. Let's talk about this during your next performance review and see what we can do for you." At the next performance review, you'll get a 2%-3% payraise, if you are lucky. To some degree, facts don't matter during negotiation.
"First they came for the slanderers and i said nothing."
The way I usually respond to "what was your previous salary" question is "Yes Sir, I know how to keep a secret. Next question please." It's like asking a salesmen the same question, if they are any good, they wouldn't respond or they'd game you. I prefer the honest approach just to see how stupid the headhunter is.
The only thing that matters is the value and opportunity I represent to your company right now. If I come along with a packed Portfolio, letters of recommendation from executives with dollar amounts in them, and so forth, the discussion needs to be how much or the offer to try the job out for a month, paid of course, and see how things go.
The only kind of employer that hires a head hunter to fish around for cheap labor (if you ever get a number on a phone call or an e-mail, or a very narrow salary range, it's fishing), or wants to know your existing salary upfront, is one that thinks of their employee's like any fixed piece of equipment and treats them as such.
If you get into the habitation of treating all people like fixed equipment, and treating all equipment the same, pretty soon the really great ones move on and all you are left with is a string of bad people. As a result, many of those businesses are an absolute nightmare to work for. They have an insatiable appetite to find ways to cajole, prod, and otherwise manipulate their labor into doing often immoral and unethical work; insecure people tend to need others around them to feel insecure as well.
Ignore them, let them die, go work for the competition.
The problem is, and this is from years of experience, applicants will still waste your time as a "backup" (or even "backup backup backup") option.
Also, many applicants assume that the range is "negotiable" and think that they can somehow, in the last throes of negotiation, get an offer over the top of the range. (They are wrong -- as a matter of principle I don't do that. If the headhunter kicks in $10K of their commission to beef up the "sign-on bonus", I'll do that -- and that's surprisingly common when closure is looking tenuous).
Most people, esp. those seeking high salaries, think they are better than they are (this is a common human trait - ask 100 developers if they think they are above or below the median skill level and I'll bet about 80% will assert that they are above the median). It's a waste of my time and the team's time. I've got code to write (well, usually designs to review but...) and they have code to write -- interviewing, unlike developing software, is not something we do because we enjoy it.
Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading