Skip to main content
CreateCVOnline

Resume examples

Resume examples: four rewrites, before and after

Not sample documents to copy — four real editing problems, shown side by side. A summary that said nothing, an experience block that listed tools instead of work, a skills section that mixed products with personality traits, and a career change described from the wrong side. Each one comes with a note on exactly what changed and why.
1Professional summary

Store manager applying for a district manager role

Seven years in specialty retail, currently running one large store, applying for a multi-site role. The original summary was the first four lines the hiring panel would read, and it said nothing that could be checked.

Before

Results-driven retail professional with a proven track record of success in fast-paced environments. Excellent communication and leadership skills. Passionate about delivering outstanding customer service and motivated to take on new challenges within a dynamic organisation.

After

Store manager with seven years in specialty retail, currently running a $4.2M flagship with 32 staff. Took the lowest-ranked store in a 14-store region to top three on both sales per hour and shrink within two years. Promoted twice; trained four assistant managers who now run their own sites.

What changed, and why

  • Every adjective that a competing candidate could also claim came out. “Results-driven”, “proven track record” and “fast-paced” appear on a large share of retail resumes and carry no information whatsoever.
  • Store volume and headcount moved into the first sentence. A district manager hiring reads volume as a proxy for the complexity you can handle, and $4.2M with 32 staff answers that before the experience section is reached.
  • The two numbers the function is genuinely run on — sales per hour and shrink — replaced “outstanding customer service”, which is an aspiration rather than a measure.
  • The promotion history and the four managers trained were added, because a district role is largely a people-development job and that is the only evidence in the document for it.
  • The word count barely moved. Four sentences before, three after — the difference is that every clause in the second version is falsifiable.

Template used for this rewrite: Operations CV

2Experience block

Data analyst applying for a senior analyst role

Four years at one employer, strong work, invisible on paper. The entry listed the tools and the meetings but never said what the analyst was responsible for or what changed because of them.

Before

Data Analyst, Northbrook Health — 2021–Present

  • Responsible for creating reports and dashboards for various stakeholders.
  • Used SQL and Tableau to analyse data.
  • Assisted with data quality initiatives.
  • Attended weekly meetings with business teams to gather requirements.

After

Data Analyst, Northbrook Health — Mar 2021 – Present

  • Own the claims analytics layer: 40+ dbt models over roughly 120M rows, refreshed nightly and relied on by finance, clinical operations and the actuarial team.
  • Replaced a 30-tab spreadsheet reforecast with a Tableau model, cutting the monthly cycle from six days to one; it is now the figure the CFO reports to the board.
  • Found and corrected a mapping error in the provider dimension that had overstated out-of-network spend by around $1.8M a quarter for three quarters.
  • Built the SQL onboarding path now used by every new analyst — five hires through it since January 2023.

What changed, and why

  • “Responsible for” became “own”, and the scope came with it: the named layer, the model count, the row count, the refresh cadence and the three teams that depend on it.
  • The tools stopped being a bullet of their own. A line that says only “Used SQL and Tableau” is a keyword hiding from its evidence; both terms now appear inside sentences describing what was built with them.
  • The error-catch bullet was added. Analysts are hired to notice things, and finding a mapping fault that had been misstating spend for three quarters is the most on-brief evidence the role can offer.
  • The requirements-gathering bullet was deleted outright. Attending meetings with business teams is the job description, not an achievement, and it was occupying the fourth-most-read line of the entry.
  • Months were added to the dates. Year-only ranges are read as an attempt to blur a tenure, even when they are not.

Template used for this rewrite: Data Scientist

3Skills section

IT support specialist applying for a systems administrator role

The skills list was a fifteen-item comma-separated string that mixed operating systems with personality traits. A hiring manager filtering for endpoint management could not tell in five seconds whether this candidate had it.

Before

Skills

Microsoft Office, Windows, Communication, Teamwork, Problem solving, Time management, Customer service, Active Directory, Fast learner, Attention to detail, Office 365, Printers, Hardware, Networking, Troubleshooting

After

Technical skills

Identity and endpoints: Active Directory, Entra ID, Intune, Group Policy, BitLocker

Cloud and productivity: Microsoft 365 administration, Exchange Online, SharePoint

Networking: TCP/IP, DNS, DHCP, VPN, VLAN configuration, Meraki

Scripting: PowerShell — intermediate; wrote the starter and leaver provisioning script now in daily use

Service management: ServiceNow, ITIL v4 Foundation

Certifications: CompTIA Network+ (2023), Microsoft MD-102 Endpoint Administrator (2024)

What changed, and why

  • The soft skills came out entirely. “Teamwork”, “fast learner” and “attention to detail” cannot be verified from a document, every reviewer discounts them, and they were displacing things a hiring manager can actually filter on.
  • The remainder was grouped under five plain category labels, so a systems administrator scanning for identity management finds it in one second instead of reading a comma-separated wall.
  • Vague entries became named products. “Networking” turned into the protocols and the hardware; “Windows” turned into the identity and endpoint stack; “Printers” was simply deleted.
  • One honest proficiency marker was added on the skill where the level genuinely matters, with a piece of evidence attached to it — far more persuasive than a five-star rating bar, which no reader trusts and no parser can read.
  • Certifications were pulled out onto their own line with the years they were issued, because licences and certifications are frequently searched and filtered as a separate field.

Template used for this rewrite: IT Professional

4Career-change reframe

Paralegal applying for a financial-crime compliance role

Six years of regulatory litigation support, no compliance job title anywhere on the page. The original document described the work in the vocabulary of the field being left rather than the field being entered.

Before

Summary, and two experience bullets

  • Experienced paralegal seeking to transition into a compliance role. Strong legal background and eager to apply my skills in a new industry. Hardworking and detail-oriented.
  • Prepared legal documents and correspondence for attorneys.
  • Maintained case files and ensured deadlines were met.

After

Summary, and two experience bullets

  • Paralegal moving into financial-crime compliance, six years in regulatory litigation support. Built and ran the document-hold process for two federal investigations and completed the ICA International Diploma in Anti-Money Laundering in 2025. Comfortable turning a regulation into a checklist somebody else can follow.
  • Ran document preservation and production for two federal investigations — 90,000+ documents, four custodial interviews, no missed production deadlines across 14 months.
  • Wrote the firm’s conflict-check procedure after a near-miss; the same eight-step checklist is now run before every new matter by a team of 30.

What changed, and why

  • The original summary spent all three sentences on the candidate’s wishes. Nobody hires to satisfy an applicant’s ambition, so the rewrite leads with what transfers and puts the qualification that makes the move credible in the second sentence.
  • “Seeking to transition” became “moving into”. One is a request for permission; the other is a fact already in progress, backed by a named diploma with a year on it.
  • The document bullets were re-pointed at the target job. Preservation, production and deadline discipline are the same work a compliance analyst does under a regulatory request — the rewrite simply says so in the vocabulary of compliance rather than litigation.
  • The conflict-check bullet was promoted from a line buried further down, because writing a control that other people execute is the closest thing in a paralegal’s record to a compliance deliverable.
  • Nothing was invented. Same employer, same duties, same six years — described from the point of view of the role being applied for instead of the role being left.

Template used for this rewrite: Legal CV

What all four rewrites have in common

The four documents came from different industries and different career stages, and the same five edits did most of the work in every one of them.

  • Adjectives out, nouns and numbers in. Not one of the after versions describes the candidate as hardworking, passionate or detail-oriented. The evidence does that job, and it does it credibly.
  • Verbs of ownership. Own, ran, built, wrote, rebuilt. Never responsible for, assisted with or involved in, all of which are compatible with having done almost nothing.
  • The reader’s first question answered first. A district manager wants store volume; a senior-analyst hiring manager wants the size of the data and who depends on it; a systems administrator wants the identity stack. Each rewrite front-loads the thing that reader needs.
  • Scale attached to every claim. 32 staff, 120M rows, 90,000 documents, a team of 30. Without the scale, an achievement floats free and the reader silently assumes the smallest plausible version of it.
  • Nothing invented. Every after version describes exactly the same work as the before version. That is worth stating plainly: rewriting is a problem of retrieval and framing, not of embellishment.

How to check your own rewrite

Five tests, in the order that catches the most problems fastest. Run them on your current role first — it is the entry that gets read.

  1. Cover the employer name. Could this sentence belong to anybody else who has held the same job title? If yes, it is a job description and needs a number or a specific.
  2. Read only the first three words of each bullet. That is roughly what a skim-reader takes in. If those openings are “Responsible for the”, “Assisted with the” and “Worked closely with”, the entry is invisible.
  3. Count the adjectives in your summary. More than three and you are asserting rather than showing.
  4. Ask what the reader learns. If everything in an entry could have been guessed from your job title alone, the entry has not earned its space.
  5. Read it aloud. Anything you would be uncomfortable saying to an interviewer’s face is either overstated or badly phrased, and both are worth knowing before somebody else finds out.

Layouts that suit a rewritten document

Single-column designs with a real summary block and enough room for a dense experience entry, including the four used in the case studies above.

Operations CV

corporate · one column

Pro

Data Scientist

technology · one column

Pro

IT Professional

technology · one column

Pro

Legal CV

classic · one column

Pro

Modern Minimal

modern · one column

Free

Business Professional

corporate · one column

Free

Finance CV

corporate · one column

Pro

Tech Minimal

technology · one column

Free

Frequently asked questions

Summaries, soft skills, confidential numbers and the awkward parts of an employment history.

Three or four lines, and no more than about sixty words. It needs to answer four questions: what you are, how long you have done it, the scale you operate at, and the one or two things you are measurably good at. If a fifth sentence is creeping in, it is usually an adjective sentence and it can go. The test is whether the summary would still be true if you pasted it onto a stranger’s resume — if it would, it is describing a job title rather than a person.