Civil Engineer Inter­view Questions: Explaining Your Project Role

Civil engineering interviews may ask about the projects you have worked on, your part in design, checking or site coordination, how you work with design and site teams, and how you reason through problems. This guide helps you describe your real role and level of responsibility.

It gives no technical answers, calculations, codes, standards or construction safety instructions, and it does not give legal, licensing or pay advice. Technical content has to come from your own training and from sources you have verified. Formats and questions vary, so follow the invitation and the advert first.

Questions you may be asked

About you and the role:

• Tell me about yourself, and what are your strengths and weaknesses?
• Why this role, and why this employer?

About your projects and responsibility:

• Which projects have you worked on, and what was your part?
• Which decisions were yours, and which needed someone else's approval?
• What did you check yourself, and what did someone else check?

About design and coordination:

• Tell me about a time you coordinated between design and site teams.
• Tell me about a time you noticed an issue late and who you told.
• Describe a time you disagreed with a design decision.

About problems and pressure:

• Tell me about a time you noticed a problem or a risk on site and what you did.
• How would you handle a client who wanted to change a requirement?
• Tell me about a mistake you made and what happened next.

About technical topics and development:

• You may be asked technical questions in your field. Answer from your own knowledge.
• What are your plans for professional development, including registration or chartership if it applies to your career?

Describe your project role and level of responsibility

For each project you might discuss, make notes:

• What type of project was it, and what stage were you involved in? Describe it in general terms.
• What was your role, and what did you personally do?
• What did other people do, such as design engineers, site teams, subcontractors or the client?
• Who approved or decided things, and what was outside your authority?
• What did you check, and what did someone else check?
• What happened, including if the outcome is unknown?

Be accurate about the level at which you worked, for example assisting, working under supervision, checking or taking responsibility. Do not claim calculations, design decisions, sign-offs or inspections that were someone else's.

A short decision log for each project can help. Note the decision, the options considered, who decided and what happened. Keep it general, and leave out calculations and confidential details. Our STAR examples guide and our guide to explaining an unsuccessful project show ways to structure an example.

Professional status and certification

If you are asked about professional registration, chartership or certification, state your actual status accurately. Do not describe a stage you have not reached or imply authority you do not hold. Be clear about what you do under supervision and what you do not. If the advert requires a particular registration or certificate, ask the recruiter what is required.

This guide gives no licensing or registration advice. For what applies to you, check with the relevant professional body or the employer, or get appropriate qualified local guidance.

When you are asked a technical question

Answer from what you know, and say where your knowledge stops. You can talk through your reasoning and state your assumptions, but do not guess at codes, standards or values, and do not quote one you have not verified. If you are asked which one applies, say what you have used and that you would confirm what applies in this case. If you do not know, say so, and say how you would find out or who you would ask. Our guide on what to do when you don't know an answer covers this.

Describing your approach does not replace knowing the fundamentals of your field. If a question touches an essential competence for the role, such as a required analysis method, a tool or a qualification, say accurately whether you have used it, at what level, and what you would need to learn. Do not use a general statement about process to hide a gap.

Site coordination and problems

When you describe coordination between design and site teams, say who you spoke to, what you raised, what happened, including if the outcome was unresolved or unknown, and what was decided by someone else. If you are asked about a safety or quality issue, describe only what you actually did and what you reported through your employer's own process. This guide gives no construction safety instructions or guidance on handling hazards, and you should not suggest that telling someone is all that is needed in an urgent situation. If you do not know an employer's process, say so, and ask what induction and training the employer provides. Not knowing an employer's process does not excuse a gap in core competence, and you should not conceal a limit that is essential or affects safety.

Show your work safely

Drawings, calculations and project records may belong to an employer, a client, a university or a team, and they may be confidential. For every example you plan to show, check that you own it or have permission to share it, and that it contains no confidential material. This applies to personal and university projects too, because they can include another person's, a sponsor's or an institution's material. Leave out names, locations and anything that could identify a client or a site, and if you cannot show something, describe it in general terms. Our portfolio walkthrough guide covers showing work in an interview.

Fictional practice examples

Each example below is invented. Do not present any of them as your own experience or credentials, and do not copy them.

Fictional example, your role and level: "On a small drainage project I was a graduate engineer working under supervision. I prepared drawings for review and recorded questions from site. A senior engineer checked and approved the drawings. I did not sign anything off. I'm not sure how the project finished because I moved to another team."

Fictional example, coordination: "Site asked me a question about a drawing. I wasn't sure of the answer, so I passed it to the design engineer and told site who was dealing with it. I told site when I received a reply. I don't know whether the answer changed the work on site."

Fictional example, raising an issue: "I noticed something on a drawing that didn't seem to match another document. I told the design engineer and showed them both. They said they would check it. I don't know what they decided."

Fictional example, professional status: "I'm working towards professional registration. I carry out checks under supervision and I don't sign off final designs. I'm discussing my development plan with my supervisor."

Fictional example, a limitation: "The advert mentions a design software package I haven't used. I've used a different package for similar work, so I would need training before working independently."

Questions you can ask

• How are design checks and approvals organised on this team?
• How do design and site teams communicate?
• What training and supervision is provided for new engineers?
• What support is there for professional development?

Practice your answers

Say your answers aloud, and record yourself if you wish. If you practice with another person, agree with them before recording. Use true examples, and leave out confidential information. In a real interview, do not use any tool to generate answers unless the organiser has explicitly allowed it, and do not record the conversation unless the interviewer has agreed. Our interview preparation checklist covers the wider preparation.

This guide is published by Muqabala. You can visit our interview practice page for your next practice session. Use any method that suits you, and check how any tool handles your data first. Do not paste confidential employer, client or site information into a practice tool.