To answer “describe yourself in three words”, choose three words that are true, that match what the role needs, and that each cover a different side of you: how you work, how you work with people, and what drives you. Say the three words, give one sentence of evidence for each, and finish with a line that ties them to the job. The whole answer takes 30 to 60 seconds. The proof matters more than the words: “curious, dependable, direct” followed by three quick, real examples beats a more impressive-sounding list with nothing behind it.
Below: why interviewers ask it, a five-step way to choose your words, how to deliver them, ten example word sets for tech roles with one-line proofs, words to avoid, and the common variations. Our “what are your strengths?” guide goes deep on one strength with a full story; this page is about a fast, three-part snapshot.
Why interviewers ask you to describe yourself in three words
It's a compression test. In a few seconds you have to show:
- Self-awareness. Do your words match what your résumé and your references would say?
- Fit. Do the words line up with what this team actually needs?
- Concise communication. Can you summarize yourself without rambling, the way you'd summarize a design in one sentence?
- An evidence habit. Do you back claims with examples, or stop at adjectives?
- Composure. The question can feel like a curveball, so a calm, prepared answer stands out.
It comes in several versions, and each has a twist:
| Wording you might hear | The twist | How to handle it |
|---|---|---|
| “Describe yourself in three words.” | Your own view | Three words, one proof each |
| “What three words would your coworkers use?” | Other people's view | Use words from real feedback: reviews, peer comments, thank-you notes |
| “Describe yourself in one word.” | Forces a top pick | Lead with your most role-relevant word, then one proof |
| “How would your manager describe you?” | Your manager's view | Paraphrase actual review language you can stand behind |
| “What would your last team say about working with you?” | Collaboration | Pick words about how you work with people |
The coworker version shows up in tech loops too: the Tech Interview Handbook's list of commonly asked behavioral questions at top tech companies includes “What words would your colleagues use to describe you?”
How to choose your three words
- Gather evidence first. Reread your recent performance reviews, peer feedback, code-review comments and messages where someone thanked you. Note the words other people actually used. Words you've been called are easier to defend than words you'd like to be called.
- Read the job description. Highlight the traits it repeats: “ownership,” “ambiguity,” “collaborate with product,” “high quality bar,” “mentor.”
- Cover three different sides. One word for how you work (thorough, fast, systematic), one for how you work with people (collaborative, direct, dependable), one for what drives you (curious, user-focused, accountable). Three near-synonyms waste two slots.
- Prefer precise words to generic ones. The table below shows common swaps.
- Test each word with a one-sentence proof. If you can't finish “For example, I…” with something real, drop the word.
| Generic word | Why it's weak | More precise options |
|---|---|---|
| Hardworking | Expected of everyone; describes effort, not outcome | Persistent, reliable, thorough |
| Team player | A cliché that says nothing about how | Collaborative, dependable, supportive |
| Passionate | Impossible to prove in a sentence | Curious, user-focused, invested |
| Detail-oriented | Overused, and can hint at slowness | Meticulous, careful, precise |
| Smart | Sounds arrogant and invites a test | Analytical, quick to learn |
| Problem solver | Nearly everyone in tech says it | Systematic, resourceful, tenacious |
| Perfectionist | Often heard as a weakness in disguise | Rigorous, quality-focused |
How to deliver the answer
Use a simple format: the three words, a one-line proof for each, and one line connecting them to the role. Here's an example we wrote for a backend role:
“I'd say curious, dependable and direct. Curious because I dig into why something broke, not just how to patch it; last month that turned a recurring timeout into a small connection-pool fix. Dependable because when I own an on-call week or a deadline, nobody has to chase me. And direct because I'd rather raise a risk in planning than at launch. Those three seem to fit a team that owns its production services end to end.”
- Say the words first, then explain. Don't make the interviewer wait for the list.
- Order by relevance. The word that matters most for this job goes first.
- Keep each proof to one sentence. If they want more, they'll ask, and then a full story helps.
- Skip the preamble. No “oh, that's a hard one.” Pause for two seconds if you need to, then answer.
10 example word sets for tech candidates
These are example sets we wrote for this guide to show the pattern. The proof lines are illustrative, not real candidates' stories; use words that are true of you and proof from your own work.
| Role or situation | Three words | One-line proof for each (example) |
|---|---|---|
| New grad software engineer | Curious, coachable, persistent | Taught myself Docker for my capstone; reworked my first pull request the same day I got review feedback; stuck with a flaky test until I found the race condition. |
| Backend engineer | Systematic, dependable, direct | Write a timeline for every incident I work; have never dropped an on-call handoff; flagged a schema risk in planning instead of at launch. |
| Frontend engineer | User-focused, precise, collaborative | Sit in on usability sessions before changing a flow; fix keyboard and screen-reader issues before calling a component done; walk through edge cases with designers before building. |
| SRE or DevOps engineer | Calm, methodical, proactive | Stay steady when leading an incident call; follow the checklist even at 3 a.m.; write the runbook before the page, not after. |
| Data engineer | Rigorous, pragmatic, transparent | Add data-quality checks to every pipeline; ship a simple batch job when that's all the use case needs; publish known data gaps where analysts can see them. |
| Machine learning engineer | Skeptical, experimental, clear | Check for leakage before trusting a great metric; run small experiments before big training jobs; explain model trade-offs to product managers in plain language. |
| Mobile engineer | Meticulous, empathetic, quick | Test on older devices and slow networks; read app-store reviews to find bugs; ship small releases often instead of big risky ones. |
| Senior or staff engineer | Strategic, supportive, accountable | Write the design doc that sets the direction; spend real time unblocking others in reviews and pairing; own the outcome when a plan I proposed goes wrong. |
| Career switcher into tech | Adaptable, disciplined, customer-minded | Moved from teaching into engineering; studied every morning before work for a year; bring years of explaining complex ideas to non-experts. |
| Startup or full-stack generalist | Resourceful, versatile, decisive | Built an internal admin tool from parts we already had; moved between the frontend, the database and the deploy pipeline in the same week; made quick, reversible calls when the founder was unavailable. |
Words to avoid, or use carefully
- Perfectionist or workaholic. Often heard as a disguised weakness or a burnout risk.
- Honest, loyal, punctual. Good qualities, but baseline expectations. They spend a slot without setting you apart.
- Humble, smart, brilliant. Calling yourself humble undercuts the claim; calling yourself smart invites the interviewer to test it.
- Funny, chill, nice. Fine traits, weak evidence for a job.
- Competitive. On an engineering team it can sound like a collaboration risk unless you explain that you compete with the problem, not your teammates.
- Buzzwords such as “synergistic,” “disruptive” or “rockstar.” They sound like a template.
- Words your answer contradicts. Saying “concise” at the end of a three-minute answer undoes itself.
Variations and follow-ups
- “Which of the three is most true?” Have your order ready and a reason for it.
- “Give me an example of the second one.” This is where your prepared story comes in. See our behavioral STAR examples for the format.
- “What word doesn't describe you?” This is the weakness question in disguise. Pick something real and show what you're doing about it; our guide to “what is your greatest weakness?” covers how.
- “What would someone who disagrees with you say?” Be honest and constructive: “They might say I propose fixes too quickly. I've learned to ask a few more questions first.”
- “Tell me about yourself.” The long-form version of the same question, often asked minutes earlier. Your three words should match the story you tell there; see “tell me about yourself” for software engineers.
How to practice
Write your three words and their proofs on one card, say them out loud five times, and ask a former teammate whether the words sound like you. Then practice them inside a full interview. CoPilot Interview's free AI mock interview builds behavioral questions from your résumé and the job description in the desktop app, reads them aloud and scores each spoken answer out of 10 with what to fix and a model answer. If you'd rather start in the browser with nothing to install, the same page has 113 real practice questions across 9 tracks, behavioral included. For a quick check on what else to prepare, try the two-minute interview readiness quiz.
Say your three words out loud
Paste your résumé and the job description, answer an AI interviewer out loud, and get a score out of 10 for each answer with what to fix and a model answer. Free for 15 minutes every day, no credit card.
Try a free AI mock interviewFAQ
Can I use the same three words for every interview?
You can keep a core set if it is true, but swap one word when a role clearly values something else. A startup role might call for “resourceful”, while a platform team might care more about “rigorous”. Change the proof examples to match each job too.
Should I explain each of the three words?
Yes, briefly. Give one sentence of evidence per word so the whole answer stays under a minute. Words without proof sound like guesses, and long explanations turn a quick question into a monologue.
Is “hardworking” a bad word to use?
Not bad, just weak. Nearly every candidate could claim it, and it describes effort rather than results. A more precise word such as “persistent” or “reliable”, backed by an example, tells the interviewer more.
What if I freeze when I'm asked to describe myself in three words?
Pause for a second, then use the three-sides shortcut: one word for how you work, one for how you work with people and one for what drives you. Preparing your words in advance is the real fix.
How do I answer “what three words would your coworkers use”?
Use real evidence: performance reviews, peer feedback, code-review comments and thank-you messages. Words other people have actually used about you are the most credible answer, and you can say where they came from.
How is this different from “what are your strengths?”
The strengths question usually wants one or two strengths with a full story each. The three-words question wants a quick snapshot across different sides of you, with a one-line proof per word and a fuller story only if the interviewer asks.