# Civil engineer interview questions and how to answer them

Civil engineer interviews ask you to walk through a project you worked on, describe a problem found on site, explain how you made sure a design met the relevant codes and standards, and show how you communicate with contractors. Answer with your exact role, the numbers behind the design, and the decision you made when the site didn't match the drawings.

By the Speaking Coach team at Sodhera Intelligence. Updated 2026-10-22. Source: https://www.orecci.com/speaking-coach/interview-questions-by-role/civil-engineer/

## What the interviewer is listening for

Civil interviews are usually led by a senior or principal engineer, sometimes with someone from HR. They want to know that you understand why a design is the way it is, that you'll catch your own mistakes before they reach site, and that a site foreman will take you seriously. The technical questions test knowledge. The spoken questions test judgement.

Numbers make you credible. "A 120-metre retaining wall up to 4 metres high" beats "a large retaining wall."

## Walking through a project

Pick one project you know well and can draw on a whiteboard. Use this order:

| Part | What to say | Time |
| --- | --- | --- |
| Scope | What it was, where, how big, who the client was | 20 seconds |
| Your role | Which calculations, drawings or site duties were yours | 20 seconds |
| Key decision | One design choice and the reason, with numbers | 60 seconds |
| Construction | What changed on site and how you responded | 40 seconds |
| Result | Finished on time? What would you do differently? | 20 seconds |

Example opening for a graduate (made-up details):

> "It was a 600-metre road widening with a new culvert under it. I did the drainage calculations and the culvert sizing under my senior's review. The key choice was the culvert size: the existing pipe was 600 mm, but the catchment had grown with new housing upstream, so we went to a 900 mm box culvert."

If your main project was at university, the [final year project](/speaking-coach/interview-questions/tell-me-about-your-final-year-project/) page shows how to present it like work experience.

## Problems on site

Interviewers want to see that you investigate before you redesign, and that you keep the right people informed.

Example answer (made-up details):

> "During excavation for a footing, the contractor hit soft clay about a metre higher than the ground investigation showed. They wanted to keep digging. I asked them to stop on that footing, took photos and called our geotechnical engineer, who came out the same afternoon. We deepened two footings and added a layer of compacted stone. It cost two days, and I wrote up what we'd do if we found the same thing on the other footings so the crew didn't have to wait again."

Show the sequence: stop, record, get the right expertise, decide, document.

## Codes, standards and regulations

You won't be expected to recite clauses, but you should be able to say how you work with the codes that apply where you are.

> "Before I start a calculation, I note which standard and edition the project uses, because the client sometimes specifies an older one. I reference the clause in my calc sheet, so whoever checks it can follow my logic. If I'm unsure how a clause applies, I ask before I design around my guess."

Also mention checking: a second engineer's review, a hand check on software output, or a comparison against a similar past design.

## Communicating with contractors

Contractors judge a young engineer fast. Interviewers want to hear respect, clarity and firmness on things that matter.

| Situation | Weak response | Better response |
| --- | --- | --- |
| Contractor proposes a cheaper alternative | "We have to follow the drawings." | "Send me the details and I'll check it against the design loads by Thursday." |
| Work doesn't match the drawings | Arguing on site | Photograph it, raise a site instruction or query, agree on next steps in writing |
| Contractor asks a question you can't answer | Guessing | "I'll confirm with the design lead and call you back this afternoon." |

Example answer (made-up details):

> "A foreman wanted to reduce the rebar lap length to fit a pour schedule. I explained why the length mattered in two sentences, without jargon, and offered to check whether a mechanical coupler would work instead. It did, and the pour went ahead the next day."

## Mistakes to avoid

- **Saying "we" for everything.** Be clear about which calculations and drawings were yours.
- **Presenting software output as the answer.** Say how you checked it.
- **Sounding rigid.** Being firm on safety and loads is right; refusing to discuss alternatives isn't.
- **Skipping the documentation.** Site problems should end with something written down.

Talking through a design under questioning is different from writing it up. Speaking Coach can play a senior engineer who keeps asking "why that size?" until your answer is clear.

## Questions people ask

### How technical are civil engineering interviews?

Expect some technical questions on your specialism, such as loads, drainage or soils, and sometimes a short design exercise. The behavioural questions carry as much weight, especially for site roles.

### What if I have no site experience?

Talk about site visits from university or internships, and what you noticed. Then show you understand how design decisions affect the people building them.

### How should I answer questions about chartership or licensure?

Say which route you plan to follow and roughly when, and what experience you need from this role to get there. It shows you're planning to stay and grow.

### How do I explain a technical problem to a non-engineer in the interview?

Use one comparison, one number and the consequence. For example: "The old pipe was like a garden hose trying to drain a bath; we needed one twice the size."

---
Speaking Coach on the App Store: https://apps.apple.com/app/id6767124039
Speaking Coach on Google Play: https://play.google.com/store/apps/details?id=com.sodhera.speakingcoach