"How Would Your Coworkers Describe You?" A Practical Guide to Answering Well
3 views
Interviewers ask "How would your coworkers describe you?" because it forces you to look at yourself from the outside. It is a softer cousin of "What are your strengths?", but it is harder to fake. A self-description can be pure marketing; a description attributed to other people invites the follow-up question "Can you give me an example?" If you are not ready for that, the answer collapses.
What the interviewer is really checking
- Self-awareness: do you know how you come across to others?
- Consistency: does your answer match your resume, your references and the way you have behaved in the interview so far?
- Team fit: are the traits you mention the ones this team actually needs?
Step 1: Collect real evidence
Before your interview, look back at performance reviews, peer feedback, LinkedIn recommendations, Slack shout-outs or thank-you emails. Write down the adjectives and phrases people actually used about you. You will usually find that two or three themes repeat. Those are your answer. Using words other people genuinely said is far more convincing than picking flattering words from a list.
Step 2: Pick two or three traits that match the job
Reread the job description. If it emphasises cross-team work, "the person who keeps everyone in the loop" is more useful than "really fast coder." If it is a support role, "calm when customers are upset" matters more than "creative." Choose traits that are both true and relevant.
Step 3: Attach a short story to each
The formula is simple: trait, evidence, impact.
Example for a software engineer:
"I think my teammates would say I'm the person who makes code reviews useful rather than painful. In my last team I started leaving a short summary at the top of each review explaining the main concern and what was just a nitpick. A couple of engineers told our manager it made them less anxious about reviews, and our average review turnaround dropped by about a day. They'd probably also say I'm a bit too eager to refactor, which I've learned to balance by separating refactors into their own pull requests."
Example for a project coordinator:
"My coworkers would probably call me the organised one. When our department moved offices, I built the shared checklist everyone used, and my manager mentioned in my review that nobody missed a deadline during the move. They'd also say I'm direct; I'll flag a risk in a meeting rather than wait, which I think the team appreciates even if it isn't always comfortable."
Notice that both answers include one mild, honest flaw. That is optional, but it makes the answer feel credible and shows maturity.
Mistakes to avoid
- Listing five adjectives with no stories.
- Choosing traits that contradict what your references will say.
- Making it about your boss's opinion rather than your peers'. The question is about colleagues.
- Picking something irrelevant to the role just because it sounds impressive.
Prepare for the follow-up
Good interviewers will dig: "What would someone who didn't enjoy working with you say?" Have an honest, non-catastrophic answer ready, plus what you did about it. That shows you can take feedback, which is often the real point of the question.
Practising out loud
Because this question is about perception, it helps to rehearse with a friend who has actually worked with you and can tell you whether your answer rings true. Some candidates also use an AI interview assistant during the real thing. Linkjob AI (https://linkjob.ai) gives real-time help during job interviews and technical interviews, which can help you remember the specific stories you prepared when nerves make your mind go blank. The stories themselves, though, need to come from your own work history.
Answer this question with real words from real colleagues, connect them to the job, and back each one with a concrete example. That combination is hard to beat.