IT Resume Workshop

Step 9: Final Checklist + Export

This is the “don’t lose to dumb stuff” step. You’re going to run a final pass for clarity, consistency, and credibility — then export cleanly.

Principle

A resume is a technical document. It should be consistent, easy to scan, and impossible to misread.

Final content checklist

  • The top half of page 1 makes your target role obvious (from Step 6).
  • Skills are grouped, readable, and reflect the job posting themes (Step 3 + Step 6).
  • Experience bullets lead with impact and include scope/results (Step 4 + Step 5).
  • Every tool you list is supported somewhere (Skills ↔ Experience ↔ Projects).
  • Projects/Labs are “resume-ready” and include evidence (link or write-up) (Step 7).
  • Nothing is exaggerated or impossible to defend in an interview.

Formatting + consistency checklist

  • Single-column, no icons/graphics, no tables/text boxes.
  • Consistent font sizes, spacing, and bullet indentation.
  • Dates are formatted consistently (e.g., Jan 2024 – Present).
  • Job titles and company names are consistent and aligned.
  • Bullets are mostly 1–2 lines; avoid paragraphs.
  • Section headings are standard (Experience, Skills, Projects, Education).
  • No weird widows/orphans (single words on a new line) if possible.

Credibility checks

If you get asked “tell me about this” in an interview, you should have a clean story for each item.

  • Every metric is either exact or clearly an estimate (~ / range).
  • No invented tools, responsibilities, or “expert” claims you can’t defend.
  • Project links actually open and look professional.
  • Spelling/grammar is clean (read it out loud once).
  • Contact info is correct (email/phone/LinkedIn/GitHub).

Export rules (PDF)

  1. Export to PDF from your editor (Word/Google Docs) — don’t “print to PDF” with weird scaling.
  2. Ensure the PDF is selectable text (not an image scan).
  3. Verify margins didn’t shift and bullets didn’t reflow.
  4. Open the PDF and do a 10-second scan test (does it look clean instantly?).

File naming

Use a clear format: First_Last_TargetRole_Resume.pdf
Example: Jake_Hulberg_SysAdmin_Resume.pdf

Last pass (the 10-second test)

Pretend you’re a recruiter scanning 100 resumes. If you only had 10 seconds, what would you notice?

  • Is the target role obvious?
  • Do the first 3 bullets show real impact?
  • Do the skills match what the job posting asks for?
  • Does it look clean and readable without effort?