Engineer interview questions and answers in English

B1 answer

I'm a civil engineer. I've worked for a construction company for four years. I work on roads and small bridges. I check drawings, visit the site and write reports. I enjoy solving practical problems. Now I'd like to work on bigger projects and become a chartered engineer.

B2 answer

I'm a mechanical engineer with five years of experience in building services, mostly heating and ventilation for schools and hospitals. I produce designs, check calculations and spend about two days a week on site with contractors. On my last project I led the design of a system for a 200-bed hospital wing. I'm applying here because I'd like to move into larger projects and work towards chartered status.

B1 answer

I want to join your company because you work on big infrastructure projects, like bridges and railways. I'd like to learn from experienced engineers. I'm careful with details and I communicate well with contractors on site, so I think I can help your projects.

B2 answer

I'd like to join because your projects are larger and more technical than mine, especially your rail work, and that's the direction I want to grow in. I also know you support engineers towards chartership, which is my goal for the next two years. In return, I bring strong site experience, I'm careful with calculations and I'm used to explaining technical issues to clients.

B1 answer

First I stop the work, politely but clearly. I explain the danger and make sure the area is safe. Then I tell the site supervisor. I write a short report about what happened. Later I check that the problem is fixed and the worker has the right equipment.

B2 answer

Safety comes before the programme, so I'd stop the activity straight away, calmly and without blaming anyone. Then I'd make the area safe and explain the risk to the worker. After that, I'd inform the site manager and record it as a near miss, so we can learn from it. If it showed a wider problem, I'd suggest a short toolbox talk the next morning.

B1 answer

First I read the drawing carefully and check it against the brief. Then I check the main calculations again, step by step. I ask a colleague to review it too. If I find a mistake, I correct it and I write it in the log. Only then do I send it.

B2 answer

I use a checklist, because it's easy to miss things when you're busy. First I check the drawing against the brief and the latest revisions, then I repeat the key calculations by hand to make sure the software results are sensible. Before anything is issued, a second engineer reviews it. On my last project this process caught three errors before they reached site.

B1 answer

Last year we were building a small bridge, and the ground was softer than in the survey. I had to find a solution quickly. I talked to the ground engineer, I changed the foundation design and I explained the new plan to the client. In the end we finished only two weeks late.

B2 answer

On a school project last year, the steel delivery was delayed by six weeks, which threatened the opening date. I had to find a way to keep the programme on track. I reorganised the sequence of work, so the concrete and drainage were done first, and I agreed a partial delivery with the supplier. As a result, we lost only one week, and the school opened on schedule.

B1 answer

I use simple words, and I don't use too many technical terms. I often draw a quick sketch or show a photo. I explain the problem, the options and the cost. Then I ask the client if they understand and if they have any questions.

B2 answer

I start with what matters to the client: cost, time and safety. Then I explain the problem in plain English, often with a simple sketch or a photo from site. I give two or three options, with the impact of each. For example, I recently explained a drainage issue to a head teacher with one diagram, and she approved the solution in the same meeting.

B1 answer

First I listen to both people and I ask them to explain their ideas. Then we look at the facts together: the cost, the safety and the programme. We choose the best option. If we can't agree, I ask the project manager to decide.

B2 answer

I'd bring them together and ask each to explain their reasoning, because disagreements often hide a missing piece of information. Then we'd compare the options against the brief: safety, cost, programme and buildability. Usually the data makes the answer clear. If not, I'd take both options to the project lead with a short summary, so the decision is quick and nobody feels ignored.

B1 answer

Yes, I have two questions. What kind of projects would I work on in my first year? And do you support engineers who want to become chartered? I'd like to plan my development, so I can be useful on your projects and keep learning.

B2 answer

Yes, a couple. How is time usually split between the office and site for this role? I'd also like to know how you support engineers towards chartered status, for example with a mentor. Finally, which project is the team most excited about at the moment? That would help me understand where I could contribute first and what I should read before I start.