Photo: Petbluzz (CC BY-SA 4.0)
Job description
Day to day means conferring with developers, engineers, and business stakeholders to resolve problems, tracking milestones and deliverables against the project plan, and directly gathering customer needs through conversations and surveys. The desk-based, team-driven work runs at a fast, deadline-pressured pace, and because IT projects sit at the intersection of business goals and technical execution, managers often mediate frustration from both sides while making independent calls about scope and sequencing. With a bachelor's degree as the typical entry point and pay ranging widely (about $56K to $188K), this is a common path for developers or analysts who want to move into leadership without leaving tech behind.
Pros
- High pay ceiling near $188k with much faster than average growth (8.2%)
- Large national demand pool (31,300 jobs) across nearly every industry that uses technology
- Central, high-visibility role bridging technical teams and business stakeholders
Cons
- Above-average hours, often exceeding a standard 40-hour week to keep projects on schedule
- Constant pressure to hit budget, scope, and deadline targets all at once
- Regularly manages frustrated stakeholders when timelines slip or requirements change
A typical day
The 9am standup surfaces the day's truth: the payments integration is two days behind because a vendor API doesn't match its documentation. The PM's morning is spent working that problem — a call with the vendor, a scope decision escalated to the sponsor with options instead of complaints, and a revised timeline nobody loves but everyone can live with. Midday is stakeholder translation: turning engineering reality into an executive status report that's honest without being alarmist, then turning executive urgency back into achievable sprint priorities. The afternoon holds a risk review (what breaks if the lead developer wins the lottery?), a budget reconciliation, and a testing-phase kickoff. The PM writes no code but touches everything; the job is making forty people's work land as one coherent thing, on a date, for a number.
Tasks at the job
- Manage project execution to ensure adherence to budget, schedule, and scope.
- Confer with project personnel to identify and resolve problems.
- Monitor or track project milestones and deliverables.
- Submit project deliverables, ensuring adherence to quality standards.
- Assess current or future customer needs and priorities by communicating directly with customers, conducting surveys, or other methods.
- Direct or coordinate activities of project personnel.
Workplace & working conditions
Work happens indoors in a climate-controlled setting, and most of the day is spent sitting at a desk.
The pace is often fast, with real time pressure to meet deadlines, and you're expected to exercise significant independent judgment day to day. The work is highly structured, following set procedures. You'll regularly deal with frustrated or upset people as part of the job, and almost all of the work is done as part of a team.
Education necessary or common
Bachelor's degree
Common college majors
Licenses & certifications
- CAPM — the entry-level PMI credential
- PMP — the field's flagship (experience-gated)
- Certified ScrumMaster (CSM)
- CompTIA Project+
Career path
Related fields
Courses to take
- AP Computer Science Principles — you must speak the builders' language
- Business or Intro to Business — budgets, stakeholders, and value
- AP English Language — status reports and negotiations run on clarity
- AP Statistics — estimation and risk are probabilistic
- Public Speaking — meetings are the medium of the job
Clubs, activities & competitions
- FBLA or DECA — project-based business competition
- FIRST Robotics — real project management: deadline, budget, team, demo day
- Organize a school event start to finish — a dance, a tournament, a fundraiser
- Student government — stakeholder management practice
First steps you can take now
- Plan and run one real event with a written timeline, budget, and task list — then write down what slipped and why
- Learn a project tool (Trello or any kanban board) and manage your own semester with it
- Read a plain-English intro to Agile and waterfall — the field's two grammars
- Interview a project manager about what actually goes wrong on projects
