Engineering interview questions: technical, design and behavioural, and how to answer each.
Engineering interviews usually test three things: whether you understand the fundamentals of your field, how you reason through a design or failure, and how you work with other people on a project.
Engineering interviews mix technical questions on your field's fundamentals, design or problem-solving questions where you think aloud, and behavioural questions about projects and teamwork. For design questions, clarify requirements, state assumptions, compare options and explain the trade-off you would choose. For behavioural questions, use a project story: the problem, your part, the method and the outcome.
Practice questions for engineers, role by role
Data Questions are taken from each role's TryHired interview page, which builds them from that occupation's O*NET work activities.
| Role (interview guide) | Questions on its page | Two of its practice questions |
|---|---|---|
| Civil Engineer | 13 | Walk me through how you direct engineering activities, ensuring compliance with environmental, safety, or other governmental regulations. Walk me through how you manage and direct the construction, operations, or maintenance activities at project site. |
| Industrial Engineer | 12 | Walk me through how you estimate production costs, cost saving methods, and the effects of product design changes on expenditures for management review, action, and control. Walk me through how you plan and establish sequence of operations to fabricate and assemble parts or products and to promote efficient utilization. |
| Mechanical Engineer | 12 | Walk me through how you read and interpret blueprints, technical drawings, schematics, or computer-generated reports. Walk me through how you research, design, evaluate, install, operate, or maintain mechanical products, equipment, systems or processes to meet requirements. |
| Electrical Engineer | 12 | Walk me through how you design, implement, maintain, or improve electrical instruments, equipment, facilities, components, products, or systems for commercial, industrial, or domestic purposes. Walk me through how you oversee project production efforts to assure projects are completed on time and within budget. |
| Electronics Engineer | 12 | Walk me through how you design electronic components, software, products, or systems for commercial, industrial, medical, military, or scientific applications. Walk me through how you operate computer-assisted engineering or design software or equipment to perform electronics engineering tasks. |
| Biomedical Engineer | 12 | Walk me through how you evaluate the safety, efficiency, and effectiveness of biomedical equipment. Walk me through how you prepare technical reports, data summary documents, or research articles for scientific publication, regulatory submissions, or patent applications. |
| Chemical Engineer | 12 | Walk me through how you develop safety procedures to be employed by workers operating equipment or working in close proximity to ongoing chemical reactions. Walk me through how you troubleshoot problems with chemical manufacturing processes. |
| Manufacturing Engineer | 12 | Walk me through how you troubleshoot new or existing product problems involving designs, materials, or processes. Walk me through how you investigate or resolve operational problems, such as material use variances or bottlenecks. |
General practice questions, not a prediction of what any employer will ask.
How to prepare
- Review fundamentals. The core principles your field's posting assumes; be ready to explain them simply.
- Pick three project stories. A design you contributed to, a failure or test that didn't pass, and a disagreement on a team.
- Practise thinking aloud. Requirements, assumptions, options, trade-off, decision.
- Prepare to discuss tools honestly. What you have used, at what depth, and what you are learning.
- Prepare questions for them. Current projects, review processes and how engineers are mentored.
- Rehearse with a whiteboard or paper. Sketching helps in design questions.
Illustrative examples to adapt
Illustrative: these answers were written by TryHired to show structure. They are not real candidates' answers and were not given in any real interview. Every name, employer, number and result is fictional or a bracketed placeholder: replace each bracket with your own true details, and never claim an achievement you did not have.
Design question structure
When to use: How would you design a component for a given load or requirement?
First I'd confirm the requirements: [load, environment, constraints]. I'd assume [assumption] and state it. Options are [option A] and [option B]; A is better for [criterion], B for [criterion]. Given [priority], I'd choose [option] and validate it with [test or analysis].
Failure story structure
When to use: Tell me about a time a design or test failed.
On [project], [what failed] during [test or review]. I [how you investigated], found [cause], and [change you made]. The next [test or build] [outcome you can document], and I now [practice you adopted].
Question to ask the interviewer
When to use: End of the interview.
What does a design review look like on your team, and how are newer engineers involved in it?
Disclosure: TryHired makes HIRED, a paid job-search program, so we have a conflict of interest when we mention it. Every sample on this page is free to use without buying anything.
What the questions focus on, by field
| Field | Technical focus | Prepare a story about |
|---|---|---|
| Civil or environmental | Loads, codes, site constraints | A design changed by site conditions |
| Mechanical or aerospace | Mechanics, materials, tolerances | A prototype that failed a test |
| Electrical or electronics | Circuits, power, signals | Troubleshooting a fault |
| Chemical or biomedical | Processes, safety, regulation | A process change and its validation |
| Industrial | Process flow, quality, efficiency | Improving a workflow |
The same line, rewritten
Illustrative example with placeholders.
| Version | Example |
|---|---|
| Weak | I'm a strong problem solver and I'm very detail-oriented. |
| Strong | On [project], I [traced which fault, with what method], changed [what], and the next [test] [outcome you can document]. |
Why it matters: Interviewers hear problem solver from everyone. A project story with a method and an outcome shows how you solve problems.
Before you use it
- Fundamentals for your field are reviewed.
- Three project stories are ready.
- You can think aloud through a design question.
- Tool claims match what you can demonstrate.
- You have questions about reviews and mentoring.
- No confidential employer details in your stories.
Mistakes to avoid
- Jumping to a solution without clarifying requirements.
- Overstating your role in a team project.
- Sharing confidential project details.
- Bluffing on a technical question instead of reasoning aloud.
- No questions for the interviewer.
Build yours
Questions people ask
What are common engineering interview questions?
How do I answer engineering design questions?
What if I don't know the answer to a technical question?
What should I ask at the end of an engineering interview?
How this page is built
Written by Maid Dizdarevic, a career coach and 8x LinkedIn Top Voice. Role tables are computed from public data and from TryHired's live role pages; advice is labelled as advice. Every sample uses a 'Your name' placeholder, and every employer, school, date and result is a bracketed placeholder for your own true details.
- What a specific employer screens for: always read the posting.
- Licensing rules: they vary by state; check your state board.
- Outcomes: no resume, letter or answer can promise an interview or a job.
- TryHired editorial guidance by Maid Dizdarevic, career coach, Nov 4, 2026.
- O*NET 31.0 Database, U.S. Department of Labor, Employment and Training Administration (USDOL/ETA), used under the CC BY 4.0 license. TryHired selected, ranked and combined the data; O*NET is not responsible for these pages.