IT Project, Business Analysis & Communication · Project Coordination / Business Analysis

IT Project Coordinator

The person who keeps tech projects moving — schedules, scope, stakeholders, and the notes everyone actually reads.

IT Project CoordinatorJunior Business AnalystProject AdministratorScrum Team CoordinatorPMO Analyst
$100,750 median · +6% for project specialists; the analyst track (median $103,790) is growing faster at +9%
~$59,830 to start — coordinator and junior BA roles sit at the bottom of the range. U.S. BLS figures for Project Management Specialists (13-1082) and Computer Systems Analysts (15-1211); a median is the midpoint of everyone employed, so entry pay runs well below it. Verify against the live BLS pages before deciding.
Is this you? Take the free assessment

What you actually do

You keep IT projects on track without writing the code yourself. Day to day you coordinate schedules and dependencies, gather and document what the business actually needs, translate between technical teams and everyone else, chase down blockers, and run the meetings — standups, planning, retros — that keep work visible. It's one of the few genuine non-coder first roles in tech: employers hire coordinators and junior business analysts for organization and communication, then teach them the domain.

  • Run the morning standup and capture blockers before they become slipped deadlines
  • Sit with a business stakeholder to pin down what 'the report should be faster' actually means, then write it up as requirements
  • Update the project plan after a vendor delay and walk the team through what moves
  • Translate a developer's technical constraint into plain language for the steering committee
  • Chase three people for the sign-offs the project can't proceed without

What the work feels like

CommunicationVery high
Technical depthMedium
TroubleshootingMedium
Customer contactHigh
On-callLow
Remote-friendlyHigh

This fits you if…

  • You're naturally organized and people trust you to follow through
  • You like talking to people all day and turning conversations into structure
  • You want into tech without making coding your job

Less ideal if…

  • You want deep, heads-down technical work with minimal meetings
  • Chasing people for updates would drain you
  • You need clear authority to feel effective — this role runs on influence
The honest downsides: You carry responsibility for the deadline without authority over the people who can miss it. Herding stakeholders, absorbing scope creep, and translating for both sides all day is genuinely tiring — and when a project slips, the coordinator is the visible face of it. Early roles can be heavy on note-taking and chasing before you earn real ownership.

Skills to build

Written and verbal communication Foundational The core tool of the job — clear notes, clear asks, clear status.
Organization & scheduling Foundational Dependencies, milestones, and who's waiting on whom.
Requirements elicitation & documentation Working Asking the questions that turn a vague wish into something a team can build.
Agile & waterfall fundamentals Working Enough to run ceremonies and know which method fits which project.
Stakeholder management Working
Tooling fluency (task trackers, spreadsheets, docs) Working
Data literacy (SQL basics, reading dashboards) Emerging What separates coordinators from analysts — and raises your ceiling.
Jira / Azure DevOpsConfluence / SharePointMicrosoft 365 / Google WorkspaceExcel / Google SheetsMiro / VisioSmartsheet / MS ProjectSlack / Teams

Your roadmap

An ordered path from beginner to employable. Certifications are optional checkpoints, not the point — skills and a portfolio are.

  1. 1
    Learn the vocabulary

    Agile, Scrum, and waterfall basics plus the tooling — free via Scrum.org's Scrum Guide, Atlassian's agile guides, and a Jira free tier. Learn to build a real project plan in a spreadsheet.

  2. 2
    Build coordination evidence

    Coordinate something real: a volunteer project, a community event, a process fix at your current job. Document the requirements, the plan, the risks, and the outcome — that write-up is your portfolio.

  3. 3
    Add an entry credential

    CAPM, PSM I, or ITIL 4 Foundation — pick the one matching the jobs you're seeing locally. These validate the vocabulary; your portfolio proves you can use it.

    Study guide: PMI CAPM →
  4. 4
    Pick your lane

    Project management (toward PMP once you have the experience it requires), business analysis (add SQL and data skills), or platform ownership (become the Jira/M365 person). Each is a real career, not just a rung.

Certifications for this path

A facet of the path, not the path itself — skills and a portfolio come first.

Honest priority check: this is a portfolio-first path — evidence you've coordinated real work beats any credential. Pick ONE of these to match the jobs you're actually seeing locally; PMP is not entry-level (it requires documented project experience first).

Try it this weekend

Do the actual job on a real-life project — a move, an event, a trip: elicit what people need, structure a plan with milestones and risks in a spreadsheet, and get someone to agree to it.

Free 60–90 minutes Fully local — any spreadsheet you already have; nothing installed or transmitted.

Related paths

Not sure this is the one?

Take the free 10-minute assessment and see your three strongest IT paths.

Take the IT Career Navigator →