Project Engineer Interview Questions UK: 8 Real Questions and What Interviewers Want

Most Project Engineer 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 Project Engineer interview questions, and what the interviewer is thinking

1. How do you manage technical queries and RFIs between site, the design team and suppliers, and why does it matter?

Why they ask: Handling queries well keeps work moving and creates a record, so they want to see a disciplined process.

2. How would you review a contractor's risk assessment and method statement, and what would make you reject it?

Why they ask: RAMS review is a daily duty for project engineers and has direct safety consequences.

3. What is an inspection and test plan, and how do you use one to make sure work is built to the specification?

Why they ask: They want to check you understand quality assurance on site or in the factory.

4. How do you review a supplier's technical submission or drawings against the specification before approving it?

Why they ask: This is a core task where mistakes can lead to wrong equipment being manufactured.

5. How do you track project costs and manage variations at a package level, and what records do you keep?

Why they ask: They want to ensure you understand commercial control at the level a project engineer works.

6. During a site visit you find that installed pipework does not match the approved drawing, and the contractor says the change was made to avoid a clash. What do you do?

Why they ask: They want to see you balancing quality control, practicality and fair process.

7. Tell me about a time you resolved a technical problem on site that was holding up the programme.

Why they ask: They want evidence of practical problem solving and coordination under real pressure.

8. What does a typical day as a project engineer involve, and what do you enjoy about the role?

Why they ask: They want to check your expectations are realistic and you understand the breadth of the work.

A sample answer to question 1

How do you manage technical queries and RFIs between site, the design team and suppliers, and why does it matter?

I log every request for information in a register with a unique number, the date raised, the originator, the drawing or specification reference, who needs to answer and the required response date. Before sending, I check whether the answer is already in the documents, because a vague or duplicate query wastes the designer's time. I write it clearly, with a sketch or photo where helpful, and describe the impact on the programme if it is not answered. I chase those at risk of holding up work, and prioritise by the critical path. When an answer comes back, I check that it does not change scope or cost, because if it does it needs to go through the change process, not just be passed on to site. I then issue the response to everyone affected and update any drawings. I review the register weekly, looking at ageing queries and trends, because repeated queries on one area often signal a design problem. The record also protects us in any later dispute.

Common mistake to avoid: Passing on answers that change scope; letting queries sit unchased

Want the rest?

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