4 ms·
I've been hiring in the valley for the last 12 years, starting off in the interview chain at Netscape in '96, and moving into management at my current organizat
by ghshephard 18y ago
I've been hiring in the valley for the last 12 years, starting off in the interview chain at Netscape in '96, and moving into management at my current organization in 2003. Since I moved into management, and end each interview chain (with a candidate that I am the hiring manager for, and have a candidate that I think we will bring on board), I have always ended the interview with three questions: Do we have your application filled out, When can you start, and "what did you make at your last company."
"What did you make at your last company" is a valid question, and I know of no employer (at a Silicon Valley Company) that has instructed their employees to _not_ tell future employers what they make. It is, of course, considered good taste not to discuss compensation (Stock or Salary) with coworkers - but it's remarkable that there aren't typically company policies against that. (There are exceptions, I'm sure)
The thing is - you _need_ to color that answer. Don't just say "I made $150K/year as a Sysadmin at my prior company", it's fine to say "They were paying me $150K, but that was probably an outlier, and I'd be very comfortable making $115K." Or, "I was making $90K/year, but I'm looking to make $115K at my next engagement" - You probably know (through salary.com, your colleagues at other companies, etc..) what the market will pay for your skills - and that is the number you need to communicate during the interview, what you are _worth_. It is as destructive and harmful to a career to be paid more than you are worth, than it is to be paid less than you are worth.
The employees being overpaid are always the very first ones to be laid off, while their less skilled, but more appropriately compensated colleagues, are kept on. And, when you aren't being laid off, if you aren't delivering to your compensation level - you are never receiving positive performance reviews - even if you are performing at a much higher level than someone less well compensated - makes for a stressful work environment. (There is more to a job than money.)
Speaking only for myself, any candidate who starts going down the road of "I won't fill out employment application until we are interested in each other", "I won't discuss previous salary", "I won't provide references until there is an offer letter", etc... - just screams "Prima Donna"
That strategy might work if you are a very strategic hire, with very specialized skills, in a very tight job market - but in general, life is too short to have to manage those type of personalities, and I'd rather just take a pass and bring on someone who is willing to work _with_ me, and not _against_ me.
- Locke 18y agoI'm not sure your post deserves to be downmodded -- it seems honest and on topic. I can see how one bit in particular could come off as slightly offensive: 'Speaking only for myself, any candidate who starts going down the road of "I won't fill out employment application until we are interested in each other", "I won't discuss previous salary", "I won't provide references until there is an offer letter", etc... - just screams "Prima Donna"' This is a matter of trust. Salary history, a detailed employment history, and references are private. In the case of references it would be down right rude, to repay the people who are willing to vouch for you by spamming their contact info to anyone who asks. There is nothing unreasonable about withholding that info until both sides clearly serious about moving forward. If anything, I wonder what your cavalier attitude screams about you?
- ghshephard 18y agoSo, In a world of Networks that need to be built, customers that need to be deployed, ticketing systems that need to be improved, Post Mortems that need to be completed, and Network Architectures that need to be visioed - I simply don't have time/energy or, even the _ability_ to deal with someone who isn't going to throw themselves 100% onto the team. And that starts at the interview. Perhaps it's a reflection on how I perceived the employer/employee relationship. The interview is a (very poor) proxy for what the work relationship will be like with the candidate in the future. Firing people is such a major, major hassle (particularly as you get bigger) - that unless the person is grossly incompetent or breaches company policy in an unambiguous manner, you typically have to wait for the next round of layoffs to get rid of them, even if they are difficult to work with. What this means, is that you are looking for all the danger signs you can during an interview - and hiring someone who is going to "Stand up for their rights" or "as a matter of principle, not share detailed employee history", is fraught with risk. Both of those actions are entirely reasonable in and of themselves, but, for better or worse, they portend, for the potential employer, risk. And I guess that's what I was trying to get across (from the perspective of an employer) - that rightly or wrongly, your actions in holding back information or challenging the employer in an interview, will be sending clear signals. If you are a strategic hire, or if the job market is tight, or if you have some very, very specific skills - then you can probably afford to negotiate hardball, and be as difficult as you want - they aren't hiring you for the person that you are, but the things that you can do - but, in the 95% of the time a hiring situation is taking place, that is not the case. [added: And as far as spamming references - ask anyone who hires; actually getting around to calling references of people you are _hiring_ is hard enough - I don't know if I have _ever_ contacted a reference unless a salary, start time, and position where pretty much agreed upon. And I'm better than most at getting around to that task. ]