"Are you a team player?" is one of the bluntest interview questions you'll encounter. Nobody says no. The question almost always appears in a more sophisticated form: "Tell me about a time you worked effectively in a team" or "Describe a situation where you had to influence colleagues who didn't report to you." The answer to all versions requires the same thing: a specific, well-structured example, not a list of positive adjectives.
Why interviewers ask about teamwork
Most roles require working with others, and most team problems come from people who either don't collaborate well or overstate their ability to do so. Interviewers are looking for someone who can do their own work AND work effectively with others who have different styles, priorities, and levels of seniority. They want to see that you've done this before and can articulate how.
Answering the direct question
If asked directly "are you a team player?", don't just say yes. Confirm briefly and then move immediately to an example: "Yes, and I'd say working effectively with others is one of my strengths. For example, in my last role..." The example is what makes the claim believable.
Behavioural teamwork questions
These are the more common form. Examples you should prepare for:
- "Tell me about a time you worked in a high-performing team."
- "Describe a situation where you had to work with someone whose style was very different from yours."
- "Tell me about a time you influenced a colleague or team to change direction."
- "Give me an example of when you put the team's needs ahead of your own."
Each needs a concrete STAR answer. Don't speak in generalities: "I always make sure to communicate clearly with my team" is not an answer. A specific situation where your communication prevented a problem is.
Sample answers
"Describe a time you worked effectively in a team"
"In my previous role, I worked on a cross-functional team tasked with launching a new B2B product in six months. The team spanned engineering, design, sales, and legal. The challenge was that each function had different priorities and different definitions of 'done'. What I did was set up a weekly sync where each team shared their three biggest blockers and dependencies on other teams. It sounds simple, but it surfaced misalignments early enough to solve them. We launched on time and the product had a significantly smoother rollout than previous launches the team had done."
"Tell me about a time you worked with a difficult colleague"
"A colleague in another team and I had consistently different views on project priorities, and it was slowing down decisions. Rather than escalating, I asked if we could have a conversation outside of the formal meeting structure. I came prepared with a clear picture of what my team's priorities were and why, and asked them to walk me through theirs. Turns out most of our differences came from not having visibility into each other's constraints. We ended up creating a shared priority tracker that both teams could see. The friction reduced significantly from that point."