Katkat
Back

New-Grad Behavioral Round: Teamwork, Conflict, and a Failure

Capital OneSoftware Engineer · Onsite
MediumSoftware EngineerOnsiteBehavioral & Leadership

Last updated

A new-grad onsite behavioral round asking for three separate stories from your own project work: one on teamwork, one on a disagreement with someone else, and one on a real failure. Tests whether you can tell a specific, honest story with your own contribution clearly visible, rather than a generic or deflected answer.

This is a classic new-grad behavioral round. You'll be asked for three distinct stories, each drawn from a real project you've worked on (an internship, a class project, a hackathon, research, or personal work are all fair game unless the interviewer says otherwise). Prepare one story for each prompt below and be ready to tell it in Situation, Task, Action, Result (STAR) form, with enough specificity that a follow-up question wouldn't catch you flat-footed.

Prompt 1 — Teamwork

Walk me through a project you shipped alongside other people. Where did you personally add the most value, and what made the collaboration work?

Prompt 2 — Conflict

Describe a disagreement you had with a teammate or someone outside the team. How did you move it toward a resolution?

Prompt 3 — Failure

Walk me through something that went wrong on your watch. Where was the mistake yours, and what's different about how you operate now?

What makes an answer land in this round

  • A story, not a résumé line. Specific enough that the interviewer could ask "what did you say in that meeting" and you'd have a real answer, not a reconstruction on the spot.
  • Your own "I" inside the team's "we." Especially for Prompt 1 — a team's success isn't your answer unless you can point to the specific decision or action that was yours.
  • A disagreement with real stakes, for Prompt 2 — not a trivial style preference, and not one where the other person was simply wrong and you were simply right. The interviewer is listening for how you handled someone who had a legitimate, different point of view.
  • An actual failure, owned, for Prompt 3 — something that had a real cost (missed a deadline, shipped a bug, made a bad technical call), told without quietly blaming a teammate, a vague "the scope changed," or a non-failure dressed up as one ("I failed to get an A+").
  • A change that followed, for Prompt 3 specifically — the interviewer wants to hear what's different about how you work now, not just remorse.

How it's likely to be run

Expect the interviewer to let you tell each story largely uninterrupted, then probe with one or two follow-ups per story — often "what would you do differently" or "how did the other person react." A story that can't survive a follow-up question usually wasn't specific enough to begin with.

Hints

Hint 1

For the teamwork story, write down the team's outcome first, then force yourself to name the one or two actions that were specifically yours — if you can't separate them, pick a different story.

Hint 2

For the conflict story, be able to state the other person's position in a sentence that they themselves would agree is fair, before you explain why you still thought you were right (or why you changed your mind).

Hint 3

For the failure story, resist the urge to pick something small and safe — a failure with no real stakes reads as evasive, and interviewers notice.

Hint 4

Rehearse each story out loud once, with a timer, aiming for roughly 90 seconds to 2 minutes unprompted before you'd expect a follow-up.

Follow-up questions

  • What would you have done differently if the conflict you described hadn't resolved the way it did?
  • Was there a moment in the teamwork story where you considered a different approach and didn't take it? Why not?
  • How do you know the change you made after the failure actually worked — did a similar situation come up again?
  • If you could redo that project from the start, what's the one thing you'd change first?