How to Write a Professional Resume That Reads as Evidence

Most resumes are a list of job titles with duties attached. They are accurate, they are unreadable, and they give a hiring manager nothing to decide with. A professional resume is a different artefact: a set of claims, each supported by a specific piece of evidence, ordered by how well they match the role.

The method

Write everything down first, without editing

Every role, every project, every thing you were responsible for. Do not judge or shorten. You are building a source document, not a resume.
For each item, ask what changed

What was different because you were there? If the honest answer is nothing, it probably does not belong in the document — though it may still be worth keeping in the source.
Find the number, or find the scope

Time saved, volume handled, people supported, money moved, errors prevented, team size, coverage, frequency. A number is ideal. A well-defined scope is nearly as good.
Write it as action, method, result

One line, starting with a specific verb, containing what you did and what changed. Read it aloud; if it sounds like a job description, it is not finished.
Cut anything that would be true of everyone

If a bullet would read identically under a different name, it is filler. Delete it.
Then tailor

Now select and reorder against the specific job description. This step is separate on purpose, because it is the step everyone skips.

The formula, with examples

Verb plus what you did, plus the mechanism or approach, plus the outcome. The examples below are all in the same weak-bullet category before rewriting.

Before	After
Responsible for customer support	Handled 60 to 80 support tickets a day across email and chat, keeping first-response time under two hours
Helped with the website redesign	Led the checkout redesign, which cut cart abandonment by 14% over the following quarter
Worked on reporting	Rebuilt the weekly reporting pack in a spreadsheet, replacing three manual exports and removing a full day of work per week
Managed a small team	Managed four engineers, running the planning cycle and taking on the two most difficult technical escalations
Improved processes	Mapped the invoice approval process and cut the average approval cycle from eleven days to four
Various admin duties	Reconciled supplier invoices monthly, resolving discrepancies that had previously been written off

Notice what changed. The rewritten versions contain no adjectives that claim quality, no self-assessment, and no soft skills. They are checkable. A hiring manager can ask a follow-up question about any of them, which is exactly what you want to invite.

Verbs that carry information

Use verbs that name a thing you did rather than a quality you have. Built, migrated, reduced, negotiated, wrote, diagnosed, launched, reconciled, eliminated, led, redesigned, cut, grew, delivered, automated, resolved, trained, saved all point at an action somebody could verify.

By contrast, spearheaded, leveraged, synergised, passionate about, dynamic, results-driven, detail-oriented, hard-working, proven track record are claims about a person rather than a record. They are unfalsifiable, they occupy space that an evidence bullet needs, and every candidate has them.

Where to find the numbers

Scope, not just size. "Supported 200 users across four offices" is a real number even if the money is confidential.
Time. Anything you made faster or less frequent. Time is a number everyone can picture.
Frequency. Weekly to monthly, manual to automated, quarterly to continuous.
Quality. Error rates, defect counts, complaints, review scores, audit findings — before and after.
Proportion. "Reduced exceptions by half" works without naming a total.
Ratios. Headcount, coverage, conversion, and similar comparisons are often publishable when absolutes are not.

The two-pass edit

Write the whole document, then edit it twice with different questions. The first pass asks: is this true and specific? Remove anything you cannot defend in an interview, and anything that would be true of a different candidate. The second asks: does this match this job? Remove what does not, even if you are proud of it. Pride is not a hiring criterion.

Most of the value is in the second pass, and it is the one that requires you to have read the job description carefully. That is why the section structure and the application checklist both assume tailoring happens last.

Common questions

Frequently asked questions

What if I genuinely cannot quantify anything?

Then write about scope and change rather than numbers: what you owned, how many people or systems you covered, what process you replaced, what would have happened if you had not done it. Specificity is the requirement, not arithmetic. A resume of vague sentences is a problem regardless of whether you have metrics.

Should the summary say what I want?

If you are changing direction or moving to a new sector, yes — it saves the reader from working it out. If you are applying for a straightforward move inside your field, the summary is better spent on your domain and seniority, since that is what they are trying to establish in two lines.

Is a cover letter required if the resume is strong?

Rarely strictly required, and frequently read when the resume is otherwise good. It is the only place you can explain a gap, a pivot or a genuine reason for interest. See the cover letter guide.

How long should my resume be after all this?

One page under roughly five years of relevant experience, two pages up to about fifteen, and two pages beyond that with a strong reason. Beyond two pages the marginal content is almost always padding. The resume versus CV guide covers the exceptions in academic and specialist roles.

Where to go next

These are the services referenced above. Compare them on your own terms before you sign up for anything.