3 ms·
So, 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 c
by ghshephard 18y ago
So, 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. ]
- brlewis 18y agoDo you always tell the people you're interviewing what the maximum budgeted salary is for the position? If the answer is no, then withholding their previous salary isn't hardball negotiation, it's simply negotiating on the same terms you are.
- ghshephard 18y ago"maximum budgeted salary" is probably a more relevant concept to large 1000+ employee company. I typically only know what the _minimum_ budgeted salary is - that is, the lowest skilled employee I can justify bringing into a position. At the top end, sky is the limit - if you can justify $200K/year based on contribution, we'll be lucky to bring you on board. And yes, I immediately tell all applicants at the conclusion of the interview process precisely what I think they can command in the peninsula economy, and at our company (65th percentile), based on what I know about their experience, the listed (and back door references), the local economy, and what our needs are. I don't negotiate salary - that's the number we offer them, and they can either take it or leave it. The information they provide on their salary, and the reason they are leaving their last position, just happen to be two pieces of information that feed into that final number. The difference, of course, being that I know very little about how smart they are, and how much they can get things done, whereas the candidate knows almost _everything_ about themselves. And having the candidate hold back that information just makes my job more difficult, rather than easier. Certainly not what I'm looking for in an employee. They should be able to walk into the interview and tell me to within $5K precisely what they should be making. Remember - I'm a hiring manager, not an HR staffer. I see my job in life to maximize my employee's compensation, ensure that they are making more at my company than they would anywhere else. Every single day consists of me trying to increase what my employees make by giving them more training, more tools, more projects, more guidance, more time to focus on what interests them. Also remember - it hurts an employee just as much to be overcompensated as it does to be undercompensated.
- prakash 18y agoAlso remember - it hurts an employee just as much to be overcompensated as it does to be undercompensated. Why? Can you expand on that?
- ghshephard 18y agoAs a manager, when we do both our employee reviews as well as rankings, we always take into account what an employee is making. Ideally, an employee is performing slightly above their pay grade at all times, so their is a consistent track record of pay increases, punctuated every so often by significant changes in job responsibilities. On a technical track, the typical valley growth pattern is from a low level helper, to a developer/technician, to an engineer/sysadmin, to an architect/Sr.Sysadmin. But, from time to time, something gets out of whack, and either an employee was poorly interviewed, lied about their previous salary, or was grossly overpaid, and they come into a job with far higher expectations than they are going to be capable of delivering on. Let's say that a solid Jr. Sysadmin, who's comfortable working around DNS zone files, configuring startup scripts, placing IP addresses on interfaces, and writing rudimentary scripts to automate all of this, should be making around $80K/year in the valley right now. Now, let's say they got hired into a Sr. Sysadmin role, at $120K/year and, in their first couple months, were expected to architect/engineer/deploy a global loadbalancing DNS architecture, complete with performance and redundancy capability, documentation, etc... This isn't unreasonable to expect of a $120K/year performer, so, when the individual failed to accomplish this, they are placed on a performance improvement plan, seen as an underperformer, and are taking up a valuable head count where someone else could have been performing those functions. They are mostly likely the first people to be laid off, and will be very unlikely to see a repeat of that salary, and will need to adjust to that fact. In a worst case scenario, it takes them 9-12 months to adjust to the fact that their next job will include a $40k/year pay decrease. On the flip side, if they had come in as an $80K/year Sysadmin, and performed well, they would have been seen as an asset to the team, and would have continued to have enjoyed both career as well as salary growth. Ideally they manage to dodge layoffs, and then, 3-4 years later, they are making $120K/year based on merit.
- netcan 18y agoas 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. In this case, why do you need these references before that point? A matter of principle?
- ghshephard 18y agoHaving everything on the application form just makes life so much easier. I realize for the candidate that getting to the point of being hired is a major event, that happens only once every 3-4 years, and so providing references is a big deal. On the other side, we're doing reference checks, even in a small company, with around 20-30 references/month. Keeping everying on an application letter means that we don't have to delay the process and do (even more) back and forth with the candidate to track down their references.
- netcan 18y agoWhen an applicant is expected to provide references, they probably call first to let these references know or ask permission. Since these are often not close friends, that isn't something you want to be doing multiple times. He/She must also reveal that they are applying for a job, something they may not want to discuss given the likelihood of rejection. If you are going to 5 - 10 interviews over the course of several months, that's a reasonable inconvenience to juggle. To avoid this the hiring company would simply have to obtain this information at a later stage. As you mention, they would have been in contact anyway to discuss compensation & such. A pretty minor detail. Some things are unavoidable: Writing a job application is more emotionally draining & time consuming then reading one. Interviewing less then being interviewed. But things like these really put to light the asymmetry: A major inconvenience for the applicant is acceptable to avoid a minor one for the employer. I think the reason you get such seemingly strident positions from the applicant side of the street is that it feels a lot like abusing the asymmetry.
- ghshephard 18y ago
- deleted 18y ago[deleted]