Engineering Project Manager Interview Questions UK: 8 Real Questions and What Interviewers Want

Most Engineering Project Manager interviews in the UK follow a pattern, and knowing it beats guessing. Below are eight questions from our bank of 16, each with a note on what the interviewer is really after.

Eight Engineering Project Manager interview questions, and what the interviewer is thinking

1. How do you build and manage a project programme, and how do you identify the critical path?

Why they ask: Programme control is the core skill of an engineering project manager, and they want to hear it explained practically.

2. What are the duties of the client, principal designer and principal contractor under CDM 2015, and what is your role as project manager?

Why they ask: Health and safety law is central to engineering projects, and they want to be sure you will not put the company at risk.

3. How do early warning notices and compensation events work under NEC4, and how do you manage them as a project manager?

Why they ask: Many UK engineering contracts use NEC, and mishandling notices can be very costly.

4. How do you manage risk on an engineering project, and how do you decide how much contingency to hold?

Why they ask: They want to see a structured approach rather than an ad hoc list of worries.

5. How do you control scope and handle change requests during an engineering project?

Why they ask: Scope creep is one of the biggest causes of overrun, and they want to know you can manage it firmly but fairly.

6. A critical supplier tells you their delivery of a key component will be six weeks late. What do you do?

Why they ask: They want to see calm, structured problem solving on a common project risk.

7. Tell me about a time you delivered an engineering project on time and on budget despite significant challenges.

Why they ask: They want evidence of delivery and the way you handle obstacles.

8. Why did you choose project management within engineering rather than staying in a purely technical role?

Why they ask: They are checking motivation and whether you understand the change in focus the role requires.

A sample answer to question 1

How do you build and manage a project programme, and how do you identify the critical path?

I start with a work breakdown structure agreed with the discipline leads, so every deliverable and owner is visible. I then estimate durations with the people who will do the work, link tasks with logical dependencies, and build the programme in Primavera P6 or MS Project. The critical path is the longest chain of dependent activities, so any slip on it moves the completion date. I also track near-critical paths, because those can become critical quickly, and I keep a close eye on total float. I use resource levelling to avoid overloading key engineers, and I build in realistic procurement lead times, which are often what hurt engineering projects, for example switchgear or castings. I baseline the programme once the client approves, then update it weekly with progress, report variance and forecast, and run what-if scenarios when risks materialise. If something slips, I look to recover time through resequencing or parallel working before I accept a delay, and I report honestly.

Common mistake to avoid: Ignoring procurement lead times; building programmes without input from engineers

Want the rest?

Full model answers, key points and common mistakes for all 16 questions are on the Engineering Project Manager interview questions page. The first five are free, no sign-up needed.