Twelve questions to expect in a construction interview

Interviews in construction tend to be concrete. You will be asked about specific projects and specific decisions far more than hypotheticals, and the interviewer is usually someone who has done the job — a commercial manager interviewing a QS, a contracts manager interviewing a site manager. They are not checking whether you can describe the role. They are checking whether you have actually carried the weight of it.

The twelve questions below come up, in some form, in nearly every interview for a commercial or delivery role. For each one: what it is testing, and what a good answer contains. Prepare one real example per question, with numbers in it, and you will have covered most of what you are asked.

Commercial

1. Walk me through a valuation you prepared end to end.

Testing whether you have owned the process rather than assisted on it. A strong answer moves in order — measurement against the agreed basis, materials on site, variations and their status, retention, the application date and what happened when the payment notice came back short. Name the contract, the value, and the one line that was argued over. If you have only ever populated someone else's spreadsheet, say so and describe the part you did own; interviewers can tell the difference and respect the honesty.

2. Describe a compensation event you managed and how it was resolved.

An NEC question, and often the gating one for infrastructure roles. They want the sequence: what triggered it, whether the early warning went in on time, how you built the quotation, what the project manager's assessment was, and where it landed. The detail that separates candidates is whether you talk about the programme impact as well as the money. A compensation event is a time claim as much as a cost claim, and people who only price the cost get found out.

3. How do you approach a subcontractor final account that is in dispute?

Testing judgement under pressure, not contract law. Good answers start with the paperwork — what was instructed, what was recorded, what was agreed in writing — and move to the commercial reality: what the relationship is worth, what the delay is costing, where the sensible settlement sits. Mention when you would involve the contracts manager or seek adjudication, and when you would not. An answer that goes straight to "we would adjudicate" suggests you have never had to keep a subcontractor on site the following Monday.

4. What is your process for cost reporting to the client?

This is about rhythm and candour. Describe the cycle — monthly, aligned to valuations, cost to date against budget, forecast final account, risk and opportunity register — and then describe how you handle the month the forecast moves the wrong way. The interviewer is listening for whether you report bad news early with a plan attached, or late with an explanation.

Delivery

5. Tell me about a programme that slipped and what you did.

Every programme slips. The question is whether you saw it coming, what you did in the week you saw it, and whether you re-sequenced or just added hours. Strong answers name the critical path activity, the cause, the options you put forward and the one that was taken. Say what it cost. An answer in which nothing was your fault and the programme recovered on its own is not believed.

6. How do you handle a subcontractor who is behind and blaming design?

Testing whether you separate the two problems. Sometimes the design really is late, and the correct answer is an early warning or a notice and a conversation with the design team. Sometimes it is a resourcing problem wearing a design excuse. Describe how you would establish which — information release schedule against the programme, RFIs raised and answered, labour on site against the method statement — and what you would do in each case.

7. Describe a safety issue you stopped work over.

There is a right answer to the first half of this, and it is that you have stopped work. If you cannot think of a time, think harder, because every site has had one — an unprotected edge, a lift plan that was not being followed, an excavation nobody had inspected that morning. Then describe what happened next: who you told, how long it took to make safe, what the conversation with the subcontractor was like, and whether anything changed on site afterwards. The interviewer is checking that you will stop the job when it is expensive and awkward to do so, not only when it is easy.

8. What does a good site handover look like to you?

Testing whether you think past practical completion. Snagging done before the walkround rather than during it; O&M manuals and the health and safety file complete and indexed; commissioning certificates in hand; training delivered to the client's facilities team; defects period arrangements agreed. If you have been on the receiving end of a bad handover, say what was missing — it shows you know what the client is about to live with.

Behavioural

9. Where have you disagreed with a project manager, and what happened?

They want to see that you will push back, and how. A good answer has a real disagreement — on sequencing, on a procurement decision, on whether to notify a delay — a reason you held your position, and an outcome that is not simply "I was right". Being overruled and making the decision work anyway is a perfectly good answer.

10. How do you keep a client informed when the news is bad?

Early, in person or by phone before it goes in writing, with the cause, the impact and the options in the same conversation. Describe a specific occasion. The thing interviewers are listening for is whether you let a client find out from the monthly report.

11. What part of the job do you find hardest?

A genuine answer beats a disguised strength. The commonest honest ones are managing people who do not report to you, the paperwork load on NEC contracts, and the emotional cost of a dispute with a subcontractor you otherwise rate. Pick the one that is true and say what you do about it.

12. Why this sector, and why now?

This matters more than candidates expect, particularly for career changers and for anyone moving between sub-sectors — fit-out to infrastructure, main contractor to client side. A specific answer beats an enthusiastic one: a project you want to work on, a contract form you want to learn, a route to chartership this employer offers. "I have always been interested in construction" is heard every day and tells them nothing.

The questions to ask back

Interviews end with your turn, and what you ask is read as a signal of how you think. Three that are always worth asking:

• What does the first ninety days look like on the project I would join — and what is it currently behind on?
• How are compensation events, or variations, actually administered here: who prices them, who decides, how long does it take?
• What has happened to the last two people who held this role?

The third one is uncomfortable to ask and more revealing than anything else on the list.