Project Stories on Teamwork, Conflict and Failure for a New-Grad Behavioral Round
Company: Capital One
Role: Software Engineer
Category: Behavioral & Leadership
Difficulty: medium
Interview Round: Onsite
A new-graduate behavioral round uses classic questions answered with stories from your own projects. The report singles out three themes: teamwork, conflict and failure. Prepare one story for each and tell it in a Situation, Task, Action, Result (STAR) structure.
### Clarifying Questions
- May stories come from internships, course projects, research or personal projects, or should they come from work experience?
- Is it acceptable to use the same project for more than one theme?
- How long should each answer be, and will there be follow-up probing on each story?
### Part 1 — Teamwork
Tell me about a project where you worked closely with other people to deliver something. What was your role, and how did you help the team succeed?
```hint Find your "I" inside the "we"
Pick a moment where something you did changed how the team worked together, not only a piece of code you wrote alone.
```
#### What This Part Should Cover
- The team's goal and your specific role in it
- A concrete action that improved coordination, unblocked someone or kept the work on track
- The result for the team, with a number or an observable outcome where possible
### Part 2 — Conflict
Tell me about a time you disagreed with a teammate or another stakeholder. How did you handle it, and how was it resolved?
```hint A disagreement worth telling
Choose a disagreement with real stakes, such as a design choice, scope or a deadline, where the other person had a reasonable point of view.
```
#### What This Part Should Cover
- The other person's position, stated fairly
- How you moved the disagreement toward a decision: listening, evidence, shared criteria, or escalation done well
- The outcome, including the working relationship afterwards and whether your view prevailed
### Part 3 — Failure
Tell me about a time you failed. What happened, what was your part in it, and what did you do differently afterwards?
```hint Own it, then show the change
A real failure had a cost. State your part in it plainly, then spend most of the answer on what you changed and how you know the change worked.
```
#### What This Part Should Cover
- A genuine failure with a real consequence, owned without blaming others
- The root cause on your side
- A lasting change in how you work, ideally with a later situation where it paid off
### What a Strong Answer Covers
- Three distinct, specific stories, rather than one project retold three ways or hypothetical answers
- A clear STAR shape with a short setup and most of the time spent on your own actions
- Measurable or observable results for each story
- Self-awareness: honest reflection on what you would do differently
- Concise delivery that leaves room for follow-up questions
### Follow-up Questions
- In your conflict story, what would you have done if the other person had refused to change their position?
- In your teamwork story, what would a teammate say was your weakest contribution?
- Since your failure, have you faced a similar situation? What did you do differently, and what happened?
- Which of these three stories would play out differently if it happened today, and why?
Overview: A new-grad behavioral round built on stories from your own projects, covering teamwork, a conflict with a teammate or stakeholder, and a failure, each told in Situation, Task, Action, Result form. It tests personal ownership, how you handle disagreement and whether you learn from your mistakes.
Read the full Capital One Software Engineer interview experience this question came from