Resume writing guide
How to Write Resume Bullet Points With Impact (Without Inventing Numbers)
Searching how to write resume bullet points, achievement bullets, or resume impact statements? Most advice skips the hard part: you already did the work, but the bullet still sounds like a job description.
"Managed a team." "Oversaw projects." "Responsible for client relationships."
True. Invisible. The hiring manager moves on in six seconds.
This guide is for people who do good work but can't say it yet: undersellers, graduates, career changers, and non-traditional paths. Same method whether you call it a resume or CV, and whether you're applying in the US, UK, Europe, or Asia.
Haiyaa exists to make this faster: Kai talks you through the work (voice or text), then builds honest bullets in a real editor. Pro adds JD tailoring when you're applying at volume.
Short path: Talk to Kai free → · When applications stack up, Pro for £9/mo (unlimited versions + cover letters).
What "impact" actually means on a resume
Impact is not a magic percentage. It is evidence a stranger can trust:
| Weak signal | Stronger signal (same job) |
|---|---|
| Managed a team | Ran weekly rota for 12 staff across two shifts |
| Handled customer complaints | Resolved billing disputes at the till; escalated fraud cases to the duty manager |
| Supported projects | Maintained the shared tracker so three teams saw blockers before stand-up |
| Responsible for stock | Counted weekly stock and flagged shortages before weekend peaks |
Notice: no invented "increased revenue 40%." Just what you owned, at what scale, with what consequence.
Numbers help when you have them. Specifics work when you don't.
The four-part bullet formula (honest version)
Use this as a checklist, not a mad-lib:
- Action: accurate verb (supported, built, tracked, trained). Don't upgrade to "spearheaded" unless you did.
- Scope: team size, geography, volume, timeframe, tools you actually used.
- Context: who cared, what constraint (short-staffed ward, peak season, launch week).
- Outcome: what changed, what didn't break, what got faster/safer/clearer. Only claim what you can explain.
Before: "Helped with onboarding."
After: "Buddy for two new starters on the ward: showed handover routine, shadowed first week of meds rounds, checked in daily until they were confident on the rota."
Same role. Defendable in interview.
Step 1: Dump the job-description language
Open a blank doc. For each job, write what you actually did on a bad Tuesday, not what HR called the role.
Prompts that unlock real bullets:
- What broke if you didn't show up?
- Who asked you for help when things went wrong?
- What did you do that nobody formally assigned you?
- What took you three months to learn that a new hire wouldn't know?
- What would your manager miss if you left?
If you freeze, that's normal. Talking beats typing for a lot of people. Kai's whole job is the follow-up question you wouldn't ask yourself.
Step 2: Separate duties from evidence
| Duty (vague) | Evidence (specific) |
|---|---|
| Customer service | Handled returns and complaints at a busy high-street store; kept queues moving at peak |
| Admin | Updated the rota and leave tracker so 14 staff always knew who was on shift |
| Project work | Built the onboarding checklist the team still uses for new hires |
Keep duties in your head. Put evidence on the page.
Step 3: Add numbers only when they're real
Good numbers:
- Team size, caseload, budget you tracked (not owned unless true)
- Frequency (daily, weekly, per shift)
- Time saved if you measured it or can rough-estimate honestly
Bad numbers:
- Percentages you can't source
- Revenue "impact" from work three steps removed from money
- "Increased efficiency 35%" because a template told you to
If you only have scope, lead with scope. Recruiters prefer 12-bed ward over significantly improved patient outcomes.
Step 4: Match the verb to the level
| You actually… | Say… | Don't say… |
|---|---|---|
| Did the work with guidance | Supported, assisted, maintained | Led, drove, owned (unless true) |
| Ran a process others relied on | Managed rota, tracked stock, coordinated handovers | Oversaw strategic initiatives |
| Made decisions when things broke | Escalated, resolved, decided hold vs dispatch | Executive leadership |
| Trained one or two people | Trained, buddy, onboarded | Built enterprise L&D programme |
Accurate beats impressive. Interviewers will ask.
Step 5: Order bullets by relevance
For each role, put the strongest evidence first, not chronological order within the job.
Applying to a care coordinator role? Lead with family communication and multi-agency handoffs, not the filing you also did.
That's the same logic as tailoring to a job description, but you can write a strong base first, then tailor per JD on Pro.
Before and after: three real patterns
Retail / hospitality
- Before: "Provided excellent customer service."
- After: "Served on a six-person floor during Saturday peaks; handled complaints at the till and kept wait times under 10 minutes when short one colleague."
Graduate / early career
- Before: "Worked on a group project."
- After: "Owned the user research sprint for a 4-person product module: 8 interviews, affinity map, final prototype presented to the module lead."
Experienced underseller
- Before: "Managed client relationships."
- After: "Primary contact for 6 mid-market accounts; prepared QBR decks, flagged renewal risk 60 days out, looped in legal on contract changes."
Do it alone vs do it with Kai
| By yourself | Haiyaa | |
|---|---|---|
| Getting past "managed a team" | Easy to stall | Kai asks the next question (free) |
| Honesty under pressure | Easy to inflate | Reframe, don't fabricate (live) |
| Structure | Blank page | Editor + PDF + public profile (live) |
| Per-job versions | Copy-paste rewrites | Pro tailor + cover letter (live) |
Kai is not a thesaurus. She interviews, then writes bullets from your answers. That's what ChatGPT won't fix if you don't already know what to say.
When a bullet should stay short
Not every line needs a novella.
- Older roles: 2–3 bullets max
- Irrelevant jobs: title + one line
- Gaps or pivots: cover in the letter, not fake bullets
Companion features (journal, wins tracking, interview prep) are on the roadmap, not live yet. For now, Haiyaa is the resume builder: get the bullets right first.
FAQ
Do I need numbers on every bullet?
No. Specifics beat vague verbs even without metrics. Invented percentages are worse than honest detail.
What if my job had no measurable outcomes?
Name ownership, scale, and consequence. That is impact recruiters can trust.
Is reframing lying?
Reframing sharpens the same facts. Lying adds what isn't true. Keep the verb accurate.
Can AI write my bullets?
AI can polish what you supply. Kai extracts the story first, then builds bullets with guardrails.
How long should each bullet be?
One to two lines. Lead with the strongest signal; cut filler.
CTA: Stop staring at "managed a team." Talk to Kai free → · Go Pro when you're applying weekly →