Evaluate Mechanical Engineer candidates across 4 weighted areas: technical depth, work that shipped, diagnosis under uncertainty, and working across the org. Technical depth leads at 35%, so check depth in stress analysis, material selection and tolerance stacks: ask which CAD suite (SolidWorks, Creo, NX), FEA solver, and GD&T standard (ASME Y14.5) they. Use the rubric to compare role-specific evidence consistently.
For technical depth, look for evidence the candidate explains load cases, safety factors and datum schemes precisely, and cites material or fatigue data behind a real design choice. For work that shipped, look for evidence the candidate names shipped assemblies with quantities, cycle times or cost per unit, and describes their own contribution at each design gate.
Apply the written 1–5 anchors to every answer, record the evidence behind each rating, and use the factor weights to reach a consistent overall assessment.
Complete evaluation framework
What to assess and how to score it
Review the evidence signals before interviewing. Then use the anchored descriptions—not instinct alone—to choose the score that best matches each answer.
01
Evaluation factor
Technical depth
35% weight
Check depth in stress analysis, material selection and tolerance stacks: ask which CAD suite (SolidWorks, Creo, NX), FEA solver, and GD&T standard (ASME Y14.5) they apply daily.
Evidence to listen for
Explains the physics or mechanism behind their work, not just the tooling
Names the standards, tolerances, and constraints they designed against
Can defend a design decision under follow-up questions
Distinguishes what they personally engineered from what the team delivered
Five-point scoring guide
1
Poor
Cannot explain the fundamentals of their own stated specialism.
2
Needs Improvement
Knows the vocabulary but not the underlying mechanism; struggles under follow-ups.
3
Satisfactory
Solid working knowledge for the role; depth thins out on edge cases.
4
Very Good
Strong command of the domain; explains trade-offs and defends decisions well.
5
Excellent
Explains load cases, safety factors and datum schemes precisely, and cites material or fatigue data behind a real design choice.
02
Evaluation factor
Work that shipped
30% weight
Probe for hardware that reached production: part numbers, build volumes, tooling released, DFM reviews with suppliers, and how prototypes moved from first article to sign-off.
Evidence to listen for
Names specific programmes, parts, or systems that reached production or field use
States their own scope inside the project
Can give measured outcomes: yield, cycle time, cost, failure rate
Explains what went wrong and what they changed
Five-point scoring guide
1
Poor
No delivered work; experience is coursework, lab-only, or purely observational.
2
Needs Improvement
Contributed to projects but cannot say what shipped or what their part was.
3
Satisfactory
Has delivered real work; outcomes described without numbers.
4
Very Good
Names shipped work and their scope, with some measured results.
5
Excellent
Names shipped assemblies with quantities, cycle times or cost per unit, and describes their own contribution at each design gate.
03
Evaluation factor
Diagnosis under uncertainty
20% weight
Test how they chase field failures: cracked welds, bearing wear, vibration or overheating, and whether they used test rigs, strain gauges, DOE or teardown to isolate root cause.
Evidence to listen for
Describes a real failure they chased to root cause
Shows a method: isolate variables, reproduce, measure, eliminate
Distinguishes correlation from cause
Says what they ruled out and why, not only what the answer turned out to be
Five-point scoring guide
1
Poor
No diagnostic method; guesses or escalates immediately.
2
Needs Improvement
Trial and error with no structure; cannot explain how they narrowed the cause.
3
Satisfactory
Reasonable method on familiar problems; less structured on novel ones.
4
Very Good
Clear systematic approach with a real root-cause story.
5
Excellent
Walks through a failure investigation with measured data, rejected hypotheses, and the design change that stopped recurrence.
04
Evaluation factor
Working across the org
15% weight
Assess collaboration with manufacturing, quality and electrical teams: ECO handling, PPAP or drawing packs sent to machine shops, and negotiating tolerance versus cost with suppliers.
Evidence to listen for
Explains technical constraints to non-technical stakeholders without condescension
Has negotiated scope, cost, or timeline with manufacturing, product, or suppliers
Documents decisions so others can act on them
Takes review feedback without defensiveness
Five-point scoring guide
1
Poor
Cannot communicate outside their specialism; dismissive of other functions.
2
Needs Improvement
Communication gaps cause rework; avoids stakeholder contact.
3
Satisfactory
Works adequately with other teams; documentation is thin.
4
Very Good
Communicates clearly across functions; reliable collaborator.
5
Excellent
Describes specific pushback from a machinist or supplier that changed their drawings, plus how they kept schedule commitments visible.
Evidence-led prompts
Interview questions for a Mechanical Engineer
Use these prompts to surface evidence for the weighted factors above and compare candidates against the same role-specific criteria.
01
Which CAD software are you skilled in using?
02
What are your techniques for stress analysis?
03
How experienced are you with thermodynamics calculations?
04
Can you describe the most challenging mechanical engineering project you have worked on?
05
Can you describe developing a new mechanical process that increased efficiency?
