Actually, I think "hire them on a temporary basis" is more egomaniacal than obsessing over job interview questions. For someone to work for you as a temp, they have to leave their current full time job and put their benefits in jeopardy. When you hire someone, you should be ready to commit.
I actually don't see what's so manipulative about asking a candidate what their decision drivers are. Every consultant who's spent a few years in the business knows to ask potential clients what their "key metrics" for success are. It's good to get everyone speaking the same language.
It's a strange kind of humility that demands that other people put their whole life on hold to see if it'll work out to join your team, isn't it?
Actually, I think "hire them on a temporary basis" is more egomaniacal than obsessing over job interview questions. For someone to work for you as a temp, they have to leave their current full time job and put their benefits in jeopardy. When you hire someone, you should be ready to commit.
In my experience, when someone is hired on to a new company, they are on a trial basis for a certain number of days anyway. This may seem less risky than being explicitly labelled as a temporary-to-hire worker, but they could still find themselves and their benefits in jeopardy if within that trial period either decides this is not as good a fit as the recruitment process suggested it would be.
I think that underneath the intuitive reaction we have to "temporary worker" vs. "permanent worker on a trial basis", they're actually very alike from an individual risk perspective. Either way, in 30/60/90 days, you could find yourself unemployed and still in the same bind. There may be benefits consequences the direction of a temporary worker, especially if you are temped through an agency. On the other hand, that agency might find you another role if the one you are in doesn't work out.
There may be a different discussion about whether or not having this trial period is right, or ethical, or good business, or whatever, regardless of what whatever label gets put on it. My stance on this is that a good process will inevitably make very bad decisions from time to time, and it's not always the best idea to force those bad decisions to be irreversible.
Maybe my experience with the occasional mistakes of what I've seen as otherwise good processes in my past has made me a little less hard-lined about this.
I somewhat agree with you in a sense that it's not on in my books to ask someone to put their aspirations on hold while I figure out if "they are the right fit".
Man up and make the call about what you feel for a candidate.
What most employers don't do - either by system or personally - is man up and admit they hired the wrong person, replace them with severance and move on. Very few people actually do this. Why not?
A candidate who is at an elevated risk of being replaced by severance, which is a position most new hires are in, is probably putting their aspirations on hold while you figure out if they are the right fit. Severance is typically enough to keep an employee above water for a time while they find a new position that fits them better, but it certainly isn't anything people can build dreams on top of.
I think there is a common point of view that wants to assume that recruiting a good fit is something that you determine based on a set of input, and then commit to. If you have to reassess at a later time, and especially if you have to reverse your decision, you've failed at recruiting, and in a way that is preventable in a deterministic way. Experience suggests that people who believe this do one of two things: either they attach an ethical weight to the employee/employer relationship that means you have to weight the cost to your business against the cost to your sense of self-worth; or, they have gotten lucky enough up to this point to meet/interview/hire people who have not misrepresented themselves or otherwise projected an image that they would be much more valuable than they proved to be.
Having been involved in a number of instances in the last two years that have exposed me to the randomness of recruitment and hiring, even using all of the hacks people use to remove the error, I'm honestly a little surprised that people can have any imperatives about recruitment. The whole things seems at best stochastic, and errors are unpreventable.
I think the reason why people are so reluctant to man up is because it means they failed at something we believe they shouldn't fail at. I would argue they've failed as something we all fail at, and that accepting that will make the whole process better for everyone.
> What most employers don't do - either by system or personally - is man up and admit they hired the wrong person, replace them with severance and move on.
For better or worse, that is legally difficult in many places. Once you commit to hiring a permanent employee, you are obligated to some extent to try to work with them and resolve any problems. Firing them outright can be almost impossible unless either their position is literally redundant (in which case obviously you won't immediately be hiring someone else to do the job, will you?) or they are guilty of gross misconduct (such as doing something that involved the police being called to remove them from the office).
It seems common in the jurisdictions I know about for the full employee protections and benefits to kick in over a period of time, maybe on a sliding scale so they aren't fully in effect until a year or two after taking a job, so it's not completely one-sided. But you definitely get employees who play the game and make things that IMHO should be their personal responsibility into an employer's problem. For example, here in the UK there are rules about statutory pay for things like maternity leave. It's not uncommon for someone to take maternity leave for several months, with their employer required to keep paying them at a certain level throughout, and then not go back to work at the end. The problem is, sometimes an action as significant as having a child really does change your perspective and priorities that much, and the employee did go on leave genuinely expecting to return, and other times they knew damn well they weren't coming back the moment they walked out the door but cashed in anyway, and there's no objective way to tell the difference.
To a larger company, where this isn't going to happen very often, you can to some extent write it off as a cost of doing business. But to a small company, being down a member of staff at all can be seriously damaging, and paying out a load of statutory benefits and then getting screwed can literally cause your business to fail. But the rules are what they are, and as long as you have to play by those rules, any employer in such a context is going to be very careful about who they agree to hire on a permanent basis, and a probationary period after hiring isn't unreasonable IMHO.
I'm not aware of the maternity rules in the UK, but I believe that in Canada if somebody attempted the same thing and didn't go back to work they would owe the maternity top-up provided by the company. Of course, there is a certain amount provided by national/federal benefits, however that doesn't affect the employer net-net cash if they get that back.*
I agree though that there is a certain amount of uncertainty when folks are close to coming back from maternity leave. However, keep in mind that the organization (big or small) would have had to fill the position in any case during the maternity period.
* In Canada, maternity leave can take up to something like 50 weeks if the father chooses not to use up their paternity leave.
Just to add, I have a sizable chunk of money waiting to vest. For the right opportunity I would be willing to jump ship before then, but if you need some sort of trial period to make up your mind how about no. Also, like most talented developers I have a decent job, if you can't make up your mind quickly I am not interested. This includes a Google style interview process, if you need to schedule more than 3 hours of interviews sorry I have better things to do with my time than talk with you.
I've said this before, and I don't mind rehashing it here. It isn't meant as a personal slight in the least, your priorities are yours to have, but as someone who does hiring, I do not operate under any desire to keep interviews short for that exact reason.
If my interviews are a waste of your time, then you aren't likely to be the guy I want to hire. I want to hire someone who wants to work for me for more of a reason than to collect a paycheck. I want new hires to believe in our purpose, to fit in with our team, yadda yadda, but ideally, I'd like our interview candidates to actually _want to work_ for our company because they like or admire it independently of whether or not they are collecting their checks from us.
Perhaps I'm biased, but that ideal candidate, in my mind, doesn't consider an extended interview a waste of their time.
Actually, I think "hire them on a temporary basis" is more egomaniacal than obsessing over job interview questions. For someone to work for you as a temp, they have to leave their current full time job and put their benefits in jeopardy. When you hire someone, you should be ready to commit.
I think it's safe to go this way with jobless developers looking to get a job. If your candidate is on a full-time job, you should certainly commit.
You forget that there is another sub-set of people: the ones that just graduated and currently don't have a job. I think that for a recent college graduate the whole temp thing would sound to bad. Now, if you already have a job, then I believe you are more likely to play the whole hiring process game. When I was trying to get that first job, I absolutely hated the HR games. Now that I have a job, I know that I would be more indifferent to the whole random bs questions.
I actually don't see what's so manipulative about asking a candidate what their decision drivers are. Every consultant who's spent a few years in the business knows to ask potential clients what their "key metrics" for success are. It's good to get everyone speaking the same language.
It's a strange kind of humility that demands that other people put their whole life on hold to see if it'll work out to join your team, isn't it?