Why should you avoid improvising stories in your behavioral interviews?

Why should you avoid improvising stories in your behavioral interviews?

Prepare your stories well enough so that when you are asked a question, the only thing you need to think about is ensuring you frame it in a way that directly answers the question.

I’ve seen many people improvise this part of the interview, and that is equivalent to not practicing a single algorithm before a coding interview.

Don’t be caught off guard!

Prepare a variety of stories, perhaps 3 to 5, that you know inside and out.

Remember:

• Team: who you worked with, what their roles were, and most importantly, what yours was.
• Impact: what were the overall goals of the team and how did you perform in relation to those goals?
• Decisions: what were some of the crossroads? Both technical (the frameworks you used) and product-related (what the user flow was). Understand why each decision was made.
• Learnings: what would you do differently now that you know what you know?

Answer the above questions for 3 to 5 projects, and you’ll be 80% of the way to an exceptional behavioral interview.

🚀 Follow me for more technical interview tips like this.