How would your coworkers describe you? How to answer honestly

Pick two or three words or phrases your coworkers have actually used about you, in reviews, thank-you messages or feedback, and back each one with the moment that earned it. Quoting real feedback ("my team lead once said…") sounds honest and checkable, which is the point, because the interviewer may ask your references the same thing.

Why this question is different

"How would you describe yourself?" lets you choose your words. "How would your coworkers describe you?" asks you to step outside yourself, and the interviewer knows they can check it with your references. That changes the game: the best answer is the one your coworkers would actually agree with.

It also tests self-awareness. People who know how they come across tend to be easier to work with. People who give a glowing list of virtues tend not to.

Where to find real feedback

You probably have more evidence than you think. Spend 15 minutes looking through:

  • Performance reviews. Look for phrases your manager or peers repeated.
  • Thank-you messages. Emails, chat messages, cards when you left a job.
  • Peer feedback or 360 reviews, if your company does them.
  • Introductions. How do colleagues describe you when they introduce you to someone? "This is Sam, she knows everything about the CRM."
  • Requests. What do people come to you for? That's how they see you.
  • For students: comments from group project partners, a supervisor at a part-time job, or a teacher's reference.

Write down the exact words. Real phrases sound more convincing than polished adjectives.

Turn feedback into an answer

  1. Pick two or three descriptions that are true and useful for this job.
  2. Attribute each one to a real source, without naming them: "my manager", "a colleague in finance", "the people I trained".
  3. Add the moment behind one of them. A short example of why they'd say it.
  4. Optionally add one honest, mild trait that isn't purely flattering, if you can frame it well. This makes the rest more believable.

Aim for 45–60 seconds.

Generic claimFeedback-based version
"They'd say I'm reliable.""My team lead's phrase in my last review was 'the person I don't have to chase'."
"They'd say I'm a team player.""The two new hires I trained both mentioned me in their first-month feedback."
"They'd say I'm good with people.""Our sales team started copying me into tricky client emails, which I took as a compliment."
"They'd say I'm hard-working.""When I left my last job, three people said they'd miss having someone who just got things done."

Example answers

These use made-up details. Use the real words people have used about you.

Example answer for an office or operations role

"I think they'd say I'm calm and very organised. In my last review, my manager wrote that I'm 'the person who keeps the team out of panic mode', because during our year-end close I set up a shared checklist and a daily ten-minute check-in. A colleague in finance also told me I write the clearest emails on the team. They'd probably also say I can be a bit too quick to volunteer for things, which I'm learning to balance."

Example answer for a customer-facing role

"They'd probably say I'm patient and that I follow through. When I moved teams, a colleague wrote in my card that I was the only person who never left a customer hanging. I make a habit of calling people back when I said I would, even if I don't have the answer yet. They'd also say I'm the one who goes quiet when it gets noisy and then has the fix ten minutes later."

Example answer for a recent graduate

"My group project teammates would say I'm the organiser. In our final-year project, I set up the shared timeline and weekly meetings, and in our peer review one teammate wrote that the project 'would have fallen apart without the schedule'. My supervisor at my café job would say I'm dependable, since I was the one she called first when someone dropped a shift."

Example answer for an engineer

"I think they'd say I'm thorough and generous with my time. My code reviews are known for being detailed; one of the junior developers told me they learned more from my review comments than from our onboarding docs. They might also say I sometimes go too deep on a problem, and my lead and I have agreed I'll check in after a few hours if I'm stuck."

Mistakes to avoid

MistakeWhy it hurtsTry instead
A list of five glowing adjectivesSounds inflated and uncheckedTwo or three, with sources
"I don't know, you'd have to ask them"Sounds unaware or evasiveUse feedback you've received
Inventing a quoteYour references may say something elseOnly use what was actually said
Saying things only your friends would say"Fun" and "loud" don't help the jobStick to work behaviour
A "flaw" that's really a boast"They'd say I work too hard"A real, mild trait you're managing

Say it like you mean it

Quoting someone else's praise of you can feel awkward, so many people mumble or rush it. Practise until you can say "my manager wrote that…" in a normal, matter-of-fact voice. It's a fact, not a boast. Recording the answer once and listening back helps; the interview answer review shows your pace and filler words. In Speaking Coach, the interviewer can follow up with "Why do you think they said that?", which is a good test that the example behind the quote is ready.

Questions people ask

What if I've never received formal feedback?

Use informal signals: what colleagues ask you for, what they've thanked you for, or what a manager said in passing. "People usually come to me when…" is good evidence.

Should I name the coworker?

No. Use their role: "my manager", "a senior colleague", "the team I supported". Naming people adds nothing and can be awkward.

Can I include a negative trait?

One mild, honest trait can make the answer more believable, if you show you're aware of it and managing it. Keep it small and not central to the job.

How is this different from "Describe yourself in three words"?

That question wants your own three words. This one wants others' view, backed by feedback. See describe yourself in three words.

What if my coworkers would say something unflattering?

Then you've learned something useful. Pick the true, positive descriptions for this answer, and be ready to talk about the other one as a weakness you're working on.