Site engineer interviews test whether you can run a working site, not just recite theory. Expect a few questions on your path and the projects you have done, stories about subcontractors, delays and mistakes, what-would-you-do scenarios such as a pump failing mid-pour or a client changing something on the spot, and checks on setting out, reinforcement, concrete, measurement and material reconciliation. Standards and contract terms differ from country to country, so answer with the spec and contract you worked to. Each question shows what the interviewer is listening for, a shape for your answer and a short answer you could say out loud.
Search all questions by round, difficulty and level, or save the ones you want to practise.
Path: your studies and the first time you were on a real site.
What hooked you: a specific part of site work you enjoy.
Now: why this role is the next step.
"In my final year I did a summer placement with a contractor building a four-storey residential block. I expected to spend it in the site office, but the engineer I shadowed had me checking steel and taking levels by the second week. I liked that the work was real and immediate. If a bar was missing, it mattered that afternoon, not in a report next month. After graduating I joined a contractor as a junior site engineer and have spent two years on a commercial building, mostly on the frame. I still enjoy design, but I'm better at making a drawing turn into something standing, and at getting a crew to do it right the first time. This role gives me a bigger site and more responsibility for my own section."
Saying you ended up on site because you could not get an office job, with nothing you actually like about the work.
Your projects: type, size and the stage you were on site for.
Your part: what you were personally responsible for.
Why this one: a real link between your experience and their project.
"I've worked on two projects. The first was a residential tower where I handled the frame from the third floor up, so a lot of rebar checks, pours and formwork cycles. The second was a warehouse with a steel roof, where I looked after the foundations, the ground slab and the drainage. From what I read, your project is a hospital block, which means tight services coordination, lots of embedded sleeves and openings, and a client who cares a lot about quality records. I've done careful pre-pour checks with services before, and I like work where the finishing matters. I'd also like to learn how a building with that much mechanical and electrical content is sequenced."
Listing project names with no idea what you personally did on them, or knowing nothing about the project you are applying to.
Start: briefing, labour count, plan for the day.
Middle: checks, inspections, sorting problems as they come.
End: progress recorded, next day planned, materials requested.
"I'm usually on site before the crews. I walk my area, check that yesterday's work looks right and that it's safe to start. Then there's a short briefing with the foremen: what we're doing today, what's needed, any hazards. I note labour and plant on site. Through the day I'm checking work before it gets covered, like steel before a pour or levels before blinding, sorting out drawing questions and chasing materials. If a consultant inspection is booked, I prepare for it. Late afternoon I record what was done, update the progress sheet, take photos and raise material requests for the next few days. Before I leave I plan tomorrow with the foremen so nobody starts the day waiting for instructions."
A day that is mostly sitting in the site office doing paperwork, with no checking of work before it is covered.
Status: revision, date, and whether it is issued for construction.
Control: superseded copies withdrawn, register updated.
Cross-check: grids, levels and dimensions against other disciplines.
Questions: anything unclear goes to the designer in writing.
"First I check the title block: the revision letter, the date and the status. If it isn't marked for construction, nobody builds from it. I compare it against the drawing register and look at what changed, usually from the revision clouds and notes. Then I pull the old copies off site so the crews can't use them by mistake, and I brief the foremen on the change. After that I cross-check it against the other drawings: grid lines and levels against the architectural set, openings and sleeves against the services drawings, and dimensions that should add up actually adding up. Anything that doesn't match, I raise as a written query to the designer rather than guessing, and I note which work is on hold until I get the answer."
Saying you just hand the new drawing to the foreman without checking the revision or pulling the old one back.
Verify: check the control points against each other first.
Set out: instrument on a known point, main grids from coordinates.
Protect: offset pegs or profiles clear of the dig.
Check: distances, diagonals and an independent check.
"Before setting out anything, I check the control points themselves by measuring between them and comparing with their coordinates, because a disturbed peg ruins everything after it. Then I set up the total station on one known point, orient it to another, and set out the main grid intersections from the coordinates on the drawing. I don't put the only marks where the excavator will work. I set offset pegs or profile boards outside the dig so the lines can be re-established later. Then I check: measure the distances between grids, check that the diagonals of a rectangle match, and close back on a control point. Finally I get someone else, ideally the surveyor, to check it independently and I record the check before work starts."
Setting out from a single control point with no closing check or independent check.
Backsight: read the staff on the benchmark to get the height of instrument.
Foresight: read the staff on the new point and subtract.
Close: run back to the benchmark and check the difference is within tolerance.
"I set up the auto level somewhere I can see both the benchmark and the point. I take a backsight on the staff held on the benchmark. Adding that to the benchmark's reduced level gives me the height of the instrument. Then I take a foresight on the new point, and the reduced level of the point is the height of instrument minus that reading. If the point is far away, I use change points and repeat. The important part is the check: I carry the levels back to the benchmark or to a second known benchmark. The error I get when I close the loop should be within the tolerance for the job. If it's not, I redo it rather than adjusting the numbers to fit."
Height of instrument = RL of benchmark + backsight
RL of new point = height of instrument - foresight
Check: close back on a benchmark; misclosure within tolerance
Taking a single reading to the new point with no closing check back to a known level.
Mistake: plainly, without excuses.
Caught: how and when it came to light.
Fix: what you did about it.
Habit: the check you added so it doesn't repeat.
"Early on, I set out the anchor bolt positions for a line of steel column bases from a drawing that had just been superseded. The grid hadn't changed, but one base had moved slightly. I'd had the new revision in my email and hadn't checked it before going out. The steel fixer's foreman noticed the base didn't match his fabrication drawing, which was on the new revision. We hadn't poured yet, so I told my project manager straight away, re-set the bolts from the right drawing, and had the surveyor check the whole line. It cost us half a day. Since then I check the drawing register before every setting-out job, and I write the revision number on my setting-out sheet so anyone can see which drawing I used."
Choosing a mistake that is really someone else's fault, or one with no change in habit afterwards.
Don't guess: hold that element.
Ask fast: written query with marked-up drawings, and a phone call.
Keep working: move the crew to work that isn't affected.
Record: the query, the wait and the answer.
"I don't pick one drawing and build. The structural engineer is responsible for the beam, but the architect's level might be there for a reason, like a ceiling or a window head. I hold that beam and raise a written query with both drawings marked up side by side, then call the designer so it doesn't sit in an inbox. Meanwhile I move the crew to formwork on the parts of the floor that aren't affected, so we don't lose the day. When the answer comes, I make sure it's in writing and that both drawings get revised, or at least that the answer is attached to them, so the next person doesn't hit the same question. I also note in the daily report how long we waited."
Building to whichever drawing looks more likely and sorting it out later.
Match the drawing: bar sizes, numbers, spacing and shapes against the drawing and bending schedule.
Laps and anchorage: lap lengths, lap positions, bars carried into supports.
Cover and fixing: correct spacers, chairs, bars tied firmly.
Everything else: clean steel, openings, sleeves and embedded items in place.
"I go through it against the structural drawing and the bar bending schedule, one element at a time. I check bar diameters, the number of bars, spacing, and that top and bottom steel are the right way round. I look at laps: the length, which the drawing gives as a multiple of the bar diameter, and that they're in the positions the drawing allows and staggered where required. I check that bars are anchored properly into beams and columns, and that stirrups have the right hooks and spacing, especially near supports. Then cover: the right size spacer blocks at the right spacing, and chairs holding the top mat so it won't get pushed down when people walk on it. The steel should be clean, without loose rust, mud or oil. Last, I check sleeves, openings and electrical conduits are fixed and don't cut the steel."
Checking only bar sizes and spacing and forgetting cover, laps or embedded services.
Approvals: steel, formwork, levels and services signed off.
Formwork and access: props, ties, clean deck, safe access and edge protection.
Resources: concrete supply rate, pump, standby plant, vibrators, crew, lighting.
Quality and after: testing kit, joint plan, curing materials ready.
"First the paperwork: steel, formwork, levels and embedded services all inspected and signed off, because I won't pour on a promise. Then I walk the formwork: props plumb and on firm ground, ties and wedges tight, the deck clean of wire and debris, and safe access and edge protection in place. I confirm the order with the batching plant: the right mix, the total quantity and a delivery rate that matches how fast we can place and compact. I check the pump and have a backup plan if it fails, vibrators with spares, enough labour, and lighting if we might run late. I check the weather. I make sure testing equipment and sample moulds are ready, the construction joint position is agreed in case we have to stop, and curing materials are on the slab before we start. During the pour a carpenter watches the props and formwork from a safe spot."
A checklist that only covers ordering concrete and ignores formwork, backup plant and what happens if the pour has to stop.
Ticket: grade, mix, quantity and batching time match the order.
Time: within the limit the spec allows from batching to placing.
Test: workability test and samples at the specified frequency.
Water: none added on site unless the mix design and engineer allow it.
"I start with the delivery ticket. It has to show the grade and mix we ordered, the quantity, and the time it was batched. I check the time against the limit in our specification, because concrete that has been sitting too long can lose workability and strength. I look at the concrete as it starts to come down, and I do a workability test, usually a slump test, and compare it with the range in the spec. Samples for strength testing are taken at the frequency the spec sets and labelled with the truck and the location it went into. If the driver or the crew want to add water to make it easier to place, the answer is no unless the spec and the approved mix design allow it, and then only under my control. A truck that fails the checks gets rejected and recorded."
Letting the crew add water to stiff concrete to make it easier to pump.
Buy time: hold trucks at the plant, keep the placed concrete workable.
Restore supply: standby pump, crane and skip, or another route.
If you can't: a proper construction joint at a position the structural engineer agrees.
After: treat the joint properly and record everything.
"I'd move fast because the clock starts as soon as concrete stops arriving. I tell the batching plant to hold trucks that haven't left, and I make sure the trucks already on site don't sit too long. I get the pump operator's estimate for the fix, and at the same time call for the standby pump or see if we can place with the crane and a skip. If supply can restart before the last concrete stiffens, we carry on and vibrate the new concrete into it. If it can't, I don't let it stop wherever it stopped. We form a proper construction joint with a stop-end, at the position the structural engineer agrees, usually near the middle of a span where shear is low. Later, the joint is prepared as specified, removing laitance and roughening it before the next pour, and I record the whole event."
Letting the slab stop in a ragged sloping edge wherever the concrete ran out, with no one deciding where the joint goes.
Risk: what heavy rain does to fresh concrete.
Options: go with protection, split the pour, or postpone.
Decide early: with the project manager, consultant and plant.
If caught mid-pour: protect, and stop at a proper joint if needed.
"Heavy rain on fresh concrete washes out the surface, adds water to the mix and can wreck the finish of a roof slab that needs to shed water later. So I look at the forecast in detail: when the heavy rain is expected and for how long. If it's a light shower risk, we can go ahead with plastic sheeting ready to cover the finished areas. If heavy rain is likely during the pour, I'd recommend postponing, and I'd make that call with the project manager and the consultant the evening before or early morning, before the plant starts batching, so we don't waste concrete or pay for trucks that get turned back. If rain arrives unexpectedly mid-pour, we cover what's placed, and if we can't continue properly, we stop at an agreed construction joint."
Pouring anyway without protection because the programme says so.
Theoretical: quantity of work done times the standard consumption.
Actual: opening stock plus received minus a physical closing count.
Compare: against the allowed wastage.
Explain: investigate and act on any variance.
"I work out two numbers and compare them. The first is what we should have used: the quantity of work done this month from the measurements, multiplied by the standard consumption, so for cement that comes from the mix designs, and for steel from the bar bending schedules. The second is what we actually used: opening stock plus everything received, minus the closing stock, and I count the closing stock physically rather than trusting the register. The difference is compared with the wastage allowed in the contract or by the company. If steel is over, I look at offcuts and scrap, rework, or bars cut wrongly. If cement is over, I look at mix control, plastering thickness and storage losses. And I report the variance honestly, because it points to a real problem on site."
Adjusting the closing stock on paper so the numbers match instead of counting it.
Content: work done, labour, plant, materials, weather.
Problems: delays, hold-ups, instructions received.
Readers: project manager, planner, quantity surveyor, client.
"My daily report covers what work was done and where, by grid and level, so anyone can find it. It lists labour by trade and subcontractor, plant on site and whether it was working, materials received, and the weather. Then the problems: anything that stopped work, like waiting for drawings, an inspection not turning up, rain, or a breakdown, with times. I also note any instructions from the client or consultant and photos of key work. The project manager uses it to see where we are, the planner updates the programme from it, and the quantity surveyor uses it to back up measurements and claims. If there's ever a dispute about a delay, the daily reports are often the best record we have, so I write them the same day while I still remember."
Treating the report as a copy-paste formality with the same text every day.
Cause: what went wrong and whether it was ours or someone else's.
Notice: how and when you flagged and recorded it.
Recovery: resequencing, extra resources, working in parallel.
Result: how much you recovered and what it taught you.
"On a commercial building, the revised drawings for the transfer beam level came late from the designer, and we lost nearly two weeks on that floor. As soon as it was clear the drawings weren't coming, I told my project manager and we put it in writing to the client, with the date we asked and the date we received them, so the delay was recorded. While we waited, I pulled forward other work: the staircases and the columns in the parts of the floor that weren't affected. When the drawings arrived, we pre-fabricated the steel cages on the ground while the formwork went up, and split the pour into two sections so each could proceed as soon as it was ready. We recovered most of the time by the next two floors."
A delay story with no written record and no recovery plan, only waiting for the problem to go away.
Rules: measure as the contract's method of measurement says.
Agree: joint measurement with the client's representative, signed records.
Build the bill: cumulative quantity less previous bills, against the bill items.
Subcontractors: checked against the same measurements, extras only with approval.
"I measure from the actual work done, following the method of measurement in the contract, because that decides things like what deductions apply for openings. For the client, I do joint measurements with their representative on site and we both sign the measurement sheets, with the drawings, sketches and photos as backup. The bill then shows the cumulative quantity for each item up to date, minus what was billed before, so this bill is only the new work. Anything outside the original items, I don't slip into an existing line. It goes as a variation, only once it has been instructed. For subcontractors, I check their claim against the same measurements, so we never pay them for more than the client is paying us for the same work, and I take off any materials we supplied to them."
Billing from drawing quantities alone without measuring what was actually built, or paying a subcontractor more than has been certified for the same work.
Pause: the foreman does not act on a verbal instruction.
Understand: what exactly is wanted and why.
Check: impact on structure, services, cost and programme.
Formalise: written instruction through the contract route before work.
"First I tell the foreman not to change anything yet. That's not about being difficult. On most contracts only certain people can instruct a change, and a verbal one leaves us unpaid and exposed if it goes wrong. Then I go to the client's representative, thank them, and make sure I understand exactly what they want and why. I check the impact: does the wall carry services, is it on a slab that was designed for it there, does it affect doors, fire compartments or finishes already done. I pass it to my project manager and the quantity surveyor so we can price the cost and time, and we ask for a written instruction through the contract route. If it's urgent, I'll ask for a signed site instruction the same day, so the work isn't held up for weeks."
Letting the foreman move the wall on the spot because the client asked for it.
Plan: an inspection and test plan with hold points for each activity.
Check first: your own check before inviting the consultant.
Record: signed checklists and photos.
Close out: defects tracked until fixed and re-inspected.
"I work from the inspection and test plan for the job, which says for each activity what gets checked, by whom, and where the hold points are, meaning work can't continue until it's signed off. Before anything gets covered, like steel before concrete, waterproofing before backfill, or services before a ceiling, I check it myself with a checklist first, and only then raise an inspection request to the consultant. That way they find very little, and we don't waste their visit. Each inspection is signed and dated with photos, and filed by location so we can find it later. Anything that fails goes on a defects or non-conformance list with a name and date against it, and it's re-inspected before we move on."
Relying on the consultant to find defects rather than checking your own work first.
Assess: how deep and how big, and whether steel is exposed.
Report: photos, record, tell the structural engineer or consultant.
Repair: the approved method for that severity, never a cosmetic cover-up.
Cause: vibration, grout loss or congestion, fixed for the next pour.
"The first thing I don't do is let anyone plaster over it. I look at how deep and how widespread it is, and whether reinforcement is exposed. I photograph it, record it, and report it to the project manager and the consultant, because a column is a critical element. If it's shallow and on the surface, the usual repair is to cut back to sound concrete, clean it, and fill with an approved repair mortar using the method the engineer agrees. If it's deep, exposes bars or is extensive, it goes to the structural engineer to decide, and that can mean grouting, a specialist repair, or in a bad case breaking out and recasting. Then I find the cause: poor vibration, grout leaking from form joints, too much steel for the aggregate, or concrete dropped from too high, and I fix it before the next pour."
Saying you would just patch it with plaster so it looks fine before the inspection.
What was rejected: and the reason given.
Response: listen, check the requirement, agree or respectfully query.
Fix: corrected and re-inspected.
Learning: what your own checks now include.
"The client's engineer rejected a set of ground beams because the cover blocks were spaced too far apart and the bottom bars were sagging between them. My first reaction was that it was fine, but when I looked with him, he was right. At the midpoints the cover was clearly less than specified. I didn't argue. I asked the steel fixers to add blocks at closer spacing and lift the bars, did my own check with a tape along every beam, and called him back the same afternoon. He passed it. After that, spacer spacing went onto my own pre-inspection checklist, and I started checking cover at the middle of spans, not just at the ends where it's easy to see."
Getting defensive or describing how you went over the engineer's head to get the work passed.
Quarantine: keep it apart and tag it, nothing gets fixed.
Report: project manager, quality team, supplier.
Resolve: correct certificate or independent testing.
Decide: accept on evidence or reject and return.
"I don't let it get used. I have the bundles stacked separately and tagged as on hold so nobody picks them up by mistake. I tell my project manager and the quality team, and I contact the supplier to ask for the correct certificate for those heats or batches. If they can't produce one that matches, we take samples for independent testing at an approved lab, as the spec allows. The steel only gets used if the evidence shows it meets the requirement. Otherwise it goes back. Meanwhile I check whether we have other approved steel to keep the fixers working, and I record it as a non-conformance so the supplier's other deliveries get a closer look."
Using the steel because it looks the same and the fixers are waiting.
Position: a hold point means no pour without sign-off.
Solve: get the inspection today, by phone, by walk-through, by escalation.
Explain: the risk of pouring uninspected work.
Record: put it in writing if pressure continues.
"I'd explain to the project manager that I can't pour without the sign-off, because if the consultant later asks to see that steel, the only way to show it is to break the slab out. Then I'd put my effort into getting the inspection today. I call the consultant directly, tell them the pour is booked, and ask for a time. I make sure our own check is done and the paperwork is ready so the visit is quick. If they can't come, I ask who else on their team can, and I let my project manager escalate to their senior. If none of that works, I'd rather move the pour to tomorrow than cover it up. If I'm told to pour anyway, I'd put my concern in writing, because that decision needs to be on record."
Pouring and planning to send photos afterwards, or refusing to help find a way to get the inspection done.
Respect the role: they protect the client; that's their job.
Facts, not feelings: argue from the drawing, spec and contract.
Make it easy: ready work, clear paperwork, no surprises.
Escalate properly: when you really can't agree, in writing through the right route.
"I try to remember that their job is to protect the client, and sometimes that means being strict with me. So I keep disagreements about the drawing, the spec and the contract, not about who's right. If I think they're asking for more than the spec requires, I show them the clause and ask what I'm missing. Often there's a reason I hadn't seen. I also make their job easy. Work is ready when I call them, my own checks are done, and the paperwork is in order. That builds trust, and trust means small questions get sorted on the spot. When we truly can't agree, I don't argue on site in front of the crew. It goes to my project manager and through the proper route, in writing."
Talking about the client's engineer as an obstacle to get around.
Situation: the trade, how far behind, what depended on them.
Cause: what you found when you looked into it.
Action: the plan you agreed and how you tracked it.
Result: where they ended up and what you learned.
"At my last company our blockwork subcontractor fell about two weeks behind on three floors, and the plasterers and electricians were stacking up behind them. Instead of just complaining, I sat with their supervisor and went through it floor by floor. The real problem was half ours: blocks were being delivered to the ground floor and they were losing hours moving them up by hand. We got the hoist time allocated to them in the mornings and the blocks moved to each floor the night before. They agreed to add a second gang, and I set weekly targets per floor that we checked together every Friday, all confirmed by email. Within a month they'd recovered most of the delay. I learned to check whether we are part of the problem before blaming the sub."
A story where the only action was threatening to cut their payment.
Situation: the crew and what went wrong.
Listen: what was behind it.
Act: what you did, and through whom.
Result: how the work and relationship ended up.
"On a housing project, the shuttering carpenters stopped work one morning over a disagreement with their foreman about overtime. A slab pour was booked for two days later. I didn't take sides on the spot. I asked the foreman and two of the carpenters to talk with me away from the rest of the crew. It turned out they'd worked late the week before and felt they hadn't been paid for it properly. That was between them and their employer, so I called the subcontractor's manager, explained that the pour was at risk, and asked him to come and settle it that morning. He did, and they were back at work after lunch. I also made sure future late working was agreed and written down before the day, not argued about afterwards."
Handling it by shouting at workers or dealing with pay disputes that belong to their employer.
What happened: short and factual.
Immediate action: make safe, first aid, report.
Cause: what the investigation found.
Change: what was done so it doesn't happen again.
"On a frame job, a short offcut of timber fell from a slab edge two floors up and landed near a worker below. Nobody was hurt, but it was close. I stopped work in that area, cleared the zone underneath and reported it to the safety officer as a near miss the same hour. When we looked at it, there were two causes: there was no toe board along that edge because it had been removed to pass formwork out, and there was no marked exclusion zone below. The fix was to put the toe boards back with a proper gate for passing materials, add a barricaded zone underneath during stripping, and do a toolbox talk about it the next morning. I learned that near misses are free lessons, and they only help if people report them."
Blaming the worker alone, or suggesting the near miss was not worth reporting because nobody was injured.
Topic: tied to that day's real work or a recent near miss.
How: short, in the crew's language, showing not telling.
Result: what you saw change afterwards.
"We were starting work on scaffolding for external plaster, and I'd seen people climbing the frames instead of using the ladders. Instead of reading rules, I took the crew to the scaffold for ten minutes. I showed them where the ladder access was, asked one of the older workers to explain why a climbed frame can shift, and showed them how to check a scaffold tag before going up. I kept it in the language most of them spoke and asked them what else they'd noticed that felt unsafe. Two of them pointed out a missing guardrail on the top lift, which we fixed that morning. Over the next weeks I hardly saw anyone climbing the frames, and the crew started telling newcomers themselves."
Describing toolbox talks as reading a sheet and getting signatures.
Stop: calmly, straight away.
Make safe: clipped on or brought down.
Why: anchor point, equipment or habit.
Follow up: his supervisor, a record, a fix.
"I stop him straight away. It doesn't matter whose worker he is; anyone on site can and should stop unsafe work. I do it calmly so he doesn't make a sudden move, and he either clips on or comes down. Then I ask him why. Often there's a reason: nothing to clip on to, a lanyard that's too short for the job, or he was only going up for a minute. If it's the anchor point or the kit, that's on us and his supervisor to fix before he goes back up. I tell his supervisor, record it as an observation, and if it's a habit across that crew, I'll raise it at the next toolbox talk and with the subcontractor's manager."
Saying it's the subcontractor's job to manage his own workers' safety.
What you see: housekeeping, access, protection, storage.
How people act: PPE worn, work stopped when unsafe, questions asked.
What's on paper: current drawings, clear programme, records up to date.
"The first thing I notice is housekeeping. Clear walkways, materials stacked and labelled, rubbish in skips rather than around the floor. Then edge protection, covered openings, safe ladders and scaffolds with valid tags. I look at how people behave: whether PPE is worn without anyone shouting, whether a worker will stop and ask if something's unclear. In the site office, I look at whether the drawings on the wall are the current revision and whether today's plan is written somewhere everyone can see. A site like that usually has fewer incidents and less rework, because the same discipline shows up everywhere. That's the kind of site I try to run, and it's much easier to keep a site tidy from day one than to fix it later."
Answering only about speed of progress, with nothing on safety, housekeeping or control of drawings.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your resume and notes are never stored on our servers. It stays out of screen share on every plan; only you can see it.