Interview questions by role
Civil engineer interview questions
Civil engineer interviews check that you understand how infrastructure is designed and built safely, that you apply codes and judgement rather than trusting software blindly, and that you can work with contractors, clients and other disciplines. Expect to walk through a project and your part in it, explain how you would check a calculation, describe a problem on site and how it was resolved, answer questions on health and safety and design standards, and say where you are on the route to chartership or licensure.
Graduates are judged on fundamentals, placements and attitude; experienced engineers on the projects they led and how they handled risk, cost and programme.
How the interview usually runs
Interviews are usually with a senior engineer and a line manager. Graduate schemes often add an assessment centre with a group exercise. The questions depend on your side of the industry: consultancy roles focus on design, such as calculations, modelling, drawings and coordination; contractor roles, such as site engineer, focus on setting out, temporary works, quality, programme and subcontractors.
In the UK, expect questions on your progress towards chartership with a body such as the Institution of Civil Engineers, the Eurocodes you have used, and your duties under the CDM Regulations. In the US, expect questions on the FE exam, your plans for the PE license, and the codes you work to. Everywhere, the panel wants to hear that you know the limits of your competence.
Common questions and what the interviewer is checking
Walk me through a project you worked on and your part in it.
What they are checking: The scope, the main constraint, the decisions you personally made, how they were checked, and the outcome.
How would you check a design calculation, whether a colleague's or the output from software?
What they are checking: Sense checks: a quick hand calculation, the load path, units, assumptions and boundary conditions, rather than accepting a result because software produced it.
Tell me about a problem on site and how you resolved it.
What they are checking: That you stopped, recorded what you found, went back to the designer through the proper query process, and did not improvise a fix outside your authority.
How do you take health and safety into account in your work?
What they are checking: For designers, designing out risk during construction, use and maintenance; for site engineers, temporary works, permits and speaking up.
A contractor asks you to approve a change to save time. What do you do?
What they are checking: Checking the change against the design intent, safety, durability and cost, consulting the responsible engineer if it is outside your competence, and recording the decision.
Which design codes have you used, and what do you do when a situation is not covered?
What they are checking: Real familiarity with the codes for your discipline, working from first principles, taking a conservative approach and asking a senior engineer, rather than bluffing.
Tell me about a time you explained a technical issue to someone who was not an engineer.
What they are checking: Plain language about what the listener cares about, such as cost, delay or risk, with clear options.
How do you manage deadlines across several projects?
What they are checking: Prioritising, being honest early about programme risks, and not letting checking or quality slip when time is short.
Where are you on the route to chartership or licensure?
What they are checking: That you understand the route, keep a record of your development, have a mentor or supervisor, and have a realistic plan.
Why civil engineering, and why consultancy or contracting with us?
What they are checking: Understanding of design versus delivery roles, interest in a sector such as transport, water or structures, and awareness of carbon and resilience.
How to structure a strong answer
Use STAR with the engineering logic in the middle: the constraint, how you analysed it, who checked it and what was built. The reasoning matters more than the software.
- Situation: the project, its scale and your role on it.
- Problem: what was different from the design or what made the design hard.
- Action: what you checked, who you involved and what you decided or recommended.
- Result: what was built, the effect on safety, cost or programme, and what you now do differently.
Example answer
Tell me about a problem on site and how you resolved it.
In my first year as a graduate site engineer on a drainage scheme, we were excavating for a headwall and hit soft, wet ground about a metre above where the site investigation suggested firm clay. The design assumed that clay as the founding layer.
I stopped the excavation and made the area safe with the foreman, then photographed and logged the ground and took levels. I told my section engineer straight away and we raised a technical query with the designer that day, with my photos and the nearby borehole log. Meanwhile the temporary works coordinator checked the excavation support.
The designer changed the detail to a deeper dig with granular replacement. That cost us four days, but I re-sequenced the pipe laying on the next section so we recovered two of them, and the headwall was built and signed off without further issues. Since then I read the ground investigation logs before every excavation starts.
Mistakes to avoid
- Naming software packages instead of explaining the engineering decision and how it was checked.
- Saying “we” throughout a project answer so the panel cannot tell what you did.
- Treating health and safety as forms to complete rather than something that shapes the design and the site.
- Describing a fix you made on site without the designer's agreement as if it showed initiative.
- Not knowing whether the role is design or delivery, or what a typical week in it looks like.
- Having no plan for chartership or licensure, or being vague about where you are on the route.
Frequently asked questions
What questions are asked in a civil engineering interview?
Expect a walkthrough of a project and your role, how you check calculations, a problem on site, health and safety, design codes, explaining technical issues to non-engineers, managing deadlines, your route to chartership or licensure, and why you chose consultancy or contracting.
How are graduate and chartered civil engineer interviews different?
Graduate interviews focus on fundamentals, university projects, placements and attitude. Interviews for chartered or licensed engineers focus on projects you led, decisions you signed off, junior staff, clients and commercial risk.
How technical is a civil engineering interview?
Many include questions on fundamentals such as load paths, bending, soils or drainage, and some set a short calculation or sketch. Talk through your reasoning out loud.
Should I bring a portfolio to a civil engineering interview?
It can help, especially for design roles. Bring a few drawings, sketches or calculation summaries you can talk through, with nothing confidential, and be ready to explain what you personally did on each.