Lately, I’ve had the pleasure of taking part in an hiring process for a position that my team had open. I reviewed a number of CVs/resumes and interviewed a number of people. I thought that I would share that experience with you and give you some advice about the CV and interviewing process.
I wrote about the CV in my last article, “Looking for a Job”, what should go into a CV and how to frame it so that it fits what the employer is looking for. However, putting a bunch of keywords on your CV that you have barely touched will probably backfire on you. For an entry-level job, hiring companies generally understand that most the skills listed are educational and not necessarily practical. However, for anything after the first job, you will be expected to back up any skills that you put on your CV.
In order to best prepare for an interview, it is worthwhile to understand the interview from the employer’s perspective. There is a popular term in the investing world, “Past performance does not indicate future results.” This concept is not true in the interviewing and hiring process. Human nature is to continue to act in similar ways that you’ve acted in the past. Based on this the questions that are asked in an interview are generally all based on examples of what you’ve done in the past.
Everything on your CV is fair game to ask about, so you should have stories prepared for every skill and experience that is listed. If you wrote a skill on your CV, you can expect questions such as:
- What did you use that for?
- Can you describe the workflow that you used?
During the discussion, other questions will pop up, such as:
- When you did X and Y, which method did you use?
- Can you write the commands that are needed for this?
- Did you have any problems, and how did you solve them?
- Can you draw out the architecture of the components used and how they work?
While a lot of work is collaborative and you only played a part in the big picture, the interviewer wants to hear about what you personally did as part of the process. The fact that your team accomplished a major project, and you were only involved in a small aspect of that, focus on the role that you played and how that facilitated the success of the entire project. Collaborative experience is also very important. Make sure you talk about how many people were on the team, and what your specific role was.
- How did you interact with the other people?
- Were you able to rely on them and they on you?
- Can you give an example of when you needed to trust someone to do their job?
- Did you ever cover for someone who was unable to complete his work on time?
A major question that I like to ask is: "Tell me about time that you screwed up badly." It happens to everyone, whether you erased the production database, let a virus into the company, recommended purchasing software that did not meet the requirements or did the accounting math wrong and caused a scandal at the company board meeting.
Why is this a good question? First of all, it tells me that you are willing to talk about your mistakes. It also lets me know how you fixed it afterwards. Were you transparent? Did you try to fix the mess without reporting first to your manager? Did you ask for help in fixing the problem?
Your behavior during a crisis speaks a lot about your personality.
Another popular question is “tell me about a weakness that you have”. Don’t try to outsmart the interviewer by trying to turn a strength into a weakness. “I am a perfectionist and make sure that my work is 100%, though it might take me a little too much time.” “I’m too organized for my own good.” Interviewers aren't fooled and don't want to hear that garbage. What they want to hear, and what will make you stand out, is an actual weakness. Think back through times that you’ve messed up, and use a real example of something you did. You can include what you are doing to mitigate that weakness as well. But being real and honest will give you a huge advantage during the decision making time.
As examples:
- When I've sent emails in the past, I often used sarcasm, which was misunderstood by the receivers. After a few negative responses, I asked a colleague to review important emails before I send them. I do the same for him, so we both benefit
- I've noticed that I often argue a point even after a decision has been made. I've been working on taking a step back and accepting the fact that my argument was not accepted.
Comments
Post a Comment