For candidates
Behavioral video interview questions and STAR answers
The behavioral questions video interviews actually use, grouped by the competency each one tests, with worked STAR answers and the one change that matters when you are recording instead of talking to a person.
Behavioral video interview questions ask for a real example from your past, almost always opening with “tell me about a time you” or “describe a situation where.” The premise is that what you did before predicts what you will do next, so they want a story, not values. The answer to all of them is the STAR method.
What changes on video is who is listening. In a live call a person can follow up and pull you back on track. In a one-way or recorded interview you answer to a lens with no interviewer, one question at a time, on a timer. The questions are predictable in both, so a small set of well-built stories goes a long way. This page groups the behavioral questions by the competency each one tests, gives you worked STAR answers, and covers the one adjustment the recorded format rewards.
What a behavioral question is really testing
Every behavioral prompt is a proxy for a competency the employer cares about. “Tell me about a conflict with a coworker” is not about the coworker. It is checking whether you stay professional and solve problems with people, not around them. Once you can see the competency behind the question, the wording stops mattering. Ten phrasings of the same prompt all want the same kind of story.
That is why preparation works. You do not memorize an answer per question. You build four or five real stories that each show something different, then map them onto whatever phrasing comes up. The behavioral set clusters into six themes.
The questions you should expect, grouped by theme
You will not get all of these in one sitting. If you have a solid story ready for each theme, you are covered for almost anything a behavioral interview asks.
Teamwork and collaboration
- Tell me about a time you worked on a team to reach a goal.
- Describe a time you had to rely on someone else to get your own work done.
- Give an example of when you helped a struggling teammate.
Conflict and difficult people
- Tell me about a disagreement with a coworker or manager. How did you handle it?
- Describe a time you dealt with a difficult customer or stakeholder.
- Tell me about feedback that was hard to hear, and what you did with it.
Failure and mistakes
- Tell me about a time you failed or made a mistake. What happened next?
- Describe a time you missed a deadline or fell short of a goal.
- Tell me about a decision you would make differently now.
Pressure and problem-solving
- Tell me about a time you handled competing priorities or a tight deadline.
- Describe the hardest problem you solved at work and how you approached it.
- Tell me about a time things did not go to plan and you had to adapt.
Initiative and leadership
- Tell me about a time you took the lead without being asked.
- Describe a process you improved or a change you pushed through.
- Give an example of a goal you set for yourself and how you reached it.
Adaptability and growth
- Tell me about a time you had to learn something quickly.
- Describe a time you adjusted to a big change at work.
- Tell me about a time you stepped outside your comfort zone.
Most of these reward a single, specific story. A few candidates already prep this way with help from a tool. As one put it on Reddit, they run the job description and their resume through an AI and ask it for “the 5 questions with answers in STAR format most likely to be asked.” That is a reasonable starting point. The catch is that the delivery still has to sound like you talking, not reading, which the recorded format makes easy to expose.
Four answers in STAR
STAR is four beats: Situation (one sentence of context), Task (the problem in front of you), Action (what you specifically did, where most of your time goes), Result (how it turned out, with a number where you have one). On a live call the interviewer can nudge you. On a recorded interview no one can, so the structure does the work. These are templates to adapt to your own experience, not lines to recite.
”Tell me about a conflict with a coworker.”
Situation. A designer and I disagreed about the layout for a launch page, and the thread had gone back and forth for two days with no decision.
Task. The launch date was fixed, so we needed to settle it that day, and I wanted to keep the working relationship intact.
Action. I asked for fifteen minutes on a call instead of more comments. I came with the two layouts side by side and the one metric each was trying to win, conversion versus clarity. I asked what we were actually optimizing for rather than which one looked better. Once we named the goal, the choice was obvious to both of us.
Result. We shipped on time with the layout that fit the goal, and the designer and I have defaulted to a quick call over a long thread ever since. I have learned that most conflict at work is two people optimizing for different things they never said out loud.
Why it works: it never makes the coworker the villain, it shows a concrete de-escalation move, and it ends on what you took from it. Reviewers screen conflict questions for maturity, not for who was right.
”Tell me about a time you failed.”
Situation. I owned the rollout of a new onboarding email sequence, and three weeks in the open rates were less than half what we had forecast.
Task. I had to figure out what was wrong and fix it fast, without quietly hoping no one noticed the numbers.
Action. I flagged it to my manager myself before the monthly review and pulled the data apart. The sends were landing in the promotions tab because of how I had set up the from-name. I rewrote the sender details, ran a small A/B test to confirm, and re-sent to the affected cohort with a corrected version.
Result. Open rates recovered to just above the original forecast within two weeks. The bigger result was the habit: I now sanity-check deliverability on a small batch before any full send. Owning the miss early cost me a little pride and saved the whole campaign.
Why it works: it picks a real failure with a real fix, not a humblebrag. The point of a failure question is to see whether you own it, diagnose it, and change something. A candidate who has never failed has failed the question.
”Tell me about a time you handled a tight deadline.”
Situation. A client moved a deliverable up by a week the day before I went on a planned three-day leave.
Task. I had to protect both the deadline and the leave, which meant the work could not just expand to fill my absence.
Action. I broke the deliverable into what only I could do and what a teammate could pick up, did my parts first and front-loaded the hardest one, and wrote a one-page handoff so my colleague was not guessing. I gave the client a single point of contact for the days I was out.
Result. The deliverable went out on the new date, the client never felt a gap, and I took the leave as planned. Breaking a crunch into what is mine, what is shareable, and what can wait is how I keep a deadline from becoming a fire drill.
Why it works: it shows prioritization, delegation, and a calm system under pressure. It also resists the trap of proving commitment by canceling your own life, which signals poor planning, not dedication.
”Tell me about a time you took the lead.”
Situation. Our weekly report took someone half a day to assemble by hand, and the person who normally did it left.
Task. Nobody owned it, and it was about to fall on whoever blinked first. I decided to fix the cause instead of inheriting the chore.
Action. I mapped where the numbers came from, built a template that pulled most of them automatically, and documented the few manual steps that were left. I showed it to the team and offered to walk anyone through it.
Result. The report dropped from half a day to about twenty minutes, and three people can now produce it instead of one. I did not have a title that told me to do it. I just saw a recurring tax on the team and removed it.
Why it works: leadership questions are not asking for a manager title. They are asking whether you act on a problem you do not have to own. This answer shows initiative and a result without claiming authority you did not have.
The STAR-under-a-timer twist
If a person is on the call, this is the interview you already know. The format that catches people out is the one-way or recorded interview, where you answer to a camera with no interviewer. It changes how STAR has to behave.
Nobody pulls you back, so structure is the safety net. In a live interview you can over-explain the setup and the interviewer will ask “so what did you do?” On a recording there is no such rescue. The single most common STAR mistake here is burying the result: people spend forty seconds on the situation, the clock runs out, and the answer cuts off before they say what happened. Get to the action fast and always land the result. The full breakdown is in the STAR method on a one-way video interview.
It runs on a timer, and the prep window is short. Most recorded tools give you a brief window to think, often thirty to ninety seconds, then record for a fixed length with no pause. One candidate described having “30 seconds to prepare for a two minute answer” while “staring at myself through a screen watching a timer count down,” and called it close to impossible. It is jarring the first time and ordinary by the third. Read the first screen for the prep time, the recording length, and how many questions there are before you start, so the numbers are not a surprise.
Retakes are a setting, not a promise. Whether you can re-record is something the employer turns on or off. One fresher applying to a sales role “didn’t notice the time limit,” panicked on the first question, and found there “were no retake options.” So never assume a redo exists. If it does, save it for a genuinely bad take rather than chasing a perfect one. The detail is in how to pass a one-way video interview.
If your recorded answers are scored with AI, the honest version is reassuring. These tools mostly transcribe what you say and check it against the role’s criteria, then hand that to a human who decides. The major vendors stepped back from scoring faces years ago. So answer the question on its merits and speak clearly for the transcript, rather than performing for a camera you think is reading your expression.
Mistakes that quietly cost people
These apply to any behavioral interview and double on a recorded one, where there is no interviewer to recover the moment.
- Going hypothetical. “I would usually try to…” is not a behavioral answer. The question asked for a time it happened. If you genuinely lack a perfect example, use the closest real one and say what you did, not what you would do.
- The story with no result. Plenty of answers describe a situation and an action and then just stop. The result is the whole point. Even a modest, specific outcome beats trailing off.
- Making someone else the villain. Conflict and difficult-people questions screen for how you treat people under stress. Blaming the coworker, the customer, or the old boss tells the reviewer how you will talk about them one day.
- Reading a script word for word. It is the most visible mistake on camera. As one interviewer put it, “you can literally tell if someone is reading an answer to you.” Keep three or four bullet points off to the side, the four STAR beats in a couple of words each, and look at the lens.
- One story for everything. Stretching a single example to answer teamwork, conflict, and failure makes it obvious you have one story. Build four or five that each show something different.
Before you record
Pick your four or five stories, make sure each one reaches a clear result, and practice telling them in about ninety seconds out loud, not in your head. Open every answer with the point in the first ten seconds and let STAR carry the rest. If the interview is recorded, read the first screen for the timer and retakes, glance at notes rather than reading them, and remember a real person watches it before deciding whether to meet you.
For the structure itself, line by line, read the STAR method on a one-way video interview. For the broader question set beyond the behavioral ones, common video interview questions covers more ground, and if your role adds its own scenarios, video interview guides by role has the specifics.