Project Manager

A project manager is responsible for getting a defined piece of work delivered - a new IT system, a building, a product launch, a change to how a department works - on time, within budget and to the agreed scope. They don't usually do the technical work themselves; they plan it, coordinate the people who do it, chase progress, manage risks and money, and keep sponsors and stakeholders informed. Graduates almost always start as a project support officer, project coordinator or junior/assistant project manager, supporting a more senior PM before running their own workstreams.

Approximate graduate salary

Roughly £25,000-£35,000 to start is a fair approximation for graduate project support and junior PM roles, but this varies a great deal - London, financial services, consultancy and defence sit at the higher end, while charities, the public sector and smaller employers outside the South East often start lower. Treat these as rough bands, not fixed figures.

What you'd actually do

Running or attending stand-ups and progress meetings with the delivery team, then chasing the actions that came out of them - a lot of the job is following up on things other people owe you
Updating the plan: adjusting dates, dependencies and milestones in a scheduling tool (Microsoft Project, Smartsheet, Jira, Asana or often just a heavily-used spreadsheet) when reality diverges from the plan
Maintaining the RAID log - risks, assumptions, issues and dependencies - which means actively asking people what could go wrong rather than waiting to be told
Writing a progress report or steering group pack: what's on track, what's slipped, what decision the sponsor needs to make, usually in a standard template
Tracking spend against budget - checking invoices, forecasting what's left, flagging when a supplier or contractor is going to overrun
Handling a change request: someone wants something added or altered, and you work out the cost and time impact and get it formally approved or rejected
Writing and circulating meeting minutes, decision records and stakeholder updates - the documentation trail matters more than graduates expect, particularly in the public sector and regulated industries

How graduates get in

Graduate schemes with an explicit project management or 'change' stream - common in banking, insurance, engineering, construction, defence, energy, utilities, the NHS and the Civil Service. These usually rotate you through a few projects and fund a professional qualification.
Consulting graduate schemes (technology, management or engineering consultancies), where you're placed on client projects as a junior PM or business analyst. Very common entry point, though the job title may be 'analyst' or 'consultant' rather than PM.
Direct entry as a project support officer, project coordinator or PMO analyst - PMO means Project Management Office, the central function that sets standards and tracks the whole portfolio. These roles are advertised year-round rather than in an autumn recruitment cycle and are a very realistic route in.
Moving sideways after a couple of years in a technical or operational role - a developer, engineer, nurse or analyst who shows they're good at organising work gets pulled into delivery. This is extremely common and arguably the most typical route into senior PM roles in technical industries.
Placement years and summer internships in engineering, construction and IT often include project support work, and converting an internship is a strong route.
Apprenticeship routes exist (including degree apprenticeships in project management), so some of your colleagues will have come in without a traditional degree - worth knowing, though less relevant if you already have one.

What employers ask for

Degree subject usually doesn't matter for general business or change roles - employers recruit widely. It matters a lot in engineering, construction and pharma, where you're expected to understand what the team is actually building, so a relevant engineering, construction or science degree is often required.
Typical grade expectations are a 2:1 for structured graduate schemes, though a 2:2 is accepted more often here than in some professions, especially for direct-entry project support roles where evidence of organising things counts for more.
Evidence you've coordinated something real - a society, a sports club, an events committee, a placement project, a part-time job where you ran a rota. Interviewers dig into this hard because there's no other proxy for the skill.
A professional qualification is expected over time but rarely before you start. The common ones in the UK are APM (Association for Project Management) qualifications such as the PFQ and PMQ, PRINCE2 (a structured method widely used in the public sector and by suppliers to government), and agile certifications such as Scrum Master. Many employers pay for these in your first year or two.
Comfort with spreadsheets and scheduling software - you will live in them. Some employers now test this at assessment centre.
Security clearance is required for defence, nuclear and some government work, which normally means UK residency for a set period. Worth checking before applying.

Skills that matter

Chasing people without annoying them

You have deadlines but usually no authority over the people doing the work, so getting updates and decisions out of busy colleagues through persistence and goodwill is the core daily skill.

Writing clearly and briefly for senior readers

A sponsor will read half a page before a steering meeting, so you need to compress a messy fortnight into 'here's the problem, here's the option I recommend, here's what I need from you'.

Planning and dependency thinking

You need to see that task C can't start until B finishes and B needs a supplier who takes six weeks - spotting that in advance is what separates a plan from a wish list.

Numeracy and budget tracking

You'll forecast spend, check whether an invoice matches what was delivered, and quantify the cost impact of a change request.

Staying calm and organised when things slip

Projects go wrong routinely; the value you add is a clear-headed reforecast and an honest escalation rather than optimism that hides the problem until it's unfixable.

Enough technical literacy for your sector

You don't need to write the code or design the structure, but you must understand the work well enough to know when an estimate is nonsense or a risk is being downplayed.

Where it leads

Project support officer / project coordinator / PMO analyst - supporting one or several projects, owning the plan, the logs and the reporting rather than the outcome. Typically the first year or two.
Junior or assistant project manager - running a discrete workstream or a small project end to end, with a senior PM accountable above you.
Project manager - owning delivery of a whole project including budget, supplier relationships and the sponsor relationship. Reaching this point commonly takes a few years but varies widely by sector; it's faster in fast-moving digital and consulting environments and slower in construction and infrastructure, where projects run for years and you need to have seen a full lifecycle.
Senior project manager, then programme manager (running a set of related projects) or portfolio manager (overseeing the whole set of change work in an organisation). Alternatively PMO lead, setting delivery standards across the business.
Common exits: operations management, general management, product management, consultancy, or contracting - experienced PMs, particularly in construction, energy and IT, often move to day-rate contract work, which pays more but with no job security.

What people get wrong

“You need to be the technical expert on the team.”

In most sectors you're deliberately not the expert - your job is to make space for the experts to work and to translate between them and the people paying. Knowing enough to ask good questions matters far more than being able to do the work yourself. The exception is engineering and construction, where a relevant technical background is genuinely expected.

“It's a leadership role, so you tell people what to do.”

Junior PMs typically have responsibility without authority - the team often reports to someone else entirely, and in consultancy or matrix organisations you're coordinating people who outrank you. Influence, persistence and relationship-building do the work that a line-management hierarchy would otherwise do.

“Agile has replaced traditional project management, so PRINCE2 and Gantt charts are obsolete.”

Both are alive and widely used, often in the same organisation. Software teams tend to run agile with sprints and a Scrum Master or delivery manager; construction, infrastructure, defence and much of government still run stage-gated plans with fixed milestones. Plenty of organisations run a hybrid and expect you to be comfortable with both.

“The day-to-day is strategic planning and big-picture thinking.”

The early years are heavily administrative - minutes, trackers, templates, chasing timesheets, reformatting slides for a steering group. The judgement-heavy work comes later, and how much administration you do depends enormously on whether the employer has a well-resourced PMO or expects PMs to do everything themselves.

Where this varies

The job varies more by sector than almost any other graduate role sharing a single title. In construction and infrastructure a project is a physical asset, timescales run to years, you may be site-based and the work is document- and contract-heavy. In IT and digital you'll likely be in an agile team on two-week sprints and the title may be 'delivery manager' or 'scrum master' instead. In banking, insurance and large corporates it's usually 'change management' - reorganising processes, systems and teams - and the challenge is stakeholder politics more than technical delivery. In the NHS and Civil Service, PRINCE2 and formal governance dominate and business cases are a big part of the work. Consultancies place you on client sites with frequent travel and short assignments. Charities and smaller organisations often have no PMO at all, so you do the strategy and the admin and the delivery yourself. Choose the sector before you choose the title.

General guidance about the role across the UK market, not about any specific employer. Entry routes and requirements vary — always check the individual job advert.