Jake’s Tech Labs
IT Resume Workshop

Step 4: Experience → Bullet Points

This is where resumes win or lose. Your bullets should prove impact with clear scope, measurable results, and the tech you used — not read like a job description.

Principle

Every bullet should answer: what changed because you were there?

The bullet formula (copy/paste)

Use this pattern to write bullets that are defensible and easy to scan:

Impact + Scope + Tech + Proof

Example starter: “Reduced ___ by ___% for ___ users by implementing ___ using ___.”

  • Impact: faster, safer, cheaper, fewer outages, fewer tickets
  • Scope: users, endpoints, locations, servers, environments
  • Tech: tools/services you used (Azure, AD, Intune, PowerShell, etc.)
  • Proof: numbers, time saved, reliability gains, measurable outcomes

Before → After examples

Example 1

Before (weak)

Managed Active Directory users and groups.

After (strong)

Reduced account provisioning time by ~60% by standardizing AD group-based access and automating user onboarding with PowerShell across 150+ users.

Example 2

Before (weak)

Provided IT support and resolved tickets.

After (strong)

Resolved an average of 35–50 tickets/week while maintaining 95%+ SLA compliance, improving first-contact resolution by creating internal troubleshooting runbooks for common issues.

Example 3

Before (weak)

Worked with Microsoft 365 and Azure.

After (strong)

Hardened M365 tenant security by rolling out MFA and Conditional Access policies for 200+ users, reducing risky sign-in alerts and improving audit readiness.

Note

If you don’t have perfect metrics, use honest estimates (ranges like “~30–50 tickets/week”) and keep them defensible.

What to include (and what to cut)

Include

  • Outcomes (time saved, outages reduced, risk lowered)
  • Scale (users/endpoints/servers/sites)
  • Automation and process improvements
  • Security and reliability improvements
  • High-signal projects you owned end-to-end

Cut

  • Generic responsibilities (“responsible for…”)
  • Tool lists inside bullets (save tools for Skills)
  • Fluff adjectives (“hardworking,” “detail-oriented”)
  • Anything you can’t explain in an interview
  • Overly long bullets (keep most to 1–2 lines)

Action

  1. Pick one job from your Experience section.
  2. Write 6 bullets using the formula above.
  3. Underline (mentally) the metric in each bullet — add one if it’s missing.
  4. Cut any bullet that doesn’t show impact or that you can’t defend.
Site feedback

Help improve Jake’s Tech Labs

Report an issue, suggest an improvement, or tell us what you’d like to learn and practice next.