Is it rude to leave an interview early if you have already made your decision?
workplace.stackexchange.com
workplace.stackexchange.com
A company can end an interview early and it's not rude.
A company can terminate an employee without notice and it's not rude.
A company can change dress code and it's not rude.
That's not to say that people won't complain, just that these things are perfectly normal.
There were other times that the boss ended it early without consulting us. Only once was I unsure he should have done so. And again, the interviewee didn't know the difference. We did, because we do the same things every interview, and if some are left out, it's obviously short.
But we could get away with it because the interviewee had no expectations. The guy in the article, however, was there for a full day of interviews. If they cut it short, he'd know. And yes, it would have been rude, just like he was rude to leave.
But in the end, does that matter? If he stayed, knowing he wouldn't fit, he'd be wasting their time and his. Leaving saved them all time and money, and they should be thankful instead of upset. Their feelings were hurt because they thought they had an awesome place to work, and he didn't think so.
You can turn company and applicant around, what stays is that the money is saved on company side and time for applicant. The company or the applicant gets humiliated, who has to go home and tell someone (family/friends) that they didn't get the job. The company staff just continuous their routine, because that is company ritual.
Relatedly, the 2003 documentary "The Corporation" (http://en.wikipedia.org/wiki/The_Corporation_(film)) makes the case that if corporations are "people", they fit the psychopath personality type. Non-psychopathic people have a sense of empathy, a personality trait that corporations lack.
See http://blakemasters.tumblr.com/post/20400301508/cs183class1 and Coase's essay "The Nature of the Firm" for more on why they exist.
As another poster pointed out, an interviewee can usually profit from sticking out the interview, maybe learn something (even if it's learning what people don't know). At the least it's practice at suffering fools.
Same from the other side of the table. Most people don't know how to interview candidates; you all know this, because you've all sat through clueless interviews. But those people (you, if you've ever interviewed a candidate) are usually competent and nice people, they just don't have that particular skill or experience.
So follow through, do the whole interview, because you need the practice. You've brought an expensive learning resource into the office, so learn from him.
Finally, there's nothing wrong with being gracious and leaving the candidate with a positive view of your company and of you. Maybe he'll treat the experience like "dang, I've got some stuff to learn," rather than "those dudes are poopy heads." In any case it's as good for you to be gracious as it is for the candidate.
The situation was that the company, right before the code test, had told me a bunch of really weird stuff that wasn't part of the discussion right up until the last minute - it wasn't actually a job, but rather contract to hire; they needed to be ready if the next round of financing didn't come in, but they still expected me to move; I would legally be a consultant and therefore not have proper insurance; et cetera.
They wanted me to do this in exchange for admittedly fairly decent money and equity. However, the sudden, last-minute nature of the reveal really left a bitter taste in my mouth.
Then we got into the code interview, and the programmers started asking questions that made it pretty clear they only sort of barely understood what they were asking. One of them tried to "catch me on an error," and when I showed him the standard saying something else, he complained that I should just accept his viewpoint.
And at that point, I said "well you know what? This is a problem."
And so I just put the brakes on, hard. I turned over a far better solution to what they were asking than the question was structured to generate, said that I was sorry that I had consumed their time, but I was uncomfortable with the way that things had been done, especially that they had not been up front about the structure of the job, and I thought the interview was probably finished, and I appreciated the opportunity.
The guy who complained asked me to explain what I had handed over.
I disconnected, and decided I was happy I hadn't flown in.
There are a lot of people who, I suspect, will feel that this is me being unacceptably rude. I could have gone out in a more gracious fashion, et cetera. I've burnt bridges.
I look at it differently than that. I think those people need to know just how strongly their choices changed how I looked at them. I had been extremely bullish; I was super excited. They knew that. We'd been on the phone a lot, and I'd given them some help over the phone (small startup, lead engineer of dubious ability.)
And, they could hear the change in my voice when they pulled back the curtain on what they were offering.
They need to know that dirty pool like that is going to cost them, hard.
I believe I informed them of that in a fairly clear way. Your mileage may vary.
Or, from an alternate gender perspective, you're a woman and you've been dating a guy. The first night you stay over at his house, he gives you $1000 the next morning. You're probably going to be miffed because of the expectation violation.
You disengaged in a mature fashion and asserted your rights as a participant in the discussion. This isn't "being rude". Anyone who thinks it is likely has a very immature view of the world.
A job interview is a business negotiation. Emphasis on "negotiation". They changed the terms on you (or rather your expectation) - it's hardly surprising to expect a change of attitude on your end.
Frankly, if I ever have someone react like you did to me in an interview I would chase them out the door and take them for coffee. Interviewees that have the fortitude to walk out in a polite fashion are worth chasing.
I have been in many situations where someone wants to talk about a gig but tries to squirm it around to more of a favor on the promise of some future funding event paying me. I usually have more experience than the other party, in such situations, with the funding process and likelihood of their success in it. What annoys me isn't the over-reach, it's the deception. It's being treated like an idiot who cannot handle the truth by someone who fears the rejection that might come with being up front. Truth is I do freebies and favors all the time, when I have spare cycles, as I really want people who have ideas to be successful - and if I can help I love to do so. But they need to be honest with me up front.
Sounds like you were dealing with inexperienced folks (though I'm extrapolating from insufficient data so I might be wrong there). If so you have done them a favor by sending them market signals about what they're offering and what they can likely get in return. I think you're right about dirty pool.
Employers forget that interviews are two-way, and that a talented potential employee is scoping you out to make a decision as well.
They are too often used to having all of the power in the negotiation, they completely don't get it when the time comes to interview someone who isn't desperate.
The ego blow is hard for them to take when you turn them down.
That said, I think it is perfectly acceptable to leave; however, do your best to explain why & don't just duck out when no one is looking.
I watched with glee as their stock symbol got de-listed. I still have that manager's name on a do-not-hire-whatsoever list.
I was once chastised by a manager because I didn't boot a candidate after I was done, aborting the schedule. (He came to me while I was writing a negative review of said candidate.)
It turns out that the candidate offered to fight a later interviewer. I thought that the candidate was a jerk but that was a bit surprising. (The interviewer in question was a rather mild person.)
In my younger days, I had an interview at a casino. One of the job requirements they sprung on me was "unless you take vacation, you need to be within 15 miles of the casino". The casino was located in rural ND.
God, now that I think of it, I'm a prostitute.
Explain to the most senior participant possible (such as the hiring manager) or barring that someone from HR why you are calling it off early. Don't get huffy and spew on the staff as that's needless.
Culture mismatches may not be obvious to young inexperienced staff, but to management it's an obvious red flag for team work. And it's management's job to keep the team highly functional so they will thank you for your honesty.
If it's not going to work, it's not going to work. I've gone into in-person interviews with reservations, because sometimes my impressions are wrong and it's good to keep an open mind. But if it's beyond all doubt that it won't work, end it.
Even if you've received a personal recommendation from a current employee and don't want to make him look bad, it doesn't matter. You're wasting everyone's time by continuing.
I had this happen to me five years ago with a terrible interview process--embarrassingly unprepared interviewers, clueless HR, arrogant VP of engineering. They offered me the job and told me to go by HR, but I just walked out because I was so angered by the entire experience.
There was no reason to let it get to that point, though.
I think the "time wasting" aspect is the important part: most people don't want their time wasted and, ideally don't want to waste the time of others—or to raise their expectations.
No, this is to do with embarrassing and humiliating the interviewers in front of the other candidates. The example guy stood up and walked up in front of every other candidate and sent a clear message to them all. Having stuck his neck out he slightly undermines himself by showing he was not aware of how he got in to the room in the first place!!!!
Like I say, if done right you are doing the interviewers a favour by leaving as soon as you are clear you don't want the job. How you do that is every thing.
That said, you should talk with folks about your discomfort as well (you are interviewing them as well). So asking them if you could use your business skills would be appropriate too.
If you have decided you just don't like the company or the position, continue with the interview just to hone your interview skills and to be professional. But keep your answers succinct and don't fain enthusiasm.
A seasoned manager will get the message and will cut the interview short.
It may feel good to explain why you have no interest in working in a place where egos are based on coding standards adherence, it is better to maintain professionalism.
But that's not quite what happened here. As I understand the situation, the prospective employee thought he wanted the job when he went into the interview; but, during the interview he learned things about the place he'd be working in, and the people he'd be working with, that made him change his mind.
This is one of the main reasons that interviews are part of the hiring process: So the company and the individual can learn more about each other before a firm commitment is made, and cancel the impending hiring at minimal cost before it's final, if it becomes clear that that would be the better course.