Top Ways to Blow a Job Interview(fins.com)
fins.com
Top Ways to Blow a Job Interview
http://www.fins.com/Finance/Articles/SB129416698193872447/Top-Ten-Ways-to-Blow-a-Job-Interview?Type=4
19 comments
I have never sent a thank you note. Not for any job I've ever had. Not for those who really wanted me and fought for me and made me great offers, never. Perhaps I am rude, or perhaps companies looking to make money are not looking for "polite" developers?
And cellphones are rude, but it is not rude if you can not or forgot to turn yours off and it rings. It is not rude to apologize and briefly take the call if only to explain why you can't talk on the phone now. It is not even rude to strongly apologize further if the call turns out to be important and you have to take <5 minutes to deal with it. This applies equally to both sides.
And cellphones are rude, but it is not rude if you can not or forgot to turn yours off and it rings. It is not rude to apologize and briefly take the call if only to explain why you can't talk on the phone now. It is not even rude to strongly apologize further if the call turns out to be important and you have to take <5 minutes to deal with it. This applies equally to both sides.
Interesting, but
> 4. Wait a week to send a thank you note. Or don't send one at all.
got me thinking. Is it an American thing? What are you thanking them for anyway?
> 4. Wait a week to send a thank you note. Or don't send one at all.
got me thinking. Is it an American thing? What are you thanking them for anyway?
I've never sent a thank you note.
I've received maybe 1 from the ~200 interviews I've conducted in 15 years. ( The candidate that sent it was awful.)
Is anyone offended if they don't receive one ?
I can't say it would really make a big difference to get a "thank you" and I've never sent more than cursory thanks.
One thing I have done, though, when interviewing for a job, is to not ask all my ?'s when the interview enters the "what do you have to ask about us?" phase. I try to keep one in reserve and send that to someone in my interview loop after the fact. I feel that it shows continued interest in the position and I have never gotten a negative reaction from anyone for asking a follow-up ?.
One thing I have done, though, when interviewing for a job, is to not ask all my ?'s when the interview enters the "what do you have to ask about us?" phase. I try to keep one in reserve and send that to someone in my interview loop after the fact. I feel that it shows continued interest in the position and I have never gotten a negative reaction from anyone for asking a follow-up ?.
To me, sending a thank you email does two things: reiterates interest and keeps you in their short-term memory (consider that the company may have interviewed several candidates in a few days).
I've sent thank-you emails in the past. Never longer than two sentences, but it was always of the flavor, "I enjoyed speaking with you today, I hope to discuss the position more." I can't really say how much it helped, but I know it didn't hurt as I've had a couple job offers that way.
I think it's an anachronism. I've interviewed well over a hundred candidates for various engineering positions, and it's extremely rare to get a follow-up. The few that I have received came across as kind of stalkerly. But maybe that's just me.
The only situation I can imagine sending one is if a couple of weeks go by and you still haven't had any response after the interview (which usually isn't a good sign anyway.)
The only situation I can imagine sending one is if a couple of weeks go by and you still haven't had any response after the interview (which usually isn't a good sign anyway.)
What kind of follow ups have you gotten that seem stalkerly? Usually when I send them, I just say "Thanks for your time, I look forward to hearing more about the position."(albeit more professionally).
If they say, "Thanks for your time. I look forward to hearing more about the position-perhaps when you arrive tomorrow at 8:15 in the parking lot? I'll have your favorite latte in hand" then I would agree that it's stalkerly :)
If they say, "Thanks for your time. I look forward to hearing more about the position-perhaps when you arrive tomorrow at 8:15 in the parking lot? I'll have your favorite latte in hand" then I would agree that it's stalkerly :)
I'm an American and have never and would never send a thank you note. They need me, I don't need them.
Yeah, I thought that one was interesting. I can't imagine hiring or not hiring a candidate based on whether they sent a thank you note, and I certainly don't expect a handwritten note! However, if a candidate follows up in email with some answers / examples / code / whatnot for questions that came up in the interview, that would be a good sign.
... I signed up here to ask the exact same thing.
> And if you really don't want the job: "Take a call during the interview from a girl you just started dating and sweet-talk her."
Priorities, priorities... :)
Priorities, priorities... :)
Top Ways for a Company to Blow a Job Interview
1. Make me wait in the waiting room past our appointment time. My time is as valuable as yours.
2. Make me meet with Human Resources first. My time is as valuable as yours.
3. Make me fill out forms. This can be done in advance. There's this thing call "the internet".
4. Don't shake my hand. (I have no idea why this happens, but it does.)
5. Begin the conversation with anything other than, "Hello," or "Nice to meet you." Again, why would the first words of any interview be, "How would you handle mass emails?"
6. Don't give me your business card. As a job applicant, I'm just as important as any vendor or business associate. This is a good chance to demonstate it.
7. Criticize my job history. Here is the reason I've had 9 jobs in the past 5 years: Because there were poorly run businesses, assholes, and mismatches. The reason I'm here is to try to fix all that. Move along.
8. Expect me to have 10 years experience in every possible technology your entire enterprise uses. I can learn what I need. Promise.
9. Ask me how many gas stations are in the United States, how many ping pong balls fit in a bus, or why manhole covers are round. Frankly, I don't give a shit. There, now you have the results for both your I.Q. test and your personality test.
10. Don't follow up. I know that I'm probably not the only person your interviewing and this may take some time. Extend me the same courtesy you would the window washers. Don't make me email you every week.
1. Make me wait in the waiting room past our appointment time. My time is as valuable as yours.
2. Make me meet with Human Resources first. My time is as valuable as yours.
3. Make me fill out forms. This can be done in advance. There's this thing call "the internet".
4. Don't shake my hand. (I have no idea why this happens, but it does.)
5. Begin the conversation with anything other than, "Hello," or "Nice to meet you." Again, why would the first words of any interview be, "How would you handle mass emails?"
6. Don't give me your business card. As a job applicant, I'm just as important as any vendor or business associate. This is a good chance to demonstate it.
7. Criticize my job history. Here is the reason I've had 9 jobs in the past 5 years: Because there were poorly run businesses, assholes, and mismatches. The reason I'm here is to try to fix all that. Move along.
8. Expect me to have 10 years experience in every possible technology your entire enterprise uses. I can learn what I need. Promise.
9. Ask me how many gas stations are in the United States, how many ping pong balls fit in a bus, or why manhole covers are round. Frankly, I don't give a shit. There, now you have the results for both your I.Q. test and your personality test.
10. Don't follow up. I know that I'm probably not the only person your interviewing and this may take some time. Extend me the same courtesy you would the window washers. Don't make me email you every week.
Well said. #8 really resonates with me. There has never been a time when I haven't been able to get up to speed on a new stack/toolset within a few days (weeks at most). Why, oh, why can't companies just focus on hiring smart/curious/motivated problem solvers? I happen to think it comes down to lazyness - it's too hard to find those people, so companies resort to keyword soup.
I agree with all of these, but I'm glad you brought up points 7 and 9.
As a job applicant, you don't always know how bad things are or will be until after you start working there. Sometimes, the job starts out OK, but things get progressively worse over time. Am I supposed to voluntarily endure a crappy situation that has no end in sight, so that my next employer doesn't think I'll leave too fast? You should be able to explain that kind of thing in an interview without it being considered a mark against you.
As for #9, too many places ask these types of questions when the job you're applying for amounts to cranking out CRUD web apps. I think it's just cargo-cult behavior from old Microsoft interview techniques. If the job will require the unorthodox, creative thinking the employer is trying to test for by that question, a better way to do that would be to see if I have any actual projects, apps, open-source code that I actually wrote that demonstrates this ability.
As a job applicant, you don't always know how bad things are or will be until after you start working there. Sometimes, the job starts out OK, but things get progressively worse over time. Am I supposed to voluntarily endure a crappy situation that has no end in sight, so that my next employer doesn't think I'll leave too fast? You should be able to explain that kind of thing in an interview without it being considered a mark against you.
As for #9, too many places ask these types of questions when the job you're applying for amounts to cranking out CRUD web apps. I think it's just cargo-cult behavior from old Microsoft interview techniques. If the job will require the unorthodox, creative thinking the employer is trying to test for by that question, a better way to do that would be to see if I have any actual projects, apps, open-source code that I actually wrote that demonstrates this ability.
#7. Agreed.
I had a recent interview at Apple, and was heavily criticized for my research background. They kept re-terating "we don't do research here", as if I was then supposed to do something about it.
I had a recent interview at Apple, and was heavily criticized for my research background. They kept re-terating "we don't do research here", as if I was then supposed to do something about it.
The only thing that's ever bothered me is when someone doesn't know the answer to a technical question, and then aggressively bullshits me.
Example: we ask, "so, you've used Perl OO before, can you write us an example class on the board". He does, and instead of "my $self = shift" or "my ($self) = @_" in the methods, he writes "my $self = $_". Easy thing to miss on a whiteboard, no big deal. We ask, "are you sure it's my $self = $_?" he replies, "yes definitely". We mention that it would be $_[0] or @_ or shift, but he starts yelling about how $_ and $_[0] are the same thing.
They're not. No hire.
(And if he had said something like, "oh, it's so weird looking on the whiteboard, I'm not really sure", that would have been fine. Next question, plenty of time to redeem yourself. But if you are going to yell about a trivial mistake... well, I'm glad we caught this in the interview. Not only do you not know Perl, you aren't even nice.)