PMP — Project Management Professional

PMP is a globally recognised project management certification from the Project Management Institute (PMI). Based on the PMBOK Guide, it covers the full project lifecycle: initiating, planning, executing, monitoring & controlling, and closing, with knowledge areas spanning scope, schedule, cost, quality, risk, and stakeholder management.

Why companies use it

·PMP-certified project managers apply standardised practices that reduce project risk and cost overruns
·A recognised credential that allows organisations to benchmark project management competence
·The PMP framework gives language and tools for managing scope creep, schedule risk, and stakeholder alignment
·Required or preferred for project manager roles in many large engineering organisations and defence contractors

What hiring managers look for

·PMP certification demonstrates commitment to project management as a discipline and validates structured thinking
·Understanding earned value management (EVM) — SPI, CPI — shows ability to report project health objectively
·Candidates with PMP understand the importance of project charters, stakeholder registers, and risk registers as living documents
·In large engineering programmes (semiconductor, aerospace), formal project management is a necessity, not an option

Typical interview questions

What are the five process groups in the PMBOK framework?

How do you handle scope creep in a project where the customer keeps adding requirements?

Explain earned value management. If your SPI is 0.8 and CPI is 1.1, what does this tell you?

How do you identify and manage project risks? What is the difference between a risk and an issue?

Describe the most complex project you have managed. How did you keep stakeholders aligned?

Common mistakes

·Creating a project plan but not maintaining it — a project plan that is not updated in real time is worse than no plan
·Not defining scope formally (Work Breakdown Structure) — without it, "done" is ambiguous and scope creep is uncontrollable
·Ignoring the critical path — schedule risk is concentrated on the critical path; monitoring non-critical activities first is a waste of attention
·Closing risks as "resolved" when they have merely not materialised yet
·Treating stakeholder management as a communication formality rather than an active relationship-building activity

Real engineering example

A programme manager overseeing an EUV lithography module upgrade applied EVM to a 14-month project. At month 6, the CPI was 0.88 (over budget) and SPI was 0.92 (behind schedule). Rather than waiting for the quarterly review, the EVM data triggered an immediate resource review. Three tasks on the critical path were identified as under-resourced; adding a specialist contractor recovered 3 weeks of schedule and brought CPI back to 0.97 by month 10.

Topics covered

PMPPMIPMBOKproject managementEVMschedulescoperisk

Related interview guides

Project Leader High Tech →Systems Engineer →Technical Product Manager →Manufacturing Engineer →