The Reason You’re Not Getting the Job You Applied For
I recently posted a job description and asked my Twitter followers to apply. As I was going through their applications, I thought it might be a good idea to write a short blog post on helping you get the job you’re applying for.
You may be qualified and have a good attitude, but if you’re not a good communicator, sorry my friend, you’re not going to get the job.
What do I mean by being a good communicator?
If the interviewer asks you: “What color is the sky?” Say: “The sky is blue”. Or even better, ask: “At what time of the day?” This shows that you pay attention to detail and can think like a problem-solver.
Don’t say: “This morning I woke up at 7, I looked up to see what color the sky is, but then I remembered I didn’t take my clothes out of the washing machine last night. It all happened because my friend called me and needed some advice about his girlfriend.”
Of course, I’m exaggerating. But you get the point! If not, here’s a real example. The last question I put in the application form was: “Why should I hire you?”
This is where I want them to sell themselves, short and sweet, to the point, without any waffling.
One candidate said:
What is wrong with this response? For starters, it’s way too long. No one has that much time to read this, or hear it in an interview.
The second issue is that he/she is telling me the problem with online courses: the fact that they get outdated quickly. Well, I already know that. That’s exactly the reason I opened up this job position. So I can get someone to help me update my courses. I don’t need to be told what I already know. The moment I hit that point, I had to move on to the next candidate. So I thought I should pause for a second and write this blog post, since I’ve seen this pattern over and over. I think this could be one of the reasons you’re not getting the job you wanted
Now, here’s a good response to “Why should I hire you?”
I’m a Front-end developer with over 7 years of experience. I’ve been working with Angular since Angular JS to Angular 8.x
See the difference? This candidate is telling me directly about his/her level of experience, and what exactly he/she knows well. To the point, in one line. No waffling. No storytelling. No repeating the obvious.