Behavioral Interview Questions: 20 Prompts and a Story-Bank Plan
Prepare real examples for behavioral interview questions. Use a story bank, check your contribution and practice follow-ups without memorizing invented answers.
On this page
Behavioral interview questions ask you to describe relevant past experience. A useful answer helps the listener understand the situation, your responsibility, the actions you took and what happened. You do not need a dramatic rescue story or a perfect result.
The 20 prompts below are a practice set, not a measured list covering almost every interview. The story-bank exercise helps you find reusable evidence without assuming four stories can answer a fixed percentage of questions.
Keep the facts stable as you practice. A different emphasis can make an example relevant to another question; a different version of what happened cannot.
20 questions to use for practice
Read the employer’s interview information and the job description alongside this list. Choose prompts relevant to the work and include any other topics the employer identifies. The numbering is only for reference in the planning table below.
- Describe a time you worked through a difficult team situation.
- Tell me about a disagreement with a colleague.
- Describe a time you disagreed with a manager’s proposed approach.
- Tell me about a project that did not meet its goal.
- Describe a mistake you made and your response.
- Tell me about feedback that changed your approach.
- Describe a project or activity you helped lead.
- Give an example of influencing a decision without formal authority.
- Tell me about a time you took initiative.
- Describe a time you did useful work beyond your initial assignment.
- Tell me about working toward a tight deadline.
- Describe how you handled competing priorities.
- Give an example of making a decision under pressure.
- Tell me about adapting to a significant change.
- Describe a decision you made with incomplete information.
- Walk me through a complex problem you helped solve.
- Tell me about learning something for a new task.
- Describe a time you tried to persuade someone.
- Tell me about a goal and how you worked toward it.
- Describe an accomplishment that matters to you.
Small wording differences can change what the question asks. A question about receiving feedback is not the same as a question about making a mistake, even when one event could support both. Listen for the requested action and answer that part of the experience.
For a hypothetical prompt such as “What would you do if two deadlines conflicted?”, explain your proposed approach. Do not invent a past incident to make it fit this list.
Understand what a past example adds
An example gives the interviewer details to explore: what you noticed, what options you considered and what you personally did. It is more informative than only saying that you are adaptable or collaborative.
OPM’s structured-interview guidance describes predetermined questions and common rating standards for job-related competencies, including questions about past or hypothetical situations. A behavioral question can be part of that process, but not every interview follows the same rubric.
Make individual and shared contributions clear. Use “I” and “we” where each is accurate. Neither a confident delivery nor a particular pronoun count proves the quality or truth of an answer.
Use STAR to organize, not to script
Situation, Task, Action and Result is a useful outline for a past example. Use it to check for missing information rather than imposing fixed timings on every answer.
- Situation: the context needed to understand the example.
- Task: your responsibility and any relevant limits.
- Action: the steps or decisions you took, including collaboration.
- Result: the observed outcome, whether successful, mixed, unsuccessful or still pending.
If a number is available, check its source and meaning. A completed handover, an agreed decision or a revised procedure can also be a concrete result. “Fastest ever” still needs evidence, even without a percentage.
For a lesson, describe something you actually changed in your practice. Do not turn a proposed safeguard into proof that an issue never recurred. The STAR method guide walks through a complete fictional example.
Build a story bank with enough range
Start with a few experiences you remember well. Add more if the role calls for evidence your first choices do not cover. There is no required story count or guarantee that one event answers several questions.
The table suggests possible connections. Test each connection against the actual facts: a project where you followed a plan may show delivery, but not necessarily leadership or initiative.
| Possible story | What it might show | Prompts to check for relevance |
|---|---|---|
| A project with a clear personal contribution | Planning, coordination or problem solving | 7, 9, 16, 19 |
| A disagreement about the work | Listening, reasoning and communication | 1, 2, 8, 18 |
| A mistake or difficult feedback | Responsibility and learning | 4, 5, 6 |
| A decision with constraints | Prioritization and judgment | 11, 12, 13, 15 |
Story option 1: a project you contributed to
Choose a project with a clear role for you. Record the goal, the decisions you could make, the people involved and the outcome. You do not need to have owned the whole project or achieved a numerical improvement.
For a leadership prompt, explain how you coordinated or supported people. For a problem-solving prompt, explain the investigation. For a goal prompt, describe the plan and progress. If the event lacks the requested element, use a different example instead of reshaping it into something it was not.
Story option 2: a disagreement about the work
Describe the issue in terms the listener can understand without assigning motives to the other person. What did each side propose? What information did you seek? What did you say or do, and what was decided?
The outcome does not have to be that you persuaded everyone. Reaching a workable decision, recognizing that you were wrong or documenting an unresolved issue can all be relevant. Give necessary context without disclosing confidential conversations or pretending to recall exact words you do not remember.
Story option 3: a mistake or feedback
Choose a real event that answers the question and that you can appropriately discuss. Be clear about your contribution to the problem without accepting blame for things outside your control.
For feedback, explain what you understood, how you checked any ambiguity and what you changed. A feedback example need not involve a major failure. Keep the result accurate even if the improvement was gradual or incomplete.
Story option 4: a decision under constraints
Look for a situation where you had to balance priorities, time, scope or resources. Explain what information you had, what you still needed and who had authority to approve a trade-off.
A useful account might describe how you proposed postponing a lower-priority task after confirming the impact with a manager. It does not need to celebrate working excessive hours or bypassing a safety check to meet a deadline. Distinguish making a decision from recommending one.
Find gaps before the interview
Review the remaining prompts, including adapting to change, learning and receiving feedback. If your current examples do not answer them, look for another relevant event. Do not force every question into the same four projects.
Keep a short note for each story: context, your role, key action, result and possible follow-up. You can prepare from study, volunteering or other relevant settings when you identify the setting honestly.
Answer a failure question honestly
State what went wrong, what part you were responsible for and what happened next. Relevant constraints belong in the explanation when they help the listener understand the decision; they are not automatically excuses.
Fictional illustration: “I did not confirm a dependency before estimating a delivery date. When the dependency was still unresolved, I raised the risk with the project lead and helped prepare a revised plan. We delivered later than originally planned. I now record dependency owners before submitting an estimate.”
This example acknowledges a mistake without inventing a perfect recovery. Choose your own event and answer the question truthfully. Do not use the exercise to conceal information you are required to disclose, and do not share confidential details to make a story more dramatic.
Discuss a disagreement with a manager
Explain the work issue, the information available to you and how you raised the concern. A neutral account can include facts that reflect poorly on a decision without turning into personal speculation. You do not have to portray yourself or the manager as entirely right or wrong.
For an ordinary disagreement about priorities, describe the decision and how you handled the next steps. If the matter involved safety, harassment, discrimination or another serious concern, following an appropriate reporting or escalation process may be the relevant action. “Commit to whatever was decided” is not sound blanket advice.
You can choose a different example if one requires disclosing private information you cannot appropriately discuss. Keep the account truthful and relevant to what the interviewer asked.
Show leadership without inventing management experience
If you have never managed direct reports, say so when that distinction matters. You may still have useful examples of coordinating a project, mentoring someone, organizing volunteers or helping a team make a decision.
Describe the role precisely: “I coordinated the shared schedule” is different from “I managed the team.” Explain how you obtained agreement, handled a dependency or supported another person. If the vacancy requires formal people-management experience, these examples may show adjacent skills but do not erase that gap.
Check your examples against the resume
Review the submitted resume so that you can explain the work it describes. Check dates, numbers, scope and job titles against your notes. If a bullet is overstated, correct it in future applications; do not build an invented story to defend it.
A relevant interview example does not have to appear on the resume. Nor must you turn every story into a new bullet. The resume and interview serve related purposes, but space on the page should go to the most useful application evidence.
Roleframe is our product. If you use an AI assistant to organize practice, give it your own notes and ask it to flag missing details as questions. It cannot reconstruct unrecorded events reliably from a short bullet or know exactly which questions your interviewer will ask.
A practical preparation session
- Read the vacancy and any instructions about interview format, assessments or time limits.
- Choose a few relevant experiences and note your responsibility, action and outcome for each.
- Match them to possible prompts, then add examples where important responsibilities are not covered.
- Practice answering a question from brief notes. Check whether you answered it, rather than reciting every detail of the story.
- Try follow-ups about alternatives, collaborators, results and lessons. If you do not remember something, say so rather than filling the gap.
- Check the facts against your resume and remove confidential information from shared notes.
- Prepare practical arrangements and any accommodation request through the employer’s process where needed.
Frequently asked questions
- Which behavioral questions are most common?
This page provides practice prompts, not a frequency study. Conflict, mistakes, feedback, priorities and problem solving are useful themes to prepare, but employers choose questions for their roles and processes.
- Which questions are hardest?
Difficulty depends on your experience and the format. Give extra preparation to prompts where you struggle to identify a relevant example or explain your contribution. There is no universal hardest-five ranking.
- How much responsibility should I take for a mistake?
Acknowledge your actual part and explain the response. Do not shift your own responsibility to others, but do not invent total responsibility for a shared or systemic problem. Include context needed to understand the event.
- How long should an answer be?
Follow any stated limit. A concise one-to-two-minute practice answer can help with a straightforward prompt, but it is not a scoring rule. Let the question and follow-ups determine the useful level of detail.
- Can I reuse a story in the same interview?
Yes, if another part of it answers the new question. Briefly acknowledge the connection. Use a different example when that gives better evidence; there is no fixed permitted number of repetitions.
- What if I have no paid work experience?
Use relevant study, volunteering, personal projects or other appropriate experience and identify its context accurately. If a question specifically requires professional experience you do not have, explain that and offer the closest relevant example.
- Is “tell me about yourself” a behavioral question?
It usually asks for an overview rather than one past incident. Briefly connect your relevant background to the role. If the interviewer asks for a particular example as a follow-up, you can then use a more detailed story.
- What if I cannot remember an example immediately?
Take a moment or ask for clarification. If no exact example comes to mind, say so and offer a related one if appropriate. Do not present a hypothetical or someone else’s experience as your own.
Ready to start your new resume?
Writing a resume takes time, and even a polished one can miss what a hiring manager is looking for. Roleframe helps you build a clear, ATS-safe resume in minutes and tailor it to the job you want.
