You\u2019re preparing for an interview. You\u2019ve poured over the job description identifying all the ways you\u2019re PERFECT for this job. You\u2019ve researched the company, the hiring manager and others you\u2019ll be interviewing with. All good stuff. But what have you done to prepare for the interview itself?<\/p>\n
Many interviewers use a technique known as behavioral interviewing. To learn what that is, contrast these two types of questions:<\/p>\n
1. How would you approach an unexpected project that has a tight deadline?
\n2. Tell me about a time you got an unexpected project with a tight deadline. What did you do?<\/p>\n
Both questions ask about your ability to work fast under pressure. The first asks what you would <\/strong>do and the second asks what you did <\/strong>do. Anytime you\u2019re asked to describe what you did in a specific past situation (#2), you\u2019ve gotten a behavioral interview question.<\/p>\n Why are behavioral questions used so much? When given general or hypothetical questions (like #1), most interviewees can figure out what the interviewer is looking for. And voil\u00e0 \u2013 they say what the interviewer wants to hear whether it accurately describes them or not. By focusing on real situations from the past, interviewers know that the abilities we\u2019ve used before will be used again. Behavioral questions are a better way to determine our skills and job fit.<\/p>\n So, what\u2019s the best way to respond to behavioral questions? Use the S.T.A.R. technique!<\/p>\n There are four pieces to a S.T.A.R. response. For each, be succinct and specific.<\/p>\n S – Situation<\/strong>: Briefly describe the background or context. What issue, problem or opportunity did you face? Example Question<\/strong>: Tell me about a time you got an unexpected project with a tight deadline. What did you do?<\/p>\n Example S.T.A.R. Answer<\/strong>: Two months ago, my team was preparing for a client presentation which was scheduled for the next day. The person who was developing it had an accident and couldn\u2019t finish, so I was asked to pull it together. I hadn\u2019t been involved up to that point so the first thing I did was to familiarize myself with the client. I talked to our team, researched them online, and then dove in. I solicited help to gather the information I needed, developed an outline and ran it by our client lead. He made a few tweaks, but less than I expected, and I stayed very late that night to make sure the information was accurate, clear, and that it looked great. And we won the business! Although I prefer to plan my work, I can work under tight deadlines when needed.<\/p>\n To use the S.T.A.R. technique effectively, have 3-5 good stories about your past work handy and ready to discuss. Pick ones that demonstrate your best skills and abilities. In the example above, this story shows initiative, collaboration, perseverance, drive, and a focus on quality results. Think beyond your technical skills when you develop your stories. The interviewer is looking for your fit with the culture as much as your ability to do the job. Prepare to describe your stories using the steps in S.T.A.R. Chances are you\u2019ll be asked a couple of questions where one or more of these stories can be used.<\/p>\n Don\u2019t shy away from telling interviewers about mistakes you\u2019ve made in the past. In fact, sometimes they will ask you to describe a situation where things didn\u2019t go well. When this happens be prepared to describe what you learned from the situation and what you would do (or have done) differently as a result of this learning. Honestly describing mistakes can demonstrate accountability, integrity, and your ability to grow.<\/p>\n It\u2019s ok to use stories from things you\u2019ve accomplished outside of your work (e.g. volunteer activities, clubs, athletics, etc.), provided you can ie the skills or lessons learned back to how it would apply in a work situation. This is especially true if your career is just starting out.<\/p>\n Good luck in your interview!<\/p>\nS.T.A.R.<\/h2>\n
\nT – Task<\/strong>: Describe the specific task or activity you took on to address the situation. What was your job in the situation?
\nA – Action<\/strong>: Describe how you went about completing the task (your action, not the action taken by your team). What steps did you take to get it done?
\nR – Result<\/strong>: Describe the outcome. What did you accomplish? What were the results, including the impact on the company, your team, your client, etc.?<\/p>\nStories<\/h2>\n
Mistakes<\/h2>\n
Non-Work Situations<\/h2>\n
\n