Behavioral interview questions and sample answers

01

What are behavioral interview questions?

The U.S. Office of Personnel Management, which writes interview guidance for federal agencies, says a behavioral interview exists to find out how a candidate actually behaved in past situations that called for the competencies the job requires. The Department of Veterans Affairs calls its version performance-based interviewing and mixes these questions with hypothetical ones.

In a structured interview, every candidate is asked the same questions and rated on the same scale. OPM notes that such interviews typically assess four to six competencies. That is why vague answers do badly: the interviewer is listening for evidence of a specific competency and has little to write down if you answer in generalities.

A question about what you would do in a hypothetical case is different. Those are situational interview questions, and they call for a different kind of answer.

02

Behavioral questions by competency

The posting tells you which of these matter most for the role. If you are early in your career, the eight career readiness competencies published by the National Association of Colleges and Employers make a useful checklist: career and self-development, communication, critical thinking, equity and inclusion, leadership, professionalism, teamwork and technology.

03

How to answer a behavioral question

Use the STAR method: the situation, the task you faced, the action you took and the result. Keep the first two brief and spend most of your time on the action. Say “I” when you describe what you did, because the interviewer is assessing you, not your team. Finish with a result, a number if you have one, and what you learned.

UC Santa Barbara’s career services suggests about 60 to 90 seconds for a behavioral answer.

04

Sample answers to behavioral questions

The three answers below are invented examples at different career stages.

Last year I was the designer on a checkout redesign, and the lead engineer and I disagreed about the address form. I wanted a single field with autocomplete. He wanted to keep five separate fields, because the autocomplete service had failed during an earlier launch. After two meetings we were holding up the sprint.

I asked him to walk me through that earlier failure. His concern turned out not to be the design but what happens when the service goes down. So I proposed building the single field with an automatic fallback to five fields if the service didn't respond within two seconds, and testing it on a small share of traffic for two weeks.

He agreed. In the test the single field cut form errors by about a third, the fallback fired a handful of times without anyone noticing, and we shipped it. He and I now do a risk review together at the start of every project.

The turning point is a question, not a compromise: the candidate found out what the other person was worried about. The result includes a lasting change in how the two work together.

In my first year as a payroll specialist, I missed a pay-rate change for fourteen warehouse employees who had just finished probation. The change arrived by email on a Thursday while I was closing payroll, and I set it aside for later. They were paid at the old rate.

One of them noticed the next morning. I told my manager right away, before she heard it from anyone else. I calculated the difference for each person and got an off-cycle payment approved, so they had the money within two days. I also called the warehouse supervisor myself to apologize.

Then I fixed the cause. Rate changes had been arriving by email with no deadline, so I set up a shared form with a cutoff two days before each close, and a checklist I run before I submit. In the two years since, we haven't missed one.

It is a real error with real consequences, owned without excuses. Two thirds of the answer is the repair and the change in process.

I worked weekends at a garden center through college. Every spring, customers asked the same questions hundreds of times: which plants survive frost, what grows in shade. New seasonal staff didn't know the answers, so customers waited for one of three experienced people and the register line stalled.

Nobody owned the problem, so I asked the manager if I could try something. I wrote a one-page sheet with the twenty most common questions and answers, checked it with our head grower, and taped a copy at each register. I also ran a fifteen-minute walk-through for new hires on their first Saturday.

The manager made it part of training for every seasonal hire after that, and the experienced staff said they were interrupted far less. I learned that I like making things easier for the next person.

A part-time job is enough when the story has a clear problem, an action nobody asked for and a result someone else adopted. There are more examples of this kind in entry-level interview questions.

05

How to build a story bank

1. List the competencies. Take them from the posting.
2. Brainstorm experiences. Projects, problems, disagreements, mistakes and wins from the last few years, from work, school or volunteering.
3. Choose three to five stories that cover the list between them. The best stories show two or three competencies at once, so one story can answer several questions.
4. Outline each one. A headline, then a line or two for each part of STAR, with the numbers you will need.
5. Practice aloud from the outline, not a script. A mock interview is the quickest way to find out which stories run long.

Story: [headline, for example "Rebuilt the onboarding checklist"]
Shows: [competency], [competency]
Situation and task: [one or two lines]
What I did: [three steps, in order]
Result: [number or outcome]
What I learned: [one line]
Could answer: [for example initiative, process improvement, working across teams]

06

Follow-up questions to expect

Interviewers often probe. OPM’s guide gives them example follow-ups for each part of your answer: what led up to the situation, what you did first, what mattered most when you decided how to act, and whether you would do anything differently. A story you lived through survives those questions. An invented or borrowed one does not, which is the best reason to use real examples.

Build the story bank as part of your wider interview preparation, next to your answers to the other common interview questions.

FAQ

Frequently asked questions