Match the proofreading stage to the posting

A proofreader resume is strongest when it says what kind of copy you checked and when you received it. A final PDF proof, a web page before publication, and a manuscript after copyediting call for different checks. Read the posting for its formats, style guide, deadlines, and approval process, then lead with the work you have actually performed.

Keep proofreading distinct from rewriting. If you also made structural edits or checked facts against sources, name those tasks separately rather than implying that every proof included them. A short profile can specify your material and stage: “Proofreader of web articles and final page proofs, with experience checking style consistency and recording queries for editors.” Use that line only if it reflects your work.

  • Material: articles, product pages, reports, book pages, or another format you handled.
  • Stage: draft review, laid-out proof, pre-publication check, or corrected proof.
  • Boundary: corrections you made, questions you raised, and approval held by someone else.

Turn careful reading into observable bullets

“Excellent attention to detail” does not show what a reader can rely on you to catch. Write a bullet around the input, the check, and the handoff. For example, if accurate: “Checked final newsletter proofs against approved copy, corrected punctuation and heading inconsistencies, and returned a query list to the editor before release.” This tells the employer what you did without claiming responsibility for the whole publication.

Choose two or three examples that differ in format or checking task. You might have compared a revised PDF with marked corrections, reviewed link text in web copy, or checked captions against a supplied style sheet. Do not add a numerical error rate or turnaround promise unless you can document how it was measured.

  • Weak: “Proofread content and ensured accuracy.”
  • Stronger, if true: “Compared revised page proofs with marked corrections, logged remaining layout and punctuation issues, and sent unresolved items to the production editor.”
  • Name the final artifact: annotated PDF, change log, corrected file, or approved proof.

Show how you separate corrections from queries

A good proofreader knows when not to guess. A misspelled heading can be corrected under an agreed style, while an unfamiliar name, ambiguous date, or conflicting product term may need an author or editor to decide. Describe the reference you used and how you marked the uncertainty for the next reviewer.

If a team uses a style sheet, explain what you checked against it: capitalization, abbreviations, numbering, or repeated terminology. Only claim fact-checking when you verified the information against an identified source; flagging a doubtful claim is a different contribution. This distinction makes your scope credible.

List tools by the proof you delivered

A list of software names can obscure your process. Pair any tool with a task you completed: tracked changes for copy corrections, PDF annotations for page proofs, or a publishing preview for link and display checks. Include a tool only if you could explain how you used it on a real assignment.

If you worked from a house style guide, mention that rather than claiming mastery of a named manual you did not use. For a web role, a link or mobile-display check may matter; for print, comparing changes after layout may matter more. Tailor the skill line to the employer’s format instead of stuffing every possible editing term into it.

Choose samples without exposing private drafts

A published page does not automatically prove which corrections you made. If you have permission to share a before-and-after example, label the material, your exact role, and the approval stage. A short, self-created sample with a marked proof and query list can also demonstrate a method, provided you label it as a practice sample rather than client work.

Do not publish internal proofs, tracked changes from a client, or another writer’s unpublished text without permission. Where samples cannot be shared, describe the format, checking scope, and handoff in your resume. Check that any portfolio link works without a private login and that its attribution agrees with your bullet.

Proof the application with the same discipline

Before sending your resume, verify names, titles, dates, hyphenation, and punctuation consistency. Read the exported PDF at normal size and check for a line break that separates a heading from its bullet, clipped links, or a stray earlier employer name in a cover letter. Have someone else review it if possible; familiar text is easy to skim.

In CreateResume, keep a role-specific draft with your most relevant proofing examples and preview the PDF-ready layout. Open the actual exported file before attaching it. The goal is not to promise an error-free career, but to show a repeatable checking process and a clear record of the work you owned.

  • Does each bullet name a check or deliverable rather than only a personal trait?
  • Can you explain who resolved every query you mention?
  • Are the PDF, cover letter, and sample links consistent and accessible?