Build your resume from one target vacancy, a verified evidence list, and a final file check—not from a universal template.
This walkthrough uses a fictional customer-operations applicant. The names, employer, dates, and example details are invented; the goal is to show the editing decisions, not promise an interview. Harvard recommends specific, active, factual language and tailoring. UC Berkeley likewise advises matching evidence to the role’s requirements. Those are writing practices, not guarantees about hiring outcomes.
Start with the vacancy and your evidence
- Save the posting and note the employer’s required format, deadline, location, and any credential or authorization questions.
- Underline three tasks that appear central to the job. Separate required qualifications from preferred ones.
- For each task, list a specific example from work, school, volunteering, or a personal project. Record where the detail came from: a report, calendar, project file, public artifact, or your own recollection.
- Mark any gap honestly. A missing requirement is not solved by copying its wording into a skills list.
Your evidence sheet is a private source document, not a resume section. Keep confidential employer records out of public portfolios and do not expose customer or coworker information.
Choose sections by the reader’s first question
Use a conventional structure unless the employer or profession asks for another format: contact details, a brief summary if it adds useful context, relevant experience or projects, education, and skills. Put the strongest relevant evidence early. A new graduate may lead with a project; a career changer can use a short profile before dated work history. In either case, keep the timeline understandable.
Within an experience entry, identify the action, its scope, and an output or result. A number belongs only when you can explain its unit, time period, source, and your contribution. If records do not support a metric, describe a verifiable deliverable instead. List tools only when you can explain how you used them.
Worked example: from duty list to evidence-backed resume
- Task: Apply for a customer-operations coordinator role whose posting emphasizes accurate case records, billing handoffs, and weekly reporting.
- First output/attempt: “Hard-working professional seeking a challenging opportunity. Responsible for helping customers and completing reports.”
- Mistake or weakness: The summary could fit almost any applicant, and the experience line hides the actual work. There is no evidence that the candidate handled the posting’s central tasks.
- Human correction: The fictional candidate checks an old resume, a personal project log, and a non-confidential description of the handoff process. They confirm they documented unresolved account cases, routed billing questions to the correct team, and prepared a recurring spreadsheet summary. They remove an unverified claim that they “cut errors by 30%.”
- Quality check: Map each sentence to its evidence source: handoff procedure for routing, the candidate’s own task notes for documentation, and a saved report template for the spreadsheet work. The “three of three requirements mapped” count is an illustrative editing check, not a hiring measure. Check that no confidential record or customer detail appears in the file.
- Final usable result: Summary: “Customer-support professional experienced in documenting account issues, coordinating billing handoffs, and preparing recurring spreadsheet reports.” Experience bullet: “Documented unresolved account questions, routed billing exceptions to the appropriate team, and prepared weekly spreadsheet summaries for a supervisor.” This is a fictional example; use the wording only where it matches your own verified work.
The improvement comes from replacing a general claim with tasks the candidate can explain. It does not claim a measured business result that the evidence cannot establish.
A 30-minute beginner exercise
Choose one real posting and make a six-row table with these columns: requirement, your example, evidence source, your role, safe resume wording, and unresolved gap. Fill one row before drafting. For example, “weekly reporting” might map to a report template you created, the fields you maintained, and the person who used it. If you have no evidence for a requirement, label it “not yet demonstrated” and decide whether a small practice project could help.
Save the posting, completed table, and final export together in a private application folder. Ask a reviewer to point to the evidence supporting each sentence; revise any line they cannot trace. Do not share confidential employer material with the reviewer.
Pass check: Your finished artifact is a target-specific draft plus an unresolved-gap list. Pass when every resume claim maps to a source or has been removed. Keep the posting and evidence table privately; do not attach confidential records.
Check the file you will actually submit
- Follow the employer’s requested file type and complete portal fields yourself rather than assuming the attachment populated them.
- Open the exported PDF or DOCX. Select and copy its text into a plain editor to check reading order, dates, symbols, and section headings.
- Review the visual file at ordinary zoom for page breaks, small type, and headings stranded at the bottom of a page.
- Click portfolio and profile links, confirm the exact tailored version is attached, and use a clear filename.
Frequently asked questions
Should I use one resume for every job?
Keep a private master record, then make a separate submission copy for each target. Reorder truthful evidence and clarify relevance; do not alter dates or invent qualifications.
What if I cannot quantify a result?
Name the deliverable, audience, frequency, or process you owned. A specific nonnumeric statement is more defensible than a guessed percentage.
Should I include a summary?
Use one when it quickly explains a relevant specialty, transition, or combination of experience. If it repeats the job title and generic traits, spend the space on evidence instead.
A useful next step
Use this to audit the finished submission copy. the resume-mistakes checklist. Use this once the evidence table is ready. the resume-tailoring guide.
Turn the evidence map into the actual file
Before formatting, draft the strongest three to five bullets for the target role. Keep a private master record with the original note, the resume wording, and the source that can verify it. A source can be a project file, an employment record, a published artifact, a supervisor who can confirm the work, or a report you are permitted to reference. If the supporting material is confidential, do not attach it; rewrite the bullet at a safe level or use an approved reference.
| Draft line | What supports it | Final check |
|---|---|---|
| “Documented unresolved billing issues and assigned a next owner.” | Illustrative handoff notes and team process checklist. | Did the candidate record the details and assign—or only recommend—the owner? |
| “Reduced resolution time by 30%.” | No source report or comparable period found. | Remove the number; do not replace it with another guessed result. |
| “Excel: pivot tables.” | Completed spreadsheet sample with a source note. | Can the candidate explain the steps in a follow-up conversation? |
A resume is not a transcript of everything you have done. It is a selective explanation of relevant evidence. If an item is required on an application form, provide it there even when it is not useful on the resume. If a project is still in progress, label that status and avoid wording that implies completion. A useful final proofread asks three separate questions: is every fact accurate, is the evidence relevant to this target, and can a reader understand the line without knowing the backstory?
Choose order by evidence, not seniority
Put a recent project before experience only when it directly demonstrates a requirement and is labeled as a project. If recent paid work is the closest match, keep experience first. A career changer can use a short profile and selected project to make the direction legible, but retain dated roles and titles. Test the order by showing the exported file to a reader for 20 seconds and asking them to name the target role and one supporting example. Record the answer and the line you moved; do not add a generic summary to solve a navigation problem.
Sources
- Harvard College Guide to Creating a Strong Resume — Supports specific, active, fact-based writing, tailoring, clear organization, and checking a converted PDF. Checked 2026-10-17.
- UC Berkeley Career Engagement: Resumes — Supports matching resume evidence to required and preferred qualifications and emphasizing targeted accomplishments; its one-page recommendations are student-specific. Checked 2026-10-17.