Ice Cream Jonsey wrote:I have a few questions about what I've been doing wrong. I am searching again for the first time in six or seven years. I've been on one interview so far and I am approaching day 90 of my search.
I'll speak from experience because, well, I can...
It all starts with the resume. I've recently hired an IT Support Engineer (I went through 93 resumes) and a mid level Java developer (about 20 resumes). I am currently interviewing Quality Assurance folks (about 30 resumes) -- got an interview tomorrow, as a matter of fact.
It can literally take me 20 seconds to decide if I want to read the resume or not. Think about that. 20 seconds before it either ends up in the "no thanks" pile or the "keep for further review". Of the 93 IT resumes, only 9 made it into the "keep" pile.
What I might look for right off the bat:
A concise, well written and no BS Objective.
Not cluttered. I don't have time to read about the great job you did four years ago on some project that is irrelevant.
Too many jobs in a 3-5 year period. I don't want to be your next career step.
Too many "I" references. "We" or "part of a team" is preferred.
Your GPA. You're probably lying. I know I did.
Questions I might ask during a phone screening:
Why are you leaving your job? Don't tell me your boss doesn't understand you. I want to hear that you want to further your career and want stability. If you're unemployed, what happened? Be careful here, one can read a lot into 'laid off', especially if the company is still doing well or if it was limited to a few people. Lie if you have to.
What do you want to do long term? Don't tell me you want my job -- you can have it today. I want to hear all the cookie cutter answers (advancing career, stability, part of a successful organization, etc...).
Why should you be brought in for an interview? Don't stumble -- you'll lose me. I want to hear your strengths, how you've learned from past experience and that you'll be an asset to the company.
What's your salary expectation? A trick question. Don't give an answer. If I'm thinking 45K, you can answer one of three ways. Low; that's good for me, not good for you. High; you'll be considered a risk in that if you settle for the 'lower' offer, you may not ultimately be happy. Right on; that rarely happens. Best answer is that you'd hope to be paid fair market value for your skills and in line with the existing staff. As a manager, I don't want to hear that answer, but it's a good one.
As for the interview itself, maybe I can get to that in another post...
HTH
-- Mike
[quote="Ice Cream Jonsey"]I have a few questions about what I've been doing wrong. I am searching again for the first time in six or seven years. I've been on one interview so far and I am approaching day 90 of my search.[/quote]
I'll speak from experience because, well, I can...
It all starts with the resume. I've recently hired an IT Support Engineer (I went through 93 resumes) and a mid level Java developer (about 20 resumes). I am currently interviewing Quality Assurance folks (about 30 resumes) -- got an interview tomorrow, as a matter of fact.
It can literally take me 20 seconds to decide if I want to read the resume or not. Think about that. 20 seconds before it either ends up in the "no thanks" pile or the "keep for further review". Of the 93 IT resumes, only 9 made it into the "keep" pile.
What I might look for right off the bat:
A concise, well written and no BS Objective.
Not cluttered. I don't have time to read about the great job you did four years ago on some project that is irrelevant.
Too many jobs in a 3-5 year period. I don't want to be your next career step.
Too many "I" references. "We" or "part of a team" is preferred.
Your GPA. You're probably lying. I know I did.
Questions I might ask during a phone screening:
Why are you leaving your job? Don't tell me your boss doesn't understand you. I want to hear that you want to further your career and want stability. If you're unemployed, what happened? Be careful here, one can read a lot into 'laid off', especially if the company is still doing well or if it was limited to a few people. Lie if you have to.
What do you want to do long term? Don't tell me you want my job -- you can have it today. I want to hear all the cookie cutter answers (advancing career, stability, part of a successful organization, etc...).
Why should you be brought in for an interview? Don't stumble -- you'll lose me. I want to hear your strengths, how you've learned from past experience and that you'll be an asset to the company.
What's your salary expectation? A trick question. Don't give an answer. If I'm thinking 45K, you can answer one of three ways. Low; that's good for me, not good for you. High; you'll be considered a risk in that if you settle for the 'lower' offer, you may not ultimately be happy. Right on; that rarely happens. Best answer is that you'd hope to be paid fair market value for your skills and in line with the existing staff. As a manager, I don't want to hear that answer, but it's a good one.
As for the interview itself, maybe I can get to that in another post...
HTH
-- Mike