Should I say "we" or "I" in an interview?

In an interview you should say "I" for your own responsibility, decisions and actions, and "we" for the team's goal and the shared result. Using both, each in its place, sounds credible and shows your part clearly.

Does saying "I" in an interview sound arrogant?

Saying "I" in an interview does not sound arrogant when it describes facts about your work, such as "I wrote the test plan". It sounds arrogant when it claims the whole result or leaves out people who clearly contributed.

How do I talk about a team project in an interview?

To talk about a team project in an interview, give the team's goal in one sentence, state your own responsibility, then describe two or three things you did and how they affected the result. Name colleagues briefly where they did key work.

What if my role in the project was small?

If your role in the project was small, describe it precisely anyway, because a small, clear contribution is more convincing than a large, vague one. Say what you owned, what you learned and what you would do with more responsibility.

Should I use "I" in "Tell me about yourself"?

Yes, the answer to "Tell me about yourself" should be built from "I" sentences, because the question is about you, not your employer. Mention the company and the team as context, then say what you did there.

What if I notice I said "we" in the middle of an answer?

If you notice you said "we" in the middle of an answer, correct it in one short sentence and carry on, for example: "To be precise, that part was mine: I wrote the specification." A calm correction sounds confident and gives the interviewer exactly the detail they were missing.

We vs I in Interviews: How to Show Your Part

In Short · Reading time: 10 minutes

Saying "we" instead of "I" in an interview hides your own contribution: the interviewer already knows the team delivered, and wants to know what you did.
Use "we" for the goal and the outcome, and "I" for your responsibility, your decisions and the problems you solved.
In German-speaking countries the same rule applies, and structured interviews make it sharper, because follow-up questions keep asking what you did.

Contents

Why Is Saying "We" Instead of "I" a Problem in an Interview?
What Does the Interviewer Want to Hear When You Talk About a Project?
When Is "We" the Right Word?
How Do You Turn a "We" Answer Into an "I" Answer?
Before and After: One Project Answer, Rewritten
Does This Apply to Interviews in Germany, Austria and Switzerland?
Why Is It Hard to Notice Your Own "We"?
Your 6-Step Plan to Say "I" Without Losing the Team
FAQ
Bottom Line

"We completed the design." "We managed the contractor." "We delivered the project."

Every sentence is true. None of them tells the interviewer what you did.

Why Is Saying "We" Instead of "I" a Problem in an Interview?

Saying "we" instead of "I" in an interview is a problem because it answers a question the interviewer did not ask: they know the team delivered the project, and they want to know your part in it. The hiring decision is about one person. A story told entirely in "we" gives them nothing to decide on.

Too much "we" leaves the interviewer with two bad options. Either they assume your role was small, or they wonder whether you are taking credit for work the wider team did. Neither helps you.

The habit is understandable. Most real work is teamwork, and saying "I" can feel like boasting. Many people are also taught to share credit, and they are right to.

The fix is not to drop the team. It is to make your own part visible inside the team's story.

The team delivered the project. You are there to explain your part in it.

What Does the Interviewer Want to Hear When You Talk About a Project?

When you talk about a project, the interviewer wants to hear four things: what you were responsible for, which decisions you made, which problems you solved and what your contribution changed in the outcome. That is the evidence a behavioural question collects.

The US Office of Personnel Management describes behavioural interview questions as asking candidates to describe past behaviour in a situation relevant to the job, on the principle that past behaviour is the best predictor of future behaviour. A "we" answer describes the team's past behaviour, not yours.

Employers have a reason to ask this way. A 2022 meta-analysis by Sackett, Zhang, Berry and Lievens in the Journal of Applied Psychology ranked structured interviews as the strongest predictor of job performance among the selection procedures it re-examined.

What the interviewer checks	Weak signal	Strong signal
Responsibility	"We were in charge of the design."	"I owned the structural design package for the substation."
Decisions	"We decided to change supplier."	"I recommended the switch, and the project manager signed it off."
Problems	"We had delays with the contractor."	"I set up a weekly progress check with the contractor's site lead."
Contribution to the result	"We delivered on time."	"The project finished on time; my part was keeping the design changes inside two weeks."

The examples are illustrative. Yours need your own facts.

When Is "We" the Right Word?

"We" is the right word for the team's goal, for decisions you genuinely made together and for the final outcome, as long as your own part is stated next to it. Good answers use both words, each where it belongs.

Context and goal: "We had to connect the new wind farm to the grid before the end of the year."
Shared decisions: "We agreed as a team to split the testing into two phases."
The outcome: "We went live in November."
Your part: "I wrote the test plan and ran the first phase."

Overcorrecting is a risk too. An answer in which you did everything alone sounds less believable, not more. Interviewers in technical and project roles know how many people a delivery takes. Naming who did what, including others, shows that you understand the work.

"We" sets the scene. "I" is the evidence.

How Do You Turn a "We" Answer Into an "I" Answer?

To turn a "we" answer into an "I" answer, keep the team's story but answer four questions about yourself inside it: what you were responsible for, what you decided, what you solved and what you contributed. The STAR method (Situation, Task, Action, Result) gives those answers a fixed place.

STAR step	Typical "we" version	What to add
Situation	"We had a big integration project."	Keep it short; "we" is fine here
Task	"We needed to hit the deadline."	Your own responsibility, in one sentence
Action	"We worked hard and fixed the issues."	Two or three things you did, with verbs like "proposed", "built", "negotiated"
Result	"We delivered on time."	The outcome, and the part that came from your actions

The Action step carries most of your answer. If someone else did a key step, say so: "My colleague handled the permits; I handled the technical review." That sentence is honest, and it makes your part clearer.

The same rule applies to the classic opening question, "Tell me about yourself". A summary such as "We built three plants in five years" says something about your employer. "I led the electrical design on three plants in five years" says something about you.

Before and After: One Project Answer, Rewritten

The same project story becomes a strong answer once the "we" sentences that carry the evidence are rewritten as "I" sentences. Here is one illustrative example for a project engineer.

Before:

"We had a substation upgrade with a tight deadline. We completed the design, we managed the contractor, and there were some delays, but we solved them. In the end we delivered the project on time."

After:

"We had to upgrade a substation within eight months. I was responsible for the design package and for coordinating the civil contractor. When the contractor fell behind, I introduced a weekly check against the schedule and moved two design reviews earlier so their crew was never waiting for drawings. We delivered on time, and the contractor's delay did not reach the commissioning date."

The second version is not longer because it is padded. It names one responsibility, two actions and one result. Every sentence gives the interviewer something to ask about next, and the details in it are invented for the example; yours must be real.

Does This Apply to Interviews in Germany, Austria and Switzerland?

Yes, the we-versus-I rule applies in Germany, Austria and Switzerland, and structured interviews there make it more visible, because interviewers are trained to keep asking what you did. In German the difference is a single word, "wir" or "ich", and it carries the same weight.

The personnel handbook of the Swiss canton of St. Gallen (2025) tells its interviewers to ask behavioural questions and to make a habit of follow-up questions about behaviour and result. If your first answer is "we", the next question will be "and what did you do?". Being ready for it saves the conversation from sounding like an interrogation.

Three points matter for international applicants:

Write your part into the CV as well. A German CV, the Lebenslauf, is read as a factual record. If your bullets say "Projektleitung" but the interview story stays at "we", the two do not match.
If the interview is in German, practise the phrases beforehand. Say "Ich war verantwortlich für …" (I was responsible for …) and "Ich habe … übernommen" (I took over …) aloud a few times. In a second language it is easier to slip into general phrases and "wir"; a ready phrase prevents that.
Modesty and precision are not opposites. A factual sentence such as "I calculated the cable sizing" is not boasting. In DACH interviews, plain facts about your own work tend to land better than superlatives.

The same applies to the question "Why should we hire you?" ("Warum sollten wir Sie einstellen?"). Its answer is about you, so it is built from "I" sentences backed by examples.

Why Is It Hard to Notice Your Own "We"?

You rarely notice your own "we", because you know exactly what your part was, while the interviewer hears only the words you actually say. When you say "we fixed it", you remember the night you found the error. The interviewer hears a team.

Reading your answers on paper does not show the problem either. It appears under pressure, when you speak freely and fall back on habit. That is why practising aloud, and getting feedback on the answer you actually gave, helps more than rereading notes. A mock interview on TalentVP, for example, scores each typed or spoken answer and shows a model answer built from your own CV, which makes it easier to see where your part went missing.

Your 6-Step Plan to Say "I" Without Losing the Team

List three projects you will talk about. Choose the ones that match the job ad.
Write one sentence per project on your responsibility. Start it with "I was responsible for".
Add two decisions or actions that were yours. Use specific verbs; avoid "helped" and "supported" unless that was truly your role.
Name others where they did the work. One short clause is enough.
Say each answer aloud and count the "we"s. Every "we" in the Action step should become "I", or name the person who did it.
Prepare the follow-up. For every project, be ready for "And what exactly did you do?".

Bottom Line

The team delivered the project. You delivered your part.

Saying "we" instead of "I" in an interview is a habit, not a strategy. Keep "we" for the goal and the result, and use "I" for everything the interviewer is actually trying to learn about you.

Credit the team. Own your part.

Sources

Structured Interviews, U.S. Office of Personnel Management: behavioural description questions and the past-behaviour principle
Revisiting meta-analytic estimates of validity in personnel selection, Sackett, Zhang, Berry & Lievens, Journal of Applied Psychology 107(11), 2022: structured interviews ranked as the strongest predictor of job performance among the procedures re-examined
Fragetechnik für Bewerbungsgespräche (PHB SG 80.2), Personalamt Kanton St. Gallen, February 2025

Related Guides

AI mock interview: practise answers aloud and get feedback on each one
Interview study library: questions and model answers by role
Interview Blueprint: one job, one CV, one preparation plan
German CV rules and format: how your Lebenslauf should match your interview stories