IT Resume Workshop

Step 2: Resume Structure

Your resume should be easy to scan in 10 seconds and defensible in a 30-minute interview. This step locks in a clean structure before we obsess over bullet wording.

Principle

A well-structured resume beats a "clever" resume. Keep it simple, consistent, and readable.

The recommended layout
This structure works for most IT roles (help desk → sysadmin → cloud). Adjust emphasis, not the format.

Order (top to bottom)

  1. Header: Name, location (optional), phone, email, LinkedIn, GitHub/portfolio
  2. Summary (optional): 2–3 lines, role + strengths + direction
  3. Certs / Skills: grouped and scannable (we'll refine next step)
  4. Experience: most recent first, 3–6 bullets per role
  5. Projects / Labs: 2–4 items max, "real project" framing
  6. Education: keep it short, bottom of page

What recruiters should instantly see

  • What you do / want to do (role)
  • What environments you've worked in (Windows, M365, Azure, networking, etc.)
  • Proof you've delivered outcomes (quantified bullets)
  • That you can communicate clearly (clean formatting + tight writing)
ATS-safe formatting rules
Keep the formatting boring. Let your content do the work.

Do

  • Use a single-column layout
  • Use standard section headings (Experience, Skills, Projects, Education)
  • Use consistent spacing and bullet indentation
  • Use simple fonts and black text (no icons)
  • Export to PDF only at the end (final step)

Avoid

  • Columns, tables, text boxes, or heavy visual design
  • Skill bars, charts, or "proficiency meters"
  • Walls of text (keep bullets tight)
  • Overstuffing keywords (it reads like spam)
  • Unclear job titles (use what you can defend)
1 page vs 2 pages
Simple guideline: earn the second page with strong experience.

Default recommendation

  • 1 page for entry-level through early mid-level (most people)
  • 2 pages only if you have enough strong, relevant, quantified experience to justify it

Rule

If page 2 is mostly fluff, old irrelevant jobs, or filler skills — cut it. One strong page wins.

Quick structure checklist

  • Section headings are consistent and easy to scan
  • Dates and titles align cleanly (no weird spacing)
  • Bullets are short (1–2 lines each)
  • Most important info is top half of page 1
  • No columns, icons, or graphics