Most developers have learned by now that when we approach a system-based problem programmatically, we are looking for identifiable patterns that lead us to simplified conclusions. This is something we take very seriously at Outco, but not just when we are met with a code-based problem. When software engineers come to know this pattern-based approach taught at Outco, that same mindset can be used to help answer behavioral questions as well.
For example: if the interviewer is trying to figure how self-aware you are about your weaknesses, they might ask -
1) What are your biggest weaknesses?
Or
2) Tell me about a time you failed?
Or
3) What feedback have your managers given on improvement?
Or
4) What are your T3B3? (Top 3 and bottom 3 qualities)
Or
5) I talked to your last 3 managers. They told me what your weaknesses are, and I want to see if you can tell me what they said.
These five unique questions are all aimed at acquiring the same information about you: How well do you know yourself?
Instead of drilling a mountain of questions and preparing responses for each of them, try to figure out what your interviewer is actually trying to learn about you with each behavioral question. By understanding the motive behind each question, you can easily nail your response by knowing how to represent yourself in the best context.
The majority of the behavioral questions can be divided into the following three patterns:
Icebreakers
Example-- Tell me about yourself.
Trying to start a conversation and find ammunition for follow-up questions.
a) Keep your response around a one minute pitch. This is never the time to ramble.
b) Sell yourself by focusing on specific projects and accomplishments. If they were to follow-up, it would allow you to give evidence of your work ethic, organizational skills, and curiosity.
c) Start with the most recent gig, and go chronologically backwards. It’s always best to end with what you’re looking for in your next role.
Situational
Use the S.T.A.R method to identify and respond to questions that fit this pattern. “S.T.A.R” is an acronym that can help you remember exactly how to answer a situation based behavioral question. Just spell it out:
Example -- You're working on a program where some aspects of the features designed were completed with errors. What do you do?
a) Situation: Give context and background info.
b) Task: What you had to do (Not what your team did - but what you did).
c) Action: What are the details to your role and how you completed the task? This will be the longest part of your answer.
d) Result: What you learned and what you would do differently. This answer should be positive and quantifiable.
At Outco, we’ve learned the best way to get better at mastering these techniques is through practice. We have professional coaches who give you feedback in real-time as you practice through mock interviews. If you’re not ready to try Outco’s program, try to find a friend or colleague whom you think might be able to give you good feedback as you work through this type of pattern.
Philosophy
Example — “How would you approach a disorganized engineer on your team given their exceptional performance?”
This one should be familiar for folks looking at leadership positions, and typically takes the frame of “how would you approach XYZ…” Your interviewer wants to be sure that you will be a great fit and share common values held by the team. Its is always best to be as honest as possible when answering these types of questions. A good fit works both ways!
Identifying patterns and executing effectively is one of the most important tenets of the Outco strategy. By knowing what to expect and how to respond, you will find that you are better able to accurately represent your best qualities and make serious inroads to the role you’ve been searching for.
Attend our Info Session to be better prepared for your next technical interview:
https://www.outco.io/info-session-signup