How to Talk About Your Work Without Sounding Arrogant
The fear of sounding arrogant is what produces self-descriptions that don't land. Five steps for talking about your work in a way that's credible, accurate, and confident — without crossing the line.
You're in the conversation — interview, networking coffee, performance review, or just the moment a senior person asks 'what are you working on?' — and you can feel the trap forming. Say too little and you sound like you don't realize what you've done. Say too much and you sound like the person nobody wants to listen to at the team meeting. The line between confident and arrogant feels like it's two millimeters wide and shifts depending on who's listening.
The fear of crossing that line is what produces most of the awkward self-descriptions people give. They under-claim, qualify everything, deflect credit reflexively, and end up signaling uncertainty about work they did clearly and well. The result is the opposite of the goal — they sound either falsely modest or genuinely unsure of themselves, neither of which is the impression they wanted to leave. The five steps below are the structural moves that let you describe your work accurately without triggering the arrogance reaction in your listener.
Use the language of impact, not adjectives
Adjective-driven self-descriptions are what triggers 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. The discipline is to never describe yourself with an adjective when a specific outcome would do the same work.
Replace 'I' with 'we' judiciously — but not on the work that was actually yours
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.
Concrete numbers don't sound boastful; vague superlatives do
There's a counterintuitive rule about numbers in self-descriptions: specific numbers, even impressive ones, almost never trigger the arrogance reaction. Vague superlatives almost always 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. The instinct that big numbers will sound boastful is wrong; the instinct that vague superlatives sound humble is also wrong.
Lead with what you learned, not what you achieved
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.
Know when 'sounding arrogant' is a fear that's costing you the room
Most 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. Most people are accurate-to-generous when describing others and chronically 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.