Read the posting for the kind of archive work it needs

An archivist resume should show more than an interest in history. One opening may focus on arranging and describing collections; another may emphasize reading-room service, digitization support, or records intake. Highlight the tasks the employer actually names and the material you have handled, rather than treating every archive job as the same role.

In a short profile, identify your setting and strongest relevant task only if you have done that work. For example, a candidate might write: Archives assistant with experience processing small manuscript collections and answering supervised reference requests. Change the title and scope to match your own record; do not call a class exercise a professional appointment.

  • Material: manuscripts, photographs, institutional records, digital files, or another type you have actually worked with.
  • Task: intake, arrangement, description, reference, digitization, or another duty in the posting.
  • Scope: your independent work, supervised assignment, or contribution to a larger team project.

Describe processing work from task to usable result

Under each position or project, name the collection context, your action, and the handoff. Processed collections hides what you did. A more useful model, if true, is: Arranged donated correspondence under the project plan, labeled folders, and recorded discrepancies for the supervising archivist. The sentence distinguishes physical work from decisions owned by someone else.

If you rehoused material or supported preservation checks, say what you actually handled and whose guidance you followed. Do not imply you designed conservation treatment when you used an established procedure. Add collection size or turnaround time only if you have a reliable source and the figure helps a reader understand scope.

Make description and metadata specific

A description bullet becomes stronger when it names the output: a folder list, finding-aid draft, inventory, metadata review, or corrected record. State the rule or local workflow you followed only when you can discuss it in an interview. You can show accuracy through checks and revisions without claiming that every record was error-free.

For example, someone who did this work could write: Drafted folder-level descriptions from reviewed notes, checked names and dates against source material, and routed uncertain entries to the project lead. Replace the tasks with your own. If you edited records created by another person, use revised or checked rather than taking credit for the original description.

  • Output: inventory, finding aid, catalog record, metadata sheet, or documented correction.
  • Check: verified dates, normalized labels, flagged gaps, or resolved a question with a reviewer.
  • Handoff: prepared a draft for approval, updated an authorized record, or logged open issues.

Show how you helped people find and use material

If the role includes reference or public access, show what you did for researchers or colleagues. You might have searched a catalog, prepared requested boxes, explained a reading-room procedure, or referred a complex question to a specialist. Keep the bullet grounded in the service you delivered, not an unsupported claim that you transformed access.

Access work also involves boundaries. If materials had restrictions or required staff review, describe how you followed the local process without revealing private details. For a digitization project, distinguish scanning, file naming, quality checks, and publication decisions; do not claim you made material publicly available when your part ended at preparing files.

Use coursework and volunteer projects honestly

Early-career applicants can include practicum, class, volunteer, or internship projects with a clear label and dates. Give each project the same useful detail as paid work: material type, assigned task, output, and review step. A small, finished inventory can show more than a long list of courses without examples.

Put relevant training and systems in a separate skills or education section, but do not present exposure to a tool as proficiency. If a project used a local spreadsheet instead of the platform named in the posting, describe your transferable process and be clear about the tool you used. Keep restricted collections and unpublished donor information out of samples unless you have permission to share them.

Tailor the final resume and check the PDF

Compare your first few bullets with the actual posting. For a processing role, lead with arrangement and description; for an access role, move reference and retrieval examples higher. Keep employer names, project dates, collection relationships, and your share of team work consistent. Remove broad claims such as managed archives if you supported one defined stage of a project.

Preview the exported PDF for clear headings, intact dates, readable collection names, and working links to any permitted samples. CreateResume can help structure a role-specific resume draft and prepare PDF-ready output, but you should verify the terminology, permissions, and claims before applying.

  • Can a reader tell what material you handled and which tasks you performed?
  • Does each bullet separate your contribution from a supervisor or team decision?
  • Are any numbers, tool claims, and sample links accurate and shareable?