IT Project Coordinator Assistant II

The IT Project Coordinator Assistant II occupies the operational center of a project team — the person who makes sure the schedule is accurate, the meeting notes are captured, the procurement request is actually submitted, and the risk register hasn't sat untouched for three weeks. Project managers rely on coordinators to own the administrative infrastructure of a project so that PMs can focus on stakeholder management and decision-making rather than chasing down action items.

At the II level, the expectation is independent execution with moderate oversight. A coordinator at this level doesn't wait to be told the status report is due Friday — they know it's due Friday, they've already pulled the latest actuals from Jira, and they've flagged a scope change request that needs to appear in the report narrative. That proactive posture is what separates a II from a I.

Day-to-day work varies by project phase. During planning, the coordinator is building out the schedule, setting up the documentation structure in SharePoint or Confluence, and coordinating kickoff logistics. During execution, the job shifts to rhythm maintenance: weekly status reports, action item tracking, meeting facilitation, and budget reconciliation against the project's approved spend. During UAT or go-live windows, coordinators often become the logistics hub — scheduling testers, managing defect spreadsheets, and making sure the right people have access to the right environments at the right time.

The role touches every layer of the project team: developers, infrastructure engineers, business analysts, vendors, and executive sponsors. Coordinators who communicate clearly across those audiences — translating technical status into business language and vice versa — build the kind of cross-functional credibility that accelerates their path to project manager.

Most IT Project Coordinator Assistant II positions sit inside a Project Management Office (PMO) or inside a specific IT delivery team. PMO-based roles tend to have more standardized tooling and process exposure; delivery-team roles tend to have deeper exposure to a specific technology domain, which can be valuable if you're targeting a technical PM track.

Education:

• Bachelor's degree in information technology, business administration, computer science, or a related field (most common requirement)
• Associate degree accepted at some employers when paired with two or more years of relevant coordinator experience
• PMI CAPM certification valued as a substitute for or supplement to formal education requirements

Experience benchmarks:

• 1–3 years of experience in an IT coordinator, administrative, or project support role
• Demonstrated exposure to a full project lifecycle — not just meeting scheduling, but schedule maintenance, documentation management, and budget tracking
• Experience working in an Agile, Waterfall, or hybrid delivery environment; ability to adapt documentation practices accordingly

Certifications (common requirements and preferences):

• CAPM (Certified Associate in Project Management) — preferred at mid-size and enterprise employers
• CompTIA Project+ — lighter-weight alternative recognized at some government and healthcare employers
• Scrum Alliance CSM (Certified ScrumMaster) — relevant for coordinator roles embedded in Agile teams
• ITIL 4 Foundation — valued at organizations running ITSM-heavy IT departments

Technical skills:

• Project scheduling tools: Microsoft Project, Smartsheet, Jira, Azure DevOps Boards
• Documentation platforms: SharePoint, Confluence, Google Workspace
• Reporting: Excel pivot tables, Power BI dashboards for project status (increasingly expected)
• Procurement and finance: basic purchase order tracking, budget vs. actuals reconciliation, invoice processing in SAP or Oracle EBS
• Collaboration: Microsoft Teams, Zoom, Slack — including meeting facilitation and recording management

Soft skills that differentiate candidates:

• Written communication precision — status reports and meeting notes that don't require a PM to edit before distribution
• Comfort navigating ambiguity when project scope is still forming
• Follow-through on action items without repeated reminders from the PM
• Ability to push back constructively when a team member hasn't delivered what the schedule requires

IT project coordination is one of the steadier mid-level roles in technology — organizations run projects continuously regardless of economic cycle, and someone has to keep those projects organized. The Bureau of Labor Statistics projects 7% growth for project management specialists through 2032, slightly above the average for all occupations, and IT-specific project roles track above that rate given continued enterprise technology investment.

The more interesting story is what's happening to the role itself. AI-powered project management tooling is compressing the purely clerical slice of coordinator work — automated meeting transcription, AI-generated status summaries, anomaly detection in project schedules. Tools like Microsoft Copilot for Project, Notion AI, and Atlassian Intelligence are already in production at enterprise organizations. This does not eliminate the coordinator role; it shifts what the role is expected to add. Coordinators who treat documentation maintenance as the entire job will find that part of the role increasingly automated. Coordinators who use freed-up time to develop risk judgment, stakeholder communication, and process improvement skills will advance faster.

Demand is strongest in sectors with large, ongoing IT project portfolios: financial services, healthcare, federal government and defense contracting, and large retail and logistics companies undertaking supply chain technology overhauls. Remote and hybrid coordinator roles are common — most coordination work can be done effectively without being in the same building as the project team, which has broadened the geographic pool of opportunities.

The career ladder is well-defined. From IT Project Coordinator Assistant II, the standard progression runs through IT Project Coordinator (full ownership of smaller projects), then Junior or Associate Project Manager (independent PM accountability with PM or senior PM oversight), then Project Manager. Earning a PMP during the coordinator years is the single biggest accelerant to this path — it signals intent and demonstrates the conceptual knowledge required for independent PM work. Coordinators who pair PMP certification with three to four years of delivery experience are competitive for PM roles paying $95K–$130K in most major markets.

For candidates interested in technical depth, the coordinator path also branches into Scrum Master, Program Analyst, or Business Analyst roles — all of which share significant skill overlap and can be lateral moves rather than strictly linear promotions.

Dear Hiring Manager,

I'm applying for the IT Project Coordinator Assistant II position at [Company]. I've spent the past two years as an IT Project Coordinator at [Organization], supporting a portfolio of infrastructure modernization and software deployment projects across the enterprise IT department.

In my current role I own schedule maintenance in Microsoft Project and Jira for three concurrent projects ranging from $200K to $1.2M in budget, produce weekly status reports that go directly to the VP of IT without PM editing, and run the bi-weekly steering committee meetings including agenda prep, facilitation, and action item tracking. Last quarter I flagged a dependency conflict between our network segmentation project and a parallel ERP upgrade that the PM hadn't caught in the master schedule — resolving it early moved the go-live back two weeks by choice rather than six weeks by incident.

I'm pursuing my CAPM certification and expect to sit for the exam in Q2. I've completed the required 23 hours of PMI education through [Training Provider] and am working through the exam prep material on weekends.

What draws me to this role specifically is [Company]'s PMO structure — working inside a formal PMO with standardized methodology and tooling is the environment where I learn fastest. I've been operating in a lighter-weight setup where process discipline varies by PM, and I want to develop in an organization that takes governance seriously.

I'd welcome the chance to walk through my project tracking samples and discuss what your team needs.

[Your Name]