Most people answer this question by listing adjectives. “My coworkers would say I’m reliable, collaborative, and detail-oriented.” That response is graded as a zero by most interviewers — not because it’s wrong, but because it’s empty. Any candidate can string three positive traits together. The question is specifically designed to get you to stop describing yourself and start describing what other people experience when they work alongside you. That shift is harder than it sounds, and how well you make it is what the interviewer is actually measuring.
Why interviewers ask this
The question does three things at once that a standard “tell me about yourself” cannot.
It tests self-awareness without asking for it directly. A candidate who genuinely reflects on how colleagues experience their work habits, communication style, and energy will answer differently from one who is recycling their LinkedIn summary. Self-awareness is one of the hardest traits to assess in an interview, so this question creates an indirect measure of it.
It checks for consistency with the rest of the interview. If you spend forty minutes telling the interviewer you’re a bold, decisive leader, and then say “my coworkers would describe me as someone who takes their time and consults everyone before moving,” that inconsistency is informative — either you’re performing the first answer or the second. If both answers feel true, the interviewer gets a richer picture of you. If they contradict each other, that’s also data.
It previews team fit. According to Gallup research, employees who have a best friend at work are seven times more likely to be engaged in their jobs — and engagement correlates directly with retention, output quality, and willingness to absorb difficulty during crunch periods. Hiring managers are not just filling a role; they are placing a person inside an existing dynamic. This question surfaces whether your working style will mesh or create friction.
None of this means the interviewer expects you to be beloved by everyone. They expect you to know how you actually come across — and to be honest enough to name both the strengths and, when relevant, the edge cases where your working style requires adjustment.
The three-part framework
A strong answer has three distinct beats, delivered in under two minutes.
Part 1: The trait (10–15 seconds)
Name one or two specific qualities — not a list of five. More than two signals that you haven’t thought hard about what actually stands out. The trait should be credible for your role and level. A senior engineer saying “creative” without anchoring it technically is vague. A marketing manager saying “detail-oriented” without specifying what kind of detail work lands differently than someone just reaching for a compliment.
Pick a trait that genuinely shows up in how you work, not the one you think sounds best.
Part 2: The evidence (60–75 seconds)
This is the load-bearing section most candidates skip. Connect the trait to a concrete example — a specific project, a recurring situation, or a pattern that colleagues would actually cite if asked. The framing is important: “I think they’d say I’m someone who…” versus “I know I’m reliable.” The first is externally referenced. The second is a self-assessment dressed as a coworker quote. Interviewers hear the difference.
Good evidence sounds like: “I think they’d say I’m the person who flags problems early, even when it’s uncomfortable — there was a launch last quarter where I pushed back on the timeline in a team meeting because the QA log had three unresolved P2 bugs, and even though it delayed us by a week, the PM thanked me afterward because the version we shipped had none of the issues we’d seen in staging.”
That is one specific incident, told from the perspective of what the team would remember, with a real consequence and a real outcome.
Part 3: The honest edge (15–20 seconds, optional but powerful)
If the role involves close collaboration, adding a brief acknowledgment of a trait that sometimes needs calibration — and what you’ve learned to do about it — elevates the answer from polished to genuine. “They’d also say I move fast and sometimes have to circle back to make sure everyone’s still with me — I’ve learned to build a check-in step into project milestones because of that.” This is not self-deprecation. It’s the kind of self-knowledge that experienced hiring managers trust.
12 sample answers
Software engineer, mid-level. “I think my teammates would say I’m someone who makes code review less painful. I got feedback early in my career that my PR descriptions were cryptic, and I overhauled how I write them — now I include a ‘what to look at and why’ section in every diff. A few engineers on my last team started copying the format, which I took as a sign it was actually useful. They’d probably also say I’m methodical to the point of being slow on greenfield work, but that I’m fast to spot integration issues that others miss.”
Software engineer, senior. “My coworkers would describe me as someone who asks the question nobody else wants to ask in a planning meeting — usually something like ‘what happens when this part breaks at 2 a.m.’ I have a reputation for being the person who stress-tests assumptions before they become incidents. The flip side is that I’ve been told I can seem skeptical even when I’m genuinely on board with something, so I’ve gotten more deliberate about saying explicitly when I think a plan is solid.”
Product manager, early-career. “I think they’d say I’m thorough in a way that’s sometimes surprising for someone junior. I prep obsessively for stakeholder meetings — I walk in with the data already visualized, the three objections already anticipated, and the fallback options ready. A few people on the engineering team told me our sprint kickoffs felt more organized than they had before I joined. That said, they’d also say I sometimes over-prepare for meetings that don’t need it, which I’m working on calibrating.”
Product manager, senior. “My last team would describe me as someone who protects engineering from scope creep in real time. I’m the person who says ‘that’s a good idea, let’s put it in the backlog for Q3’ rather than absorbing it into the current sprint. One PM peer told me I was unusually good at disappointing stakeholders in a way that didn’t make them feel dismissed — which I’d say is the actual core skill of the job. They’d also probably say I’m direct in a way that takes some adjustment if you’re used to softer feedback.”
Account executive, sales. “I’d guess my coworkers would say I’m the person they come to when a deal goes sideways. I’ve closed a few situations others had written off, and people know I don’t panic when the dynamics change late in the cycle. My manager told me in my last review that I’m ‘weirdly calm in bad news calls,’ which I’ll take. On the other side, they might say I can be impatient in pipeline reviews — I tend to push on deals that have been ‘almost there’ for more than three weeks because in my experience that’s usually a signal, not a phase.”
Customer success manager. “I think they’d say I’m the person who actually reads the client’s contract before a renewal call. A lot of CSMs work from memory on what a customer bought; I come in with the usage data, the original success criteria, and any open support tickets. Two clients renewed at a higher tier last year partly because I could show them quantified outcomes they hadn’t tracked themselves. My peers might also say I’m a bit of a note-taker — I document calls in more detail than most, which some find useful and a few find excessive.”
Marketing manager. “My team would probably say I’m clear on priorities even when the brief isn’t. We do a lot of fast-turnaround work where the initial request is vague, and they’ve told me they appreciate that I come back with a one-sentence statement of what we’re actually trying to accomplish before we start producing. That saves a lot of revision cycles. They’d also say I’m honest in creative reviews — I’ll tell a designer their first concept isn’t landing rather than wait for the client to say it, which is uncomfortable in the moment but usually faster overall.”
Data analyst. “I think they’d describe me as someone who translates numbers into decisions rather than just reports. I got feedback early on that my analyses were technically correct but hard to act on, so I restructured how I present findings — I lead with the recommendation, then show the data that supports it, rather than the other way around. My manager started asking me to present findings in team meetings that I used to just email, which I read as confirmation that something changed. They might also say I push back on vague data requests — I’ll ask what decision the analysis will support before I start pulling data, which not everyone loves initially but most people appreciate at the end.”
Operations coordinator. “My coworkers would say I’m someone who anticipates the handoff problem. A lot of processes break at the seam between teams, and I’ve gotten known as the person who maps those seams before a project launches. At my current company, I built a checklist for vendor onboarding that’s now used across three departments — it started because I noticed we kept losing the same three pieces of information between procurement and the receiving team. They’d also say I send a lot of follow-up emails, which is fair. I’d rather confirm something twice than have it fall through.”
HR business partner. “I think managers I’ve supported would describe me as someone who gives honest assessments rather than reassuring ones. I’ve had several cases where a manager wanted validation for a decision they’d already made, and I’ve told them the policy risk or the precedent issue directly, even when it wasn’t what they wanted to hear. One VP told me I was ‘the first HR partner who didn’t feel like legal protection for the company’ — I took that as the highest possible compliment for the kind of HR I want to do. My peers might say I’m not the first person to volunteer for high-visibility projects, but I’m usually the one who finishes them.”
Recent graduate / entry-level. “I think my classmates and the manager I interned for would say I’m someone who shows up completely prepared and then stays after to understand what happened. During my internship I made a point of debriefing with my supervisor after every client-facing task — not to ask for praise, but to understand what I’d missed. She told me in my final review that she’d never had an intern who asked as many follow-up questions about the reasoning behind decisions. That’s something I carry into every job: I want to understand the ‘why’ well enough that I could reconstruct the logic, not just repeat the output.”
Career changer, second role. “People from my previous industry who I’ve worked with would say I bring a perspective that stops the room sometimes — in a useful way. I spent six years in logistics before moving into tech operations, and I’ve found that a lot of software teams have never had to think about physical-world constraints like lead times, carrier reliability windows, or what happens when a dependency simply doesn’t exist yet. My coworkers at my current company have told me I make planning meetings more realistic. They’d also say I have a learning curve on terminology in any new environment, which is accurate — I ask a lot of basic questions early on, but I stop asking them quickly.”
What not to say
Generic adjective lists. “Hardworking, dedicated, and a team player” is not an answer — it’s a placeholder that tells the interviewer you didn’t prepare for this question. Every candidate in the building has those three words.
Thinly veiled self-promotion. “My coworkers would say I’m the best closer on the team” sounds like you wrote your own Yelp review. The question is asking you to inhabit someone else’s perspective, not amplify your own.
False modesty. “Oh, they’d probably say I work too hard and care too much” is a cliché the interviewer has heard in some form from roughly half of all candidates. It’s the “weakness that’s secretly a strength” trap applied to peer perception, and it lands as evasive.
Contradicting what you’ve already said. If you’ve spent the whole interview establishing that you’re a decisive, fast-moving operator, and then say “my coworkers would describe me as patient and methodical,” you’ve created a puzzle that works against you. Your answer to this question should be consistent with the rest of your interview — and if there’s apparent tension between two true things about you, name it directly rather than letting the interviewer wonder.
Describing traits that don’t fit the role. An answer that works perfectly for a solo contributor role (“I mostly keep my head down and produce”) is a red flag for a role that requires influence, cross-functional coordination, or people management. Before you answer, consider what the role actually needs from a teammate, and make sure your answer speaks to that context.
Preparing your answer before the interview
The best answers to this question come from actual evidence, not invention. Three practical ways to gather it:
Pull your last performance review or 360 feedback and look for the language other people used to describe your working style. Those phrases are the raw material for this answer.
Think about the last time a coworker thanked you in a specific way — not a generic “thanks for your help” but a specific thank-you for something you did that solved a problem for them. That interaction is usually a clue about what you’re actually known for.
If you have former colleagues you’re comfortable asking, a quick message — “I’m prepping for interviews, what would you say is the most distinctive thing about working with me?” — will often give you language more honest than anything you’d generate yourself.
Once you have the raw material, run the answer through the three-part structure: trait, evidence, honest edge. Keep it under two minutes. Practice it out loud at least three times, because this is one of the questions where your delivery signals as much as your content — a confident, considered answer reads as someone who has thought seriously about their impact on the people around them, which is exactly what a hiring manager needs to believe before they add you to a team.
The coworkers who will eventually describe you to the next person you interview are the ones you’re about to meet. The way you talk about your current team is, in a small but real way, a preview of how you’ll talk about this one.