Mechanical Engineer Inter­view Questions: Explaining Your Work

Mechanical engineering interviews may ask about your design, analysis, testing and manufacturing experience, how you work with other teams and how you reason through technical problems. This guide helps you describe your real experience: what you designed or analysed, what you personally did and what other people did.

It does not answer technical questions, and it gives no calculations, formulas, standards or operational engineering or safety instructions. 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 design and manufacturing experience:

• Which parts, assemblies or systems have you worked on, and what was your part?
• How did you take manufacturing, assembly or cost into account in a design?
• Tell me about a design or test that did not go as expected.
• Tell me about a disagreement with a supplier, a machine shop or a colleague.

About tools and analysis:

• Which CAD, analysis or other software have you used, and for what?
• What did you do yourself, and what did someone else run or check?

About problems and working with others:

• How do you work when information is incomplete?
• Tell me about a mistake you learned from.
• Tell me about a time you persuaded someone who disagreed with you.
• How did your work hand over to manufacturing or testing?

About technical topics:

• You may be asked technical questions related to the role, for example about materials, tolerances, drawings, analysis or fundamentals. Answer from your own knowledge.

Describe your design and manufacturing experience

For each project you might discuss, make notes:

• What was the part, assembly or system, described in general terms, and what was it for?
• What constraints applied?
• What did you personally do, for example design, analysis, drawing, testing or contact with suppliers?
• What did other people do, such as senior engineers, analysts, technicians or suppliers?
• Which decisions were yours, and which were someone else's?
• What happened, including if the outcome is unknown?
• What would you do differently?

Be accurate about the level at which you worked, for example assisted, contributed, led or reviewed. Say what you did yourself and what was checked or approved by someone else. Do not claim analysis, sign-off or responsibility for results that were not yours. Our STAR examples guide and our guide to explaining an unsuccessful project show ways to structure an example.

When you are asked a technical question

Answer from what you know. You can state your assumptions and explain your reasoning aloud, and you can say what you would need to check. Do not guess at standards, formulas or values. 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.

Explaining your method does not replace knowing core fundamentals. 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 hide a gap behind a general statement about process. Do not describe analysis or tests you have not done.

Show your work safely

CAD files, drawings and test data may belong to an employer, a university, a client or a team, and they may be confidential or proprietary. 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. A recreation is not safe just because it is labelled as one: it must not reproduce confidential or proprietary material. Leave out names, part numbers and anything that could identify a client or a product, and if you cannot show something, describe it in general terms. Open the exact file you plan to share beforehand. 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, and do not copy them.

Fictional example, your contribution: "On a team project I designed a bracket for a test rig. A senior engineer reviewed my drawing and asked me to change one feature, and I updated the drawing. A colleague ran the analysis. I can explain the assumptions I was given and what the result was used for. I did not run the analysis myself, so I won't describe it as my work. If the role needs me to run this kind of analysis, I would tell you what I can do now and what I would need to learn."

Fictional example, working with manufacturing: "A machine shop told me a feature on my drawing was difficult to produce. I asked what they needed, we discussed options and I changed the drawing after my supervisor approved the change. I don't know how much time it saved."

Fictional example, a test that went wrong: "A prototype did not pass a test. I was responsible for gathering the test records for my team. Colleagues investigated the cause. I wrote up what I had recorded and helped repeat the test. I did not decide the fix."

Fictional example, a limitation: "The advert mentions a simulation package I haven't used. During my degree I used a different tool for simple analysis, so I would need training and supervised practice before working independently."

Questions you can ask

• What kinds of products or systems would I work on?
• How does design hand over to manufacturing or testing in this team?
• What training and supervision is provided for new engineers?
• What would my first months involve?

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 design information into a practice tool.