How engineering interviews work

Engineering interviews vary significantly by discipline (civil, mechanical, electrical, chemical, structural) and by career stage (graduate versus experienced hire). Most share a common structure: technical questions covering core engineering principles relevant to the role, design or problem-solving exercises, project experience review, and behavioral competency questions. Graduate scheme interviews typically add verbal and numerical reasoning tests and assessment centre elements.

The depth of technical questioning reflects the seniority and specialisation of the role. A graduate civil engineering interview will test fundamentals. A senior structural engineer interview will go deep on project-specific design decisions, codes of practice, and professional judgement. Know what level you are being assessed at and prepare accordingly.

Technical questions by discipline

Civil/Structural: "Explain the difference between ultimate and serviceability limit states." ULS relates to structural collapse — designing so the structure does not fail under maximum loading. SLS relates to performance in normal use — deflection, vibration, cracking. Both are required by modern codes (Eurocode, BS standards). Know the relevant codes for your market and role. Mechanical: "How would you select a material for a component that must be both lightweight and corrosion-resistant?" Walk through the decision: specific stiffness (E/ρ), yield strength, corrosion resistance in the operating environment, manufacturability, and cost. Aluminium alloys, titanium, and carbon fibre composites each have their place depending on these tradeoffs.

Design and problem-solving questions

"Walk me through how you would approach the design of [component or system relevant to the role]." Engineering design questions test structured thinking. Cover: requirements gathering and constraints, concept generation (more than one option), evaluation criteria, selection and justification, and iteration based on analysis or testing. Show that your design process is systematic rather than jumping to the first idea.

"How would you approach a situation where your initial design did not perform as expected during testing?" Show structured root-cause analysis: what does the test data tell you, what does it rule out, what are the most likely failure modes given the design, and how would you modify the design to address them? Show that you treat test failures as valuable information rather than as problems to explain away.

Project experience questions

"Walk me through the most complex engineering project you have worked on." For experienced hires, this is often the core of the technical interview. Show: the problem you were solving, the constraints (cost, schedule, performance, regulatory), the decisions you made and why, how you managed interfaces with other engineering disciplines, and what the outcome was. Be specific about your personal contribution versus the team's.

"Tell me about a time you identified a safety concern on a project." Safety is central to engineering professional practice. Show that you understand your personal obligation to raise safety concerns regardless of commercial pressure, that you did so through the appropriate channels, and that you have a clear view of when an issue warrants stopping work versus managing through standard risk controls.

Professional and career questions

"What is your progress towards chartership?" For most engineering disciplines, professional chartership (CEng, IEng, or equivalent) is the expected career progression. Know your position in the process: whether you are working towards it, what competencies you are developing, and when you expect to apply. If you are already chartered, be ready to discuss what the process involved and what you see as its value.

"How do you stay current with developments in your engineering discipline?" Show specific habits: journal subscriptions (ICE, IMechE, IEEE publications), CPD records, conference attendance, code updates from relevant standards bodies. Engineering knowledge evolves and candidates who show awareness of current practice alongside strong fundamentals are preferred over those who have not kept up since their degree.

Get real-time help in your next interview
Live Interview Help listens to your interview and surfaces personalised answers in real time. Free 20-minute trial on Google Meet, Teams, and Zoom.
Install Free on Chrome

Frequently asked questions

How technical are graduate engineering interviews?
Graduate scheme interviews balance technical testing with potential assessment. They typically include structured technical questions on fundamentals, a design or problem-solving exercise, and behavioral competency questions. The technical bar tests whether you have the foundational knowledge to develop, not whether you already have professional expertise. Numerical reasoning and situational judgement tests are common additions for graduate schemes at large employers.
Should I bring a portfolio to an engineering interview?
Yes, for any role that involves design or project delivery work. A well-organised portfolio demonstrating projects you have contributed to, calculations you have done, or problems you have solved gives the interviewer concrete evidence of your capability. Keep it digital and easily navigable. Printed portfolios are also acceptable for in-person interviews. Reference specific pages or projects in your answers to make the portfolio an active part of the interview rather than a passive artefact.
How do I prepare for engineering technical questions?
Review the fundamentals relevant to the role: mechanics of materials, fluid mechanics, thermodynamics, or electrical circuit theory depending on your discipline. Read the relevant design codes and standards. Review any project calculations or reports you have contributed to and be ready to explain your methodology and the decisions you made. Practice deriving answers from first principles rather than memorising results, since interviewers often probe the reasoning behind your answers.