IT Coordinator II

An IT Coordinator II is the operational center of gravity for a mid-size IT department. They're not writing infrastructure architecture documents or leading enterprise migrations, but they're the person who makes sure the machines are on the desks, the accounts work on day one, the ticket queue doesn't age out, and the vendor renewal doesn't slip through the cracks. In organizations without a dedicated IT operations team, they often carry all of that simultaneously.

A typical week involves resolving a mix of escalated support tickets — the kind that stumped L1 or require access to admin-level tooling — while also running down a hardware order that's two weeks late, updating the asset database after last week's equipment refresh, and building an onboarding checklist for a new department the company just hired into. There's project coordination work layered in: scheduling maintenance windows, tracking deliverables from a managed service vendor, and making sure the change request for the firewall rule update has the right sign-offs before it goes live.

The role requires enough technical fluency to configure a workstation, read a network diagram, and speak credibly with a systems engineer — but the job isn't purely technical. A large portion of daily effort goes toward process: updating documentation that's six months out of date, writing a clear incident summary that the CTO can read without a glossary, or mediating between a frustrated business user and a slow-moving vendor.

In organizations that have adopted ITSM platforms like ServiceNow or Jira Service Management, the IT Coordinator II often functions as the queue owner — not just resolving tickets but monitoring SLA health across the board, identifying recurring incident patterns, and escalating structural problems to engineers. That operational lens is what separates the role from a senior technician.

The profile that succeeds here is someone who solves problems quickly without cutting safety corners, writes documentation that actually gets used, and treats vendor calls as a negotiation rather than a conversation. Procedural discipline matters — particularly around change management and access controls — because the mistakes at this level are the ones that show up in audit findings.

Education:

• Associate or bachelor's degree in information technology, computer science, or a related field (bachelor's preferred at larger organizations)
• Equivalent experience accepted by most employers — 3–4 years of progressive IT support experience substitutes for a degree in practice

Certifications (listed by priority):

• CompTIA A+ and Network+ — baseline expectations; candidates without these should be actively pursuing them
• CompTIA Security+ — increasingly a hard requirement in government, healthcare, and financial services environments
• ITIL Foundation — strongly valued wherever the role involves SLA management or formal change control
• Microsoft MS-900, MD-102, or AZ-900 — relevant for organizations running Microsoft 365 or Azure
• ServiceNow System Administrator (CSA) for environments built on that platform

Experience benchmarks:

• 2–4 years in an IT support or systems technician role, with demonstrated progression beyond L1 ticket handling
• Hands-on experience with Active Directory or Entra ID: creating users, managing groups, applying GPOs
• Familiarity with endpoint management tools — Microsoft Intune, Jamf, or SCCM for device provisioning and policy
• Exposure to procurement workflows: requesting quotes, processing purchase orders, tracking asset delivery

Technical skills that matter:

• Microsoft 365 administration: Exchange Online, Teams, SharePoint permissions, licensing management
• Networking fundamentals: DHCP, DNS, VLANs, VPN configuration — enough to diagnose connectivity issues without a senior engineer on the call
• Ticketing platform proficiency: ServiceNow, Jira Service Management, Freshservice, or equivalent
• Basic PowerShell for user account management and reporting tasks
• Remote support tools: TeamViewer, BeyondTrust, ConnectWise Control

What hiring managers actually screen for:

• Evidence of documentation habits — a candidate who can show a runbook or SOP they wrote
• SLA accountability — someone who has owned a queue, not just worked in one
• Vendor interaction experience — anyone who has managed a support contract or escalated with a hardware OEM

Demand for IT Coordinator roles is steady and broadly distributed across industries. Every organization above roughly 75 employees that hasn't fully outsourced its IT function needs someone performing this work — healthcare systems, law firms, manufacturers, school districts, and SaaS companies all hire at this level. That breadth creates resilience: when one sector slows hiring, others are typically active.

The BLS projects 6% growth in computer and information systems occupations through 2032, roughly in line with the overall economy. For IT coordinators specifically, the driver isn't net-new role creation so much as turnover and organizational growth. Organizations that previously ran on a single IT generalist hire a coordinator when the workload exceeds one person; organizations that had a coordinator hire a second when the first can't keep up with ticket volume and project demands simultaneously.

The automation trend is real and worth understanding clearly. Routine ticket triage, password resets, and standard equipment provisioning are all being handled with less human time than they were five years ago — AI-assisted ticketing, zero-touch enrollment for devices, and self-service portals have taken over the high-volume, low-complexity work that previously occupied L1 and lower L2 staff. The IT Coordinator II role is not disappearing, but it is evolving: the people who will thrive are those who manage and improve the automated workflows rather than simply execute manual tasks.

Geographically, remote and hybrid IT coordinator roles have become more common than in any prior period, particularly at organizations where the IT function serves a distributed workforce. That's expanded the candidate pool but also the job market — an IT Coordinator II in a lower cost-of-living region can now compete for roles at companies headquartered in higher-paying markets.

For someone in this role today with a clear development plan, the path is well-lit. Three to five years of demonstrated SLA ownership, vendor management, and infrastructure project support positions a candidate for systems administrator, IT operations manager, or IT project coordinator — all of which pay $85K–$130K at the mid-career level. The candidates who stall are those who stay in reactive mode, clearing tickets without building the process and documentation foundation that demonstrates readiness for the next level.

Dear Hiring Manager,

I'm applying for the IT Coordinator II position at [Company]. I've been working in IT support at [Current Employer] for three years, most recently as the primary L2 escalation contact for a 220-person organization running a Microsoft 365 environment with a mixed Windows and macOS fleet.

My day-to-day work covers the range I'd expect in this role: resolving escalated tickets that come from our MSP's L1 team, managing our hardware procurement cycle through a CDW account, and administering user accounts and licensing in Entra ID. Last quarter I took ownership of our asset database after noticing that roughly 30% of records hadn't been updated since 2021. I rebuilt the schema in our ITSM platform, reconciled physical inventory against what was in the system, and got it to a state where the data is actually usable for budget planning.

On the security side, I coordinated our rollout of Defender for Endpoint across all managed devices — scheduling the deployment in Intune, writing the communication to end users, and handling the exceptions for the handful of legacy machines that needed manual intervention. Nothing went to the change advisory board without documentation I wrote.

I hold CompTIA A+, Network+, and Security+, and I'm currently working through the ITIL Foundation material ahead of a scheduled exam next month.

I'm drawn to this role because of [Company]'s scale and the exposure to enterprise infrastructure projects that aren't available at my current organization. I'd welcome the chance to talk through how my background fits what you need.

[Your Name]