How to Talk About Your Work Without Sounding Arrogant
To talk about your work without sounding arrogant, describe specific outcomes instead of praising yourself, say 'we' for shared work and 'I' for what you owned, use concrete numbers rather than superlatives, and mention what you learned. If you usually undersell, describe yourself as you'd describe a colleague.
- Describe outcomes, not adjectives about yourself.
- 'We' for shared work, 'I' for what you owned.
- Specific numbers land better than superlatives.
- Mention what you learned, not only what you achieved.
- Describe your work as you'd describe a colleague's.
Talking about your own work credibly depends mostly on specifics. Concrete outcomes ('we shipped on time and the system has run for fourteen months') let listeners draw their own conclusions, while self-applied adjectives ('I'm a strong leader') invite doubt. Clear attribution, saying 'we' for shared work and 'I' for what you personally owned, reads as confident and honest. Measurable results stated plainly tend to sound less boastful than vague superlatives.
An interview, a networking coffee, or a senior person asking what you're working on. Say too little and you undersell; say too much and you sound like the person nobody wants to sit next to. The line feels two millimeters wide.
How do you describe your accomplishments without bragging?
Adjective-driven self-descriptions are what tends to trigger the arrogance reaction. 'I'm a strong leader.' 'I drove transformative change.' 'I'm passionate about excellence.' The listener has no way to verify any of these claims — they have to either accept them or push back, and most listeners default to skepticism. Impact-driven descriptions sidestep the verification problem entirely. 'I led a team of six through the platform migration; we shipped on time and the new system has been up for fourteen months.' The listener doesn't need to evaluate whether you're a strong leader; they can see the outcome and draw their own conclusion. Impact language is harder to write — it requires actual specifics — but it produces the impression that adjectives are trying to claim, with none of the friction. One useful habit is to reach for a specific outcome whenever an adjective about yourself would do the same work.
Should you say 'I' or 'we' when talking about your work?
There's a useful softening move that backfires when overused: replacing 'I' with 'we' to acknowledge that work happens on teams. 'We shipped the migration' often sounds more credible than 'I shipped the migration,' because most things in modern work do happen with collaborators. But the move only works for collaborative work. Applied to work you actually led individually — the analysis only you ran, the decision only you made, the document only you wrote — 'we' starts to read as either falsely modest or unclear about your role, neither of which is the goal. The discipline is calibration: 'we' for things the team genuinely co-owned, 'I' for things you owned individually, and explicit role-naming when the situation is mixed ('the team shipped the migration; I was the technical lead and owned the architecture decisions'). Listeners read calibrated attribution as confident; over-applied 'we' reads as evasive, and uncalibrated 'I' reads as credit-claiming.
"How would I describe this work if I were describing a colleague who did exactly the same thing?"
The single best calibration check for self-description. Most people describe colleagues' work accurately or generously, and their own work more conservatively. Writing the colleague version of your own work and then using it as your description is usually a cleaner truth than what your reflexive self-description would produce. If the colleague version feels uncomfortable to claim about yourself, the discomfort is the calibration error, not the description.
Do numbers make you sound boastful?
There's a counterintuitive rule about numbers in self-descriptions: specific numbers, even impressive ones, rarely trigger the arrogance reaction. Vague superlatives often do. 'I led the team that increased conversion by 47%' is a fact the listener can engage with neutrally. 'I led the team that achieved record-breaking results' triggers immediate skepticism even if the numbers are exactly the same. The reason is that specific numbers feel testable — the listener could in principle verify them — while vague superlatives feel like marketing copy. This means you can describe genuinely impressive work with high specificity and the listener will engage with it analytically, not defensively. Use real numbers when you have them. When you don't, use specific comparative framing ('cut investigation time from 45 minutes to under 10') rather than reaching for superlatives. Big numbers stated plainly usually don't sound boastful, and vague superlatives usually don't sound humble.
How do you talk about a project in an interview without bragging?
When the conversation is going to dwell on a single piece of work — a senior person asking about a specific project, an interview question requiring depth — the framing that lands best is what you learned, not what you achieved. 'The platform migration was the project where I learned how to manage cross-functional dependencies — I'd run technical projects before, but coordinating engineering, design, and customer success at that scale was new, and the lessons changed how I approach scoping now.' This framing does several things at once: it implicitly conveys the achievement (you led the migration), it signals self-awareness and growth (you learned from it), and it positions you as someone who will keep getting better. Pure achievement framing — 'I led the migration successfully' — leaves the listener wondering what you've taken from it. Learning framing answers that question proactively, in a way that compounds your credibility rather than competing for it.
What if you're underselling yourself?
Many people who worry about sounding arrogant are nowhere near the line. The fear itself is what produces the under-claiming that makes them sound less than they are. The signal you've crossed into this territory: are you walking out of conversations feeling like you sold yourself short? Are people who saw your work surprised when you describe it more modestly than they would? Are colleagues with similar work being recognized while you're being overlooked? If yes, the calibration error is in the direction of too modest, not too proud. The fix is structural: write out what you'd say about your work if you were describing a colleague who did exactly the same thing, and use that version. Many people are accurate or generous when describing others and conservative when describing themselves, which means the colleague version is closer to the truth than the self-version. Use the colleague version. The room will register it as confident-and-accurate, which is the impression the modest version was trying to produce and missing.
Get bullets and stories that sound credible, not arrogant
Brag Sheet Builder produces outcome-focused statements with three tone options — Bold, Balanced, and Quietly Powerful — calibrated to your audience and goals. Voice Match rewrites everything in your natural writing voice so the result sounds like you, not AI-confident. Tone tweak buttons let you fine-tune individual bullets between Softer and Stronger.
Found this useful? Link to it.
https://deftbrain.com/guides/career/how-to-talk-about-your-work-without-sounding-arrogant
Free to read, no account, no paywall — link away.