Here's How To Answer The WORST Job Interview Question
Along with ‘what are your weaknesses?’, it’s one of the most dreaded questions to be asked when going for a job.
Mainly because it’s so overwhelming.
I mean, where do you start with it, high school? How do you know if what you’re saying is actually answering the question?
Recently, managing partner at executive search group The HTW Group (formerly Hire To Win), Skip Freeman, wrote a post on LinkedIn, which gave an insight into where to put the goal posts so you don’t end up telling the interviewer your whole god damn life story.
Freeman breaks it down to a three-part response.
Here's his technique:
1 - Start with a condensed version of your career history. Keep it as concise as possible.
2 - Next, a brief summary of a specific achievement to capture the interviewer's interest. "It must be an accomplishment that can easily be explained and/or illustrated," Freeman says.
3 - Conclude with a few definitive sentences about what you hope to accomplish next in your career — making sure it's relevant to the position you're interviewing for.
Here's an example from Freeman of a good response:
"I am a five-year veteran of LAN/WAN administration and systems engineering, with substantial experience using a variety of contemporary business software systems.
"Recently, as a long-term contract employee at a local regional bank, I learned that the bank was about to install a particular software system and was planning to use an outside firm for the project. I let them know that I had done a similar installation at my last assignment, outlined how we could get the job done with in-house staff, and successfully completed the installation for $55,000 to $65,000 less than it would have cost with outside consultants.
"For the next step in my career, I would like to move away from contract work and find myself as a direct employee of a large firm where I can join a substantial IT team and be involved with a group that focuses on email and network security applications, while having access to the knowledge base that would come with a large, diverse IT group."
Not gonna lie, we’re pretty glad we’re not going for whatever position that ^^ was.