Skip to content

Saying "I", not "we"

In a behavioral answer, your own actions are told as "I" and the team's results as "we", so the interviewer can tell what you did. An answer that is all "we" leaves them guessing about your part.

On this page

What it is

Saying "I", not "we" is the habit of telling your own actions in the first person and the team's actions as the team's. It belongs to behavioral questions, where you describe something you did in a real past case, and to project walkthroughs. The person listening is assessing you, not your team. Amazon's published guidance for candidates says that when someone keeps saying "we", it is hard to judge their skill, because the interviewer can't work out what that person drove on their own. MIT's career office puts it from the candidate's side: "I" statements show ownership, while "we" statements leave an employer unsure what your skills actually are.

The habit is not about taking credit for the group's work. It is about accuracy: three ways of naming who acted, each with a job. You are taken to be a team player already; what is being asked is that you describe your own part as "I" while also giving what the team achieved, so the listener gets both the bigger picture and your share of it.

WordUse it forExample (illustrative)

"I"

Decisions you made, work you did, things you said, and the reason behind each

"I proposed splitting the release in two, because the second half had no customer waiting on it."

"We"

The team's goal, a decision the group made together, and the result the team delivered

"We shipped the first half two weeks ahead of the original date."

A name or a role

Work someone else did that your story depends on

"The QA engineer ran the load tests; I read the results and cut the slow path."

Why the split matters to the person across the table. Guidance written for interviewers tells them to listen for what the candidate personally did rather than what the team accomplished, and to probe when that is missing, with follow-ups such as "What was your specific role?", "What did you do next?" and "How did you decide on that approach?" A recruiter at a staffing firm writes that a lot of "we" might mean a strong collaborator, or might mean a story that isn't really the candidate's, and that the response is to redirect to the candidate's specific contribution. Our advice: make the split before anyone has to ask. A follow-up spent establishing your role is a follow-up not spent on depth.

The teammate test. A useful way to hear your own account: if a colleague from that project were listening, would they agree with who did what? Where they would object that you have claimed their work, switch to a name or a role. Where they would say you are underselling a decision that was yours, switch to "I". Follow-ups like "How did you decide?" and "What alternatives did you consider?" are easier to answer about a decision you actually made, which is one more reason to keep the account accurate rather than generous in either direction.

When to use it

Any question that starts "tell me about a time" or "give me an example of", and any walkthrough of a project you worked on. The Task and Action parts of a STAR answer are where it matters most: Yale's career office frames the Task beat as what your role was and how you helped reach the goal, and tells candidates to focus on their individual role, particularly when they worked in a team. Teamwork questions are where the split is hardest and most needed; the MIT office notes that it is especially tricky in examples of collaboration, and advises focusing the answer on how you contributed to the team's outcome.

Prepare the split before the room. Amazon's advice is to write down the accomplishments you plan to share, then look at each one and work out your individual role in it, because the role is the part to share in the interview. A candidate quoted on the same site describes having focused on "we" in an interview and says it created confusion about who owned what; the site's tip is to come ready to say which steps were yours and what you actually did.

Recorded and automated screens. In a one-way video answer there may be nobody to ask "what was your role?" afterward, so what you say the first time is what gets assessed. Our advice: in those formats, name your part explicitly within the first minute, and say the team's result as the team's in the same breath.

When not to

Some moments call for "we", and forcing "I" onto them sounds odd or dishonest.

  • When the question is about the team. "What did your team deliver last year?" or "How does your team run releases?" wants "we". Answer in "we", and add your part in a sentence if it is relevant.
  • When the work was someone else's. Don't convert "we" to "I" across the board. Interviewer guides tell them to probe how you decided and what alternatives you considered, and a decision you didn't make is hard to defend in detail. Say who did it, and say what you did with it.
  • When you managed the work rather than did it. A manager's "I" is the decisions of a manager: who you put on it, what you cut, what you escalated. The delivery is the team's. Claiming the hands-on work mismatches the role you held, and skipping your own decisions undersells it. Stories for a manager round goes further.
  • When it went wrong. "We missed the date" spreads a failure across people who may not have caused it, and "they missed the date" is blame. Say your part in the miss as "I", and keep the rest factual. See Failure and conflict without blame.
  • When the whole project was yours. Everything is "I" already, and the risk flips: you can sound as if you work without anyone. Mention who you consulted or who reviewed the work.

Compared

MomentAll "we"The splitWhen "we" is the right word

The team's result

"We got checkout under the target."

"We got checkout under the target. My piece was the image pipeline, which was most of the gap."

For the headline result itself, which was shared. Add your piece after it.

A decision

"We decided to delay the launch."

"I recommended delaying, and the product lead agreed."

When it was a group call you didn't lead. Then say what you argued for.

Work by others

"We ran the load tests and found the slow query."

"The QA engineer ran the load tests; I traced the slow query they found."

In the setup, where who did a background step doesn't matter to your story.

A failure

"We missed the deadline."

"We missed the deadline. My part was underestimating the migration; I hadn't checked the data volume."

When the cause was outside your control and the question is about the team's miss. State it plainly, then your response.

Managing the work

"We rebuilt the service."

"My team rebuilt the service. I chose to pause two features to staff it and defended that upward."

When the question asks about the team's output rather than your decisions.

In a picture

The questionScene: the teamMy task: I ownedMy steps: I choseOthers: by roleResult: weFollow-ups
The scene and the result belong to the team. The task and the steps in the middle are yours, told as "I", with other people's work named as theirs.

How to say it in an interview

The common mistake

Quiz

Your team shipped a feature and you wrote its API layer. Which opening gives the interviewer the most to work with?
The interviewer asks, "How does your team handle on-call?" Which word should carry most of the answer?
You told a step as "we", and the follow-up is "How did you decide on that approach?" What is this most likely doing?
You managed a team that rebuilt a service. Where does your "I" belong?

Related

Sources

  1. 6 common mistakes candidates make during their Amazon job interview, and tips to avoid them
  2. I'm a recruiting manager at Amazon: here are 7 things I'd do differently if I could interview again
  3. Using the STAR method for your next behavioral interview (MIT Career Advising and Professional Development)
  4. The Behavioral Interview (Yale Office of Career Strategy)
  5. What Are Behavioral Interviewing Questions (DDI)
  6. Behavioral Interview Questions That Reveal How Candidates Actually Perform (Kelly Services)
Sign in to report a mistake