Behavioral stories and values-based questions

Why it matters

Behavioral questions treat your past behavior, described concretely, as evidence about how you will work. Some companies describe this openly; Amazon's SDE preparation pages, for example, say a significant part of the conversation focuses on how candidates have demonstrated its Leadership Principles. Weak answers are vague ("we usually...") or hypothetical ("I would..."); strong answers are specific, first-person and honest about tradeoffs. Preparation matters because recalling details under pressure is hard, and without a bank candidates reach for their most recent project for every question. Your sources include your coursework and any team projects from your studies, building Agaria, and any internship, research or teaching roles you have held; only you know which of these contain real conflicts, failures and decisions, and every story must use your own facts.

Core ideas

Build a bank, not answers. List every substantial experience, then extract moments: a decision you made, a problem you owned end to end, a disagreement, a mistake, a goal that was unclear, a time you changed someone's mind, a time you learned something quickly. Aim for eight to twelve stories and tag each with the themes it can serve; good stories usually answer two or three. Keep each as bullet notes, not a script.

Structure. Situation: two or three sentences, enough for a stranger to follow. Task and role: what you were responsible for and what made it hard. Actions: what you did and why, including options you rejected; this should take well over half the answer. Result: what happened, with evidence you can defend, such as a measured change, a shipped feature, feedback received, or an honest "it did not work". Reflection: what you learned, what you would do differently and what you changed afterwards. Amazon's preparation pages recommend the STAR structure with data where applicable, and MIT's career office publishes a STAR worksheet that is useful for drafting.

Prompts to mine your bank.

• Ownership: a problem nobody was assigned that you took on; something you kept maintaining after it shipped.
• Conflict: a technical disagreement with a teammate, collaborator or advisor; how it was resolved and what you conceded.
• Failure: a missed deadline, a bug you shipped, a design you abandoned.
• Ambiguity: a vague goal you turned into a plan; a decision made with incomplete information.
• Influence: convincing people who did not report to you, with evidence, a prototype or a written proposal.
• Learning: a technology or domain you had to learn quickly, and how you did it.
• Users: feedback that changed what you built.

Values-based questions. Some companies publish the values they assess. Amazon's Leadership Principles page lists each principle with a short description. For every company on your list, read its official values or preparation pages, note which of your stories honestly illustrate each value, and leave a value uncovered rather than stretching a story to fit it.

Follow-ups. Expect "what exactly did you do?", "what else did you consider?", "how did you measure that?", "what would you do differently?" and "what did the other person think?". Prepare one level of detail beyond what you say.

Common misconceptions

• "Say 'we' to sound like a team player." Interviewers need your contribution; say "I" for your actions and credit others specifically.
• "Failure stories should end in a hidden success." A disguised strength reads as evasive; choose a real failure and show the changed behavior.
• "More context makes the story clearer." Long setups crowd out the actions and reasoning, and those are what get evaluated.
• "Numbers are mandatory." Use metrics when you have them, but never invent or round up figures; a concrete, checkable outcome beats a precise-sounding guess.
• "Memorize scripts." Scripts break under follow-up questions; rehearse from bullet notes so the telling stays natural.

How to approach it

Spend one session listing experiences and another drafting eight stories as bullets in the STAR-plus-reflection shape, marking every fact you still need to verify. Rehearse aloud with a timer, record yourself, and cut anything that is not context, your action, a result or a lesson. Practice with a peer who asks follow-ups. For each target company, build a table from its published values to your stories. At graduate level, specific coursework and project stories are fine; at mid and senior level, interviewers expect larger scope, cross-team influence and long-term ownership.