The specific signals an experienced it support specialist hiring panel grades on during the eight-second scan.

• Summary names the user count and ticket volume

  'Supports 380 employees with ~120 weekly tickets' beats 'IT support specialist.' Scope is what hiring managers scan for.

• Tier handled (T1, T2, T3)

  Tier signal disambiguates helpdesk-only from full-stack IT. Name the tier explicitly.

• MDM + identity stack named

  Jamf, Intune, Kandji, Workspace ONE, Okta, JumpCloud, Google Workspace. Specific products parse as tokens.

• Resolution time (MTTR for tickets)

  First-touch resolution rate, mean time to ticket resolution, escalation rate. Operational metrics.

• Runbook / automation authorship

  Wiki articles authored, KB adoption, repetitive tasks automated. Senior IT signal.

• One certification (helpful at entry-mid level)

  CompTIA A+, Network+, Security+, Apple Certified Support Professional, Microsoft 365 Certified. Certifications matter more in IT than in software engineering.

1. 1

   Open with tier + user count + ticket volume

   A senior IT-support summary names the tier and the scope: 'T2/T3 IT Support Specialist at a Series C SaaS; supports 380 employees with ~120 weekly tickets on Jamf + Intune + Okta.' Mid: 'T1/T2 helpdesk at a 180-person org.' Entry: 'Campus IT support at a major university; handled 1,200 tickets/year across the engineering school.'

   Lead with the structure. IT hiring panels read for environment scale first.

2. 2

   Quantify with FTR + resolution + escalation

   First-touch resolution rate (FTR), mean ticket resolution time, escalation rate, ticket volume per week/month, SLA compliance. These are the operational metrics IT hiring managers grade on.

3. 3

   Name the MDM + identity stack

   Jamf / Intune / Kandji / Workspace ONE / Mosyle for MDM. Okta / Entra / Google Workspace / JumpCloud for identity. CrowdStrike / SentinelOne / Microsoft Defender for endpoint security.

   Named tools parse better than 'managed endpoints.'

4. 4

   Surface automation work

   Automation is the senior IT-support signal. The pattern that works: • Name the automation tools (PowerShell, AppleScript, Python, Jamf API, Okta Workflows). • Name the workflows automated (onboarding, offboarding, license reclamation, password resets, MFA enrollment). • Quantify engineer-hours saved per week or month.

   Generic 'automated routine tasks' is filler; the named workflows and hour-saved outcome are the senior signals.

5. 5

   Close with certifications + runbooks

   List current certifications with year. CompTIA A+ for entry-level, Apple Certified or Microsoft 365 Certified for mid, RHCSA or ITIL 4 for senior. Cite KB / runbook authorship counts and adoption.

Each follows the [verb] [object] [number] structure hiring managers grade against. Copy them as a starting point, swap in your own numbers, and read the annotation to understand why each one works.

• Resolution

  Owned T2 escalations from helpdesk; first-touch resolution rate climbed from 62% to 78% across 2024 after I authored 38 new KB articles + ran 4 monthly L1 training sessions.

  Why it works: Names the tier, FTR with before/after, KB count, training cadence.

• MDM

  Own the Jamf Pro instance for 280 macOS endpoints; configured 14 smart groups + 22 configuration profiles; baseline-compliance enforcement reached 98% across the fleet (was 64% on entry).

  Why it works: Names Jamf Pro, endpoint count, configuration scope, compliance outcome with absolute numbers.

• Automation

  Automated 38 repetitive tasks through 2024 via Jamf API + Okta Workflows + PowerShell scripts; saved ~14 IT engineer-hours per week on onboarding/offboarding + license-reclamation workflows.

  Why it works: Automation count, tool stack, engineer-hours saved per week.

• Onboarding

  Built the zero-touch onboarding flow (Okta provisioning → Jamf DEP enrollment → Slack auto-add → Confluence access); new-hire time-to-productive-laptop fell from 4 days to 8 hours.

  Why it works: Four-tool chain, new-hire metric, and a strong before/after.

• Identity

  Migrated company SSO from G Suite primary to Okta primary (with Google Workspace as IdP-second); 380 users moved over 6 weeks with zero outage windows; MFA enforcement reached 100%.

  Why it works: Names the migration (source/destination), user count, duration, and MFA outcome.

• Resolution

  Reduced mean ticket resolution time from 8.4 hours to 4.2 hours through ticket-routing improvements in Jira Service Management + the L1 training program + 38 new self-service KB articles.

  Why it works: Names the metric, the before/after, and three specific interventions.

• Hardware

  Built the hardware-lifecycle automation (Jamf inventory + Zendesk webhook + Apple Business Manager pre-provisioning); 14 hours/month saved on laptop refresh cycles; zero device-loss incidents over 12 months.

  Why it works: Three-tool chain, time savings, and a zero-incident window.

• Documentation

  Authored 38 KB articles in Confluence covering the top-volume ticket categories (VPN, MFA, password reset, printer setup, SSO); KB adoption reduced ticket volume in those categories by 42%.

  Why it works: KB count, categories listed (proves real coverage), and ticket-volume deflection outcome.

• Security

  Led the endpoint-security rollout (CrowdStrike Falcon Insight + Falcon Identity Protection) across 280 endpoints; zero EDR-detected compromises through 2024 across the rollout period.

  Why it works: Names the EDR products, endpoint scope, and a sustained zero-compromise window.

• Mentorship

  Mentored 2 junior IT support specialists into T1 → T2 progression; both shipped sole-owner KB + automation work within 6 months.

  Why it works: Mentorship pipeline with deliverable per mentee.

• FinOps

  Reduced SaaS-license waste by $84k/yr through quarterly reclamation runs (Okta-app + Vendr usage data); 38 unused seats + 14 expired contracts surfaced and reclaimed.

  Why it works: Names the absolute dollar savings, the cadence, and the two automation data sources.

• Entry-level

  Built the campus-IT helpdesk runbook as a senior CS student (Notion-based, 24 articles); reduced peak finals-week ticket queue from 380 open to under 90 over the semester.

  Why it works: For entry-level IT, this kind of credible-scope contribution is high-leverage.

Same intent, two phrasings. Read why the right column lands on the keep-pile and the wrong column doesn't.

Patterns our writers see most often when reviewing it support specialist resumes — each one disqualifies candidates faster than weak experience does.

• Mistake

  Generic 'IT support specialist' without tier or user count.

  Fix

  Name T1/T2/T3 and the user count. Hiring managers read for scope first.

• Mistake

  Vague MDM claim. 'Managed devices.'

  Fix

  Name Jamf / Intune / Kandji / Workspace ONE by exact product.

• Mistake

  No FTR or mean-resolution metric.

  Fix

  FTR is the IT-support quality metric. Surface it with before/after.

• Mistake

  No automation contributions.

  Fix

  Senior IT-support folks automate. Name PowerShell / Python / Jamf API / Okta Workflows work — even one automation surfaces the senior signal.

• Mistake

  Listing certifications without years.

  Fix

  Certifications need years. List 2-3 current ones; cut lapsed ones.

• Mistake

  Soft-skills cloud. 'Strong communication, problem solver, team player.'

  Fix

  Cut it. IT support work demonstrates these through ticket volume + escalation handling — the resume should show, not tell.

• Mistake

  Two-page resume below 8 years experience.

  Fix

  One page. IT hiring moves fast through helpdesk and sysadmin roles.

• Mistake

  Listing every operating system + every software product touched.

  Fix

  Weight skills toward depth in the stack the JD targets. Helpdesk JDs distinguish Mac-shop from Windows-shop hires.

Strong verbs lead strong bullets. Replace generic openers (worked on, helped with, was responsible for) with the specific verb that matches what you actually did.

ATS pipelines weight your Skills section as a structured list. Include 15-25 of the items below if they match your experience — not soft skills.