Saturday, June 26, 2010
Monday, June 21, 2010
Tuesday, June 1, 2010
After the Recruiter Says No, How to handle job-search rejections.
You had high hopes for this job: The job requirements matched your skill set perfectly. You aced your interviews. And you imagined hearing those sweet words so many of us long to hear:
"You're hired."
Instead, you got another rejection letter. According to recent U.S. Labor Department data, 5.5 unemployed Americans, on average, are vying for each job opening--so most interviews will end in rejection.
And that can be a crushing blow--but it can also be a career-making moment. When you don't get the job, what should your next steps be?
Don't beat yourself up about it.
John Kador, the author of "301 Best Questions to Ask on Your Interview," second edition (McGraw-Hill), recommends that you try to learn from each rejection--while understanding that it may not be your fault. "Sometimes you didn't do anything wrong," he says. "Someone else was more qualified or more connected. Companies sometimes go through the motions of interviewing applicants when they've already selected a candidate."
While the experience is still fresh in your mind, writing down what you've learned may help you put a positive spin on the experience--and give you something to refer to later, according to Lewis Lin, of SeattleInterviewCoach.com.
Be gracious in defeat.
How you conduct yourself after a rejection letter can determine whether that recruiter will consider you again--or perhaps refer you to another recruiter. Liz Lynch, the author of "Smart Networking" (McGraw-Hill), says, "Send a handwritten card thanking them again for their time, reiterating your interest in the company, and expressing your hope that they'll keep you in mind for future positions. And whatever you do, do not diss them on your blog!"
Ask for feedback.
Kador advises saying that you accept the recruiter's decision before you ask for feedback: "No one will talk to you if they think you're going to argue or appeal."
If you don't trust yourself to keep your cool, you may want to skip asking for feedback. If you do ask, email is the best medium. "Telephoning is probably too intrusive," says Lynch. "And whatever feedback you hear, don't be defensive."
Lin cautions that "you'll get canned responses most of the time" due to fears about legal issues, but he recommends phrasing your request for feedback like this: "If you don't mind me asking, do you have any feedback on how I can improve for future interviews?"
He adds, "You want to keep the conversation as professional as possible. Who knows? You could be their backup candidate."
Keep trying.
In most cases, you should actively pursue new openings at the company. The phrase "we'll keep your resume on file" is usually an attempt to soften the rejection, according to Kador, who says you should keep applying for relevant jobs and staying in touch with the recruiters you've met. "If a posting says no calls,' I wouldn't call," he says. "But that doesn't mean you can't write."
Bring the recruiter into your professional network.
If, down the road, you can help the interviewer or recruiter by recommending a candidate, for instance, or forwarding a relevant article, Kador says you should "go for it--make yourself known as a resource."
Lynch, too, recommends keeping in touch with the hiring manager in a "low-key way" and says that, when you do land a position, you should write him or her a note and include your new business card. Then you can send the manager an invitation to connect on LinkedIn so you can easily stay in touch.
"You're hired."
Instead, you got another rejection letter. According to recent U.S. Labor Department data, 5.5 unemployed Americans, on average, are vying for each job opening--so most interviews will end in rejection.
And that can be a crushing blow--but it can also be a career-making moment. When you don't get the job, what should your next steps be?
Don't beat yourself up about it.
John Kador, the author of "301 Best Questions to Ask on Your Interview," second edition (McGraw-Hill), recommends that you try to learn from each rejection--while understanding that it may not be your fault. "Sometimes you didn't do anything wrong," he says. "Someone else was more qualified or more connected. Companies sometimes go through the motions of interviewing applicants when they've already selected a candidate."
While the experience is still fresh in your mind, writing down what you've learned may help you put a positive spin on the experience--and give you something to refer to later, according to Lewis Lin, of SeattleInterviewCoach.com.
Be gracious in defeat.
How you conduct yourself after a rejection letter can determine whether that recruiter will consider you again--or perhaps refer you to another recruiter. Liz Lynch, the author of "Smart Networking" (McGraw-Hill), says, "Send a handwritten card thanking them again for their time, reiterating your interest in the company, and expressing your hope that they'll keep you in mind for future positions. And whatever you do, do not diss them on your blog!"
Ask for feedback.
Kador advises saying that you accept the recruiter's decision before you ask for feedback: "No one will talk to you if they think you're going to argue or appeal."
If you don't trust yourself to keep your cool, you may want to skip asking for feedback. If you do ask, email is the best medium. "Telephoning is probably too intrusive," says Lynch. "And whatever feedback you hear, don't be defensive."
Lin cautions that "you'll get canned responses most of the time" due to fears about legal issues, but he recommends phrasing your request for feedback like this: "If you don't mind me asking, do you have any feedback on how I can improve for future interviews?"
He adds, "You want to keep the conversation as professional as possible. Who knows? You could be their backup candidate."
Keep trying.
In most cases, you should actively pursue new openings at the company. The phrase "we'll keep your resume on file" is usually an attempt to soften the rejection, according to Kador, who says you should keep applying for relevant jobs and staying in touch with the recruiters you've met. "If a posting says no calls,' I wouldn't call," he says. "But that doesn't mean you can't write."
Bring the recruiter into your professional network.
If, down the road, you can help the interviewer or recruiter by recommending a candidate, for instance, or forwarding a relevant article, Kador says you should "go for it--make yourself known as a resource."
Lynch, too, recommends keeping in touch with the hiring manager in a "low-key way" and says that, when you do land a position, you should write him or her a note and include your new business card. Then you can send the manager an invitation to connect on LinkedIn so you can easily stay in touch.
Friday, May 28, 2010
Don’t Dance in the Interview – Answering Tough Questions Directly
The interviewer asks the interviewee a direct question about why they left their previous employer. The interviewee drops eye contact, looks towards the floor, says “Um… I… uh… well…” and the dance begins! Sure, questions on an interview can sometimes be uncomfortable to answer. Maybe you’ve never worked with the technology or skill they are asking about, maybe it hits on a “rough patch” of your career, maybe you don’t even understand the question, or know where to begin. But, tap dancing is for those aspiring to be on Broadway. The rest of us need to leave the tap shoes at home and go to the interview prepared to be direct in our answers, even the uncomfortable ones.
If you respond to the tough questions with evasion, vagueness, and explanations that don’t address what’s asked, then you’re going to leave the interviewer uneasy with your candidacy for the position and they will assume you are hiding something or don’t really have the experience required for the position. If instead, you are direct and forthright in your answers and in the very FIRST sentence following the question give them the information asked for, even if you feel the answer is possibly a negative response, you’ll score points for being honest with them. You then have an opportunity to further explain the situation, turn it into more of a positive light, or make a detraction become an opportunity for growth.
Interviewer: “Why did you leave Alpha Company?”
You: “I was terminated” (DIRECT ANSWER!) “I did not have as fully developed skills in web development as the position seemed to be requiring when I went to work there. I attempted to get my skills to the level needed by putting in extra training time, but their project backlog was so heavy and the manager was impatient with the progress. I believe a better suited position would rely more on my core skills with more training opportunities and mentoring.”
It’s not great being terminated, but if you’re honest about the reasoning and seem to be applying the lessons learned to your current career search, you are more likely to find the right job and impress the company with your ability to be honest.
Interviewer: “Do you have experience creating Web Services?”
You: “No, I have not. I have studied Web Services in the classroom and wrote some sample programs for the class using them, but have not had an opportunity to do so on the job. I do believe that I pick up new technologies quickly, in fact, at my last position I had gone in with no experience in using XML style sheets and I put in extra effort at home to read up and practice them and within a few days was successfully employing them on my project. I believe I can do the same learning Web Services techniques.”
Here we have taken a negative answer – been direct with it, and then turned it towards a positive light and an opportunity by demonstrating how we have overcame similar obstacles before and will do it again.
Interviewer: “State the significance of public, private, protected, default modifiers both singly and in combination and state the effect of package relationships on declared items qualified by these modifiers?”
(You’ve been asked a very difficult question that you don’t fully understand – rather than start dancing, be direct)
You: “I’m not sure that I understand the question, is there any other way to ask it?”
or You: “I have had limited exposure to these different types of modifiers, but I can attempt to answer as much of the question as I can. I believe that public modifiers are used for…” (Let them know you’re going to take your best shot at it, but know you might not be right-on… credit for trying)
or You: “Would you mind asking the first part of the question again and let me answer it and then cover the last part of the question”? (Break it down to make it easier to understand)
or You: “I don’t know the answer to that question. Frequently as a developer I can run up against things I haven’t learned yet and I always make sure to write down the problem and then, when I have a chance, I will go to reference texts, developer forums and other resources to learn the answer. I’ll make sure I know it for the next time – this is one of those situations.”
or You: “I can’t answer that question as I haven’t had experience with it. At the environments I’ve been working on, we have been employing a different technique instead by…. ” (and explain how you did things as an alternative)
There’s a lot of other ways to handle the situation of not having an answer, the point is, we’re direct in our answer and we try to turn it as positive as we can. If you don’t understand the question at all or have the experience to answer it, the interviewer will know it, so trying to bluff your way through is of no use. Sometimes you think you know the answer, but it’s a big mistake to go into a full explanation and find out you were heading the wrong direction and didn’t answer the correct questions.
Interviewer: Asks you a question you think you understand, but are not sure.
You: “By ________, do you mean _________” or “I believe you are looking for _______, is that correct?”
Interviewers will sometimes ask questions that are very broad and don’t provide much insight as to where you should start or what level of detail they are looking for.
Interviewer: “Tell me about yourself” or “Tell me about projects you’ve worked on”
You: “Sure, where would you like me to start?”
You could provide a brief overview and then ask what they’d like to know more about.
You: “I went to College at _____ and majored in ______. My first position was ____ at _____ and I worked with _____ and then I moved to _____” (… and so on through your career highlights) “Is there any of this that you’d like me to provide more detail on?” or “Are you interested in more specifics about anything in particular?”
We aren’t sure of where they want us to go, but rather than dancing all around, we give an overview and ask them to help us narrow it down. Again we are employing the technique of asking if we’re headed in the right direction before we go too deeply.
Good luck on your interviews and BE DIRECT! Feel free to add the toughest questions you’ve faced on interviews as comments to this blog and I’d be glad to respond as to how they might best be handled.
Thanks for David .. For original Posting.
If you respond to the tough questions with evasion, vagueness, and explanations that don’t address what’s asked, then you’re going to leave the interviewer uneasy with your candidacy for the position and they will assume you are hiding something or don’t really have the experience required for the position. If instead, you are direct and forthright in your answers and in the very FIRST sentence following the question give them the information asked for, even if you feel the answer is possibly a negative response, you’ll score points for being honest with them. You then have an opportunity to further explain the situation, turn it into more of a positive light, or make a detraction become an opportunity for growth.
Interviewer: “Why did you leave Alpha Company?”
You: “I was terminated” (DIRECT ANSWER!) “I did not have as fully developed skills in web development as the position seemed to be requiring when I went to work there. I attempted to get my skills to the level needed by putting in extra training time, but their project backlog was so heavy and the manager was impatient with the progress. I believe a better suited position would rely more on my core skills with more training opportunities and mentoring.”
It’s not great being terminated, but if you’re honest about the reasoning and seem to be applying the lessons learned to your current career search, you are more likely to find the right job and impress the company with your ability to be honest.
Interviewer: “Do you have experience creating Web Services?”
You: “No, I have not. I have studied Web Services in the classroom and wrote some sample programs for the class using them, but have not had an opportunity to do so on the job. I do believe that I pick up new technologies quickly, in fact, at my last position I had gone in with no experience in using XML style sheets and I put in extra effort at home to read up and practice them and within a few days was successfully employing them on my project. I believe I can do the same learning Web Services techniques.”
Here we have taken a negative answer – been direct with it, and then turned it towards a positive light and an opportunity by demonstrating how we have overcame similar obstacles before and will do it again.
Interviewer: “State the significance of public, private, protected, default modifiers both singly and in combination and state the effect of package relationships on declared items qualified by these modifiers?”
(You’ve been asked a very difficult question that you don’t fully understand – rather than start dancing, be direct)
You: “I’m not sure that I understand the question, is there any other way to ask it?”
or You: “I have had limited exposure to these different types of modifiers, but I can attempt to answer as much of the question as I can. I believe that public modifiers are used for…” (Let them know you’re going to take your best shot at it, but know you might not be right-on… credit for trying)
or You: “Would you mind asking the first part of the question again and let me answer it and then cover the last part of the question”? (Break it down to make it easier to understand)
or You: “I don’t know the answer to that question. Frequently as a developer I can run up against things I haven’t learned yet and I always make sure to write down the problem and then, when I have a chance, I will go to reference texts, developer forums and other resources to learn the answer. I’ll make sure I know it for the next time – this is one of those situations.”
or You: “I can’t answer that question as I haven’t had experience with it. At the environments I’ve been working on, we have been employing a different technique instead by…. ” (and explain how you did things as an alternative)
There’s a lot of other ways to handle the situation of not having an answer, the point is, we’re direct in our answer and we try to turn it as positive as we can. If you don’t understand the question at all or have the experience to answer it, the interviewer will know it, so trying to bluff your way through is of no use. Sometimes you think you know the answer, but it’s a big mistake to go into a full explanation and find out you were heading the wrong direction and didn’t answer the correct questions.
Interviewer: Asks you a question you think you understand, but are not sure.
You: “By ________, do you mean _________” or “I believe you are looking for _______, is that correct?”
Interviewers will sometimes ask questions that are very broad and don’t provide much insight as to where you should start or what level of detail they are looking for.
Interviewer: “Tell me about yourself” or “Tell me about projects you’ve worked on”
You: “Sure, where would you like me to start?”
You could provide a brief overview and then ask what they’d like to know more about.
You: “I went to College at _____ and majored in ______. My first position was ____ at _____ and I worked with _____ and then I moved to _____” (… and so on through your career highlights) “Is there any of this that you’d like me to provide more detail on?” or “Are you interested in more specifics about anything in particular?”
We aren’t sure of where they want us to go, but rather than dancing all around, we give an overview and ask them to help us narrow it down. Again we are employing the technique of asking if we’re headed in the right direction before we go too deeply.
Good luck on your interviews and BE DIRECT! Feel free to add the toughest questions you’ve faced on interviews as comments to this blog and I’d be glad to respond as to how they might best be handled.
Thanks for David .. For original Posting.
2nd & 3rd Interviews – Nail It! Don’t Blow It!
You have been on a 1st Interview, maybe even a 2nd interview. The hiring manager has told you that they are very interested in hiring you – you’re their first choice. But, before they can extend an offer, they just need you to meet with the top boss – a “blessing interview”. You’re assured that you’re already going to be hired and that it’s just a routine introduction that nobody has any problems with. The decision to hire you has already been made.
Don’t believe it! Nobody is brought back in for another interview if they have the job 100%. And no one is put into the interview process if they don’t have some influence on the final decision to hire. Rather than “blessing interview” it should be called a “veto interview”. Nobody’s getting hired that doesn’t really connect with the boss on that last meeting.
I have witnessed quite a few finalists lose the job because they didn’t prepare and take the last interview seriously enough. No matter how much you may have impressed 10 other people in previous trips to the company, the last meeting with the anyone at the company may well be the most important of all the meetings.
The best rule of thumb is, TREAT ALL 2ND INTERIVEWS OR SUBSEQUENT JUST LIKE A FIRST INTERVIEW. No matter what you are told by the hiring manager, a recruiter, or your friend at the company, don’t let the fact that “you’ve practically hired”, go to your head and have you let your guard down. Assume there are always at least three equal finalists or that you’re maybe even the underdog. Prepare for that last meeting, further research the company, prepare interview questions, review your strengths, reasons for change and goals, be ready for whatever they might throw at you. (see previous blogs for ideas on these subjects).
It’s also not the time to let your appearance slide. Dress sharp, shine your shoes, get your hair trimmed or styled if it needs it. If anything, you need to look more “together” than you did on previous meetings.
Be ready to tell that individual why you want the job, why you’re excited about the company, how you feel like you can contribute to the organization, and how the opportunity fits into your career progression.
Also, be sure not to leave the meeting without expressing your appreciation for them taking the time ot meet with you and that you sincerely hope that you’ll be able to together. And when you get home, get a thank-you letter or thank-you card in the mail (again see previous blogs on thank-you letters). Maybe you’re expecting an offer before the thank-you letter would get there. Well it’s certainly no big deal if they get the thanks and you’re already going to work there. And it could absolutely be the slight nudge needed to get you the offer if the final decision maker is at all on the fence about the offer.
Please share your ideas or experiences on “blessing interviews” as comments to this blog.
Don’t believe it! Nobody is brought back in for another interview if they have the job 100%. And no one is put into the interview process if they don’t have some influence on the final decision to hire. Rather than “blessing interview” it should be called a “veto interview”. Nobody’s getting hired that doesn’t really connect with the boss on that last meeting.
I have witnessed quite a few finalists lose the job because they didn’t prepare and take the last interview seriously enough. No matter how much you may have impressed 10 other people in previous trips to the company, the last meeting with the anyone at the company may well be the most important of all the meetings.
The best rule of thumb is, TREAT ALL 2ND INTERIVEWS OR SUBSEQUENT JUST LIKE A FIRST INTERVIEW. No matter what you are told by the hiring manager, a recruiter, or your friend at the company, don’t let the fact that “you’ve practically hired”, go to your head and have you let your guard down. Assume there are always at least three equal finalists or that you’re maybe even the underdog. Prepare for that last meeting, further research the company, prepare interview questions, review your strengths, reasons for change and goals, be ready for whatever they might throw at you. (see previous blogs for ideas on these subjects).
It’s also not the time to let your appearance slide. Dress sharp, shine your shoes, get your hair trimmed or styled if it needs it. If anything, you need to look more “together” than you did on previous meetings.
Be ready to tell that individual why you want the job, why you’re excited about the company, how you feel like you can contribute to the organization, and how the opportunity fits into your career progression.
Also, be sure not to leave the meeting without expressing your appreciation for them taking the time ot meet with you and that you sincerely hope that you’ll be able to together. And when you get home, get a thank-you letter or thank-you card in the mail (again see previous blogs on thank-you letters). Maybe you’re expecting an offer before the thank-you letter would get there. Well it’s certainly no big deal if they get the thanks and you’re already going to work there. And it could absolutely be the slight nudge needed to get you the offer if the final decision maker is at all on the fence about the offer.
Please share your ideas or experiences on “blessing interviews” as comments to this blog.
Saturday, May 22, 2010
Tuesday, May 18, 2010
Subscribe to:
Posts (Atom)
