How to Write Resume Bullets for the Job You Actually Did
Most people write resume bullets that match their title rather than their actual work. Five steps for bullets that reflect the scope you really had — without overstating.
Your title says one thing. The work you did says another. Maybe you were a senior on the org chart but were leading the team's biggest initiative as if you were a manager. Maybe you were called a coordinator and were running a function. Maybe your title hadn't been updated in two years while your responsibilities had grown into the next level. Now you're writing your resume and you're staring at the gap between the title that's printed on the offer letter and the work you actually delivered.
Most resume bullets default to the title rather than the work, and the result is resumes that systematically understate what the candidate actually did. Hiring managers reading those resumes match the bullets to the title, conclude the candidate operated at the title level, and interview accordingly. The candidate who delivered above their title gets evaluated for the title they had rather than the work they did. The five steps below are how to write bullets that reflect actual scope without crossing into overclaiming — which is the calibration most people get wrong in both directions.
Lead with the action and the impact, not the title
Resume bullets are most powerful when they describe what was done and what changed, not the role under which it was done. 'Owned the customer onboarding redesign that cut activation time by 60% and unblocked the enterprise tier launch' is a bullet that signals the scope clearly regardless of whether your title was Product Manager, Senior Product Manager, or Lead Product Manager. The hiring manager reading it learns what you actually drove, which is what they're trying to figure out. Bullets that lead with the title or the role function — 'As a Product Manager, was responsible for onboarding initiatives' — bury the impact under structural information the reader already has from the title line. The fix is to make every bullet open with the action you took and the outcome that resulted. The title context is set by the role line above the bullets; it doesn't need to be re-stated in each one.
Include scope you didn't have title authority for — accurately
If you led work that was nominally above your title, the resume needs to show it — but the framing matters. 'Led migration project across three teams' is correct if you actually drove the project, even if your title didn't include the word 'lead.' 'Managed three teams' is incorrect if you didn't have direct reports, even if you coordinated their work. The honest framing for above-title scope usually uses verbs of leadership and coordination rather than verbs of authority: led, drove, owned, coordinated, partnered with, championed. These are verbs that describe what you actually did without claiming structural authority you didn't have. The hiring manager will understand the scope from the work itself; you don't need to claim a title you didn't hold to convey that you operated above level.
"Was nominally a Senior Engineer; actually led: cross-team migration project (4 teams, 9 months), incident response escalation procedure (used 47x in production), new-hire onboarding redesign (8 hires through revised process). Bullets describe the work, not the title."
This is a working example of how to handle the title-work gap. The work being claimed (cross-team migration, incident response procedure, onboarding redesign) is well above the typical 'Senior Engineer' scope, and the bullets describe it accurately without inflating the title or claiming structural authority that wasn't there. A hiring manager reading these bullets understands the scope; the title line provides honest context. No overclaim, no underclaim — just the actual work, named accurately.
Use the verb that names what you actually did
There's a class of weak verbs that fill resumes and convey almost nothing: 'helped,' 'assisted,' 'participated in,' 'supported,' 'worked on,' 'contributed to,' 'was involved in.' Each of these tells the hiring manager that you were nearby when the work happened, but not what you did. Replace each one with the verb that names your actual contribution. 'Helped with the migration' becomes 'Architected the migration plan' or 'Wrote the rollback runbook' or 'Ran the cross-team coordination' — whichever is true. The substitution requires you to be specific about your role, which is the work the resume bullet has to do. If you genuinely played a supporting role on a project, that's fine — but the bullet should still name what you specifically supported, not gesture vaguely at participation. 'Wrote the user research script that informed the redesign' is a stronger bullet than 'Participated in user research for the redesign,' even if both describe the same contribution.
Quantify in proxies if direct numbers aren't available
Resume bullets without numbers are systematically weaker than bullets with them, but most people skip the numbers because they don't have access to the headline metrics. Proxies are the workaround. If you don't have revenue impact, you may have process metrics: cycle time reduction, ticket volume changes, headcount of teams unblocked, number of releases shipped, percentage of time saved. If you don't have process metrics, you may have scope metrics: team size you coordinated, customer accounts touched, technical surfaces owned, transactions processed. If you don't have scope metrics, comparative framing works: 'Cut investigation time from 45 minutes to under 10,' 'Reduced approval cycles from three rounds to one,' 'Took the documentation from 200 pages to 40.' Some quantitative anchor in every bullet is the standard; the type of anchor varies by what's available. Bullets without any anchor read as activity claims that the hiring manager can't evaluate.
Know when the gap between title and work is a signal worth surfacing
Sometimes the gap between your title and your work is so large that it becomes the story rather than a footnote. The pattern: your title doesn't reflect what you did, the company didn't promote you to match the work, and you left (or are leaving) partly because of that. In these cases, the resume can quietly tell that story without complaining. The framing that works: clean bullets describing the actual scope at each role, listed at the level the work was done, without artificially adjusting the title line. The reader who knows the industry will recognize the level of the work and ask about the title gap in the interview, where you can address it directly: 'My title was Senior, but the scope I owned matched what we'd call Lead at most companies — that's part of why I started looking.' This framing positions the gap as honest information rather than as either complaint or overclaim. Hiring managers respect candidates who describe their work accurately, even when the official title was a mismatch. The title-work gap is real and common; pretending it isn't makes the resume less informative, not more credible.
Get bullets that reflect your actual scope — not your printed title
Brag Sheet Builder transforms vague descriptions of your work into outcome-focused bullets with verb upgrades, then uses the Metrics Excavator to replace estimates with real numbers. JD Tailoring rewrites bullets to match a specific job posting's language, scoring your match and surfacing the gaps to address before applying.