Technical questions

"How would you improve a process that is missing its production target?"

A strong answer does not jump directly to "use Lean."

Start by clarifying demand, takt or required output. Confirm actual cycle times, uptime, changeovers, staffing, scrap and starvation/blocking. Observe the process. Identify the constraint. Then choose a change that addresses the measured loss and define how you would validate it.

Good candidates explain why they would not optimize a non-constraint operation while the true bottleneck remains unchanged.

"What is the difference between process capability and process stability?"

Explain that a stable process has predictable statistical behavior over time, while capability asks whether the process distribution can meet specification. A process can be stable and still produce outside specification if it is centered poorly or has excessive variation.

Then connect the concept to action: do not interpret a capability index as proof of a healthy process without checking the process and measurement assumptions.

"How do you approach a new manufacturing process?"

Discuss product requirements, CTQs, process sequence, equipment/tooling, risk analysis, measurement, work instructions, capacity, safety, validation and launch controls. Mention cross-functional review rather than presenting process design as a solo activity.

Root-cause scenarios

"Scrap doubled this week. What do you do?"

Use a disciplined sequence:

  1. contain the quality risk if necessary;
  2. define the defect precisely;
  3. verify the measurement method;
  4. stratify by part, machine, cavity, shift, operator, supplier lot, time or other plausible factors;
  5. compare what changed;
  6. test likely causal mechanisms;
  7. implement and verify the countermeasure;
  8. update controls and monitor recurrence.

Avoid saying "I would do a 5 Why" as the entire answer. A method is useful only if the evidence supports the causal chain.

"A defect disappears when engineering watches the line. How do you investigate?"

Acknowledge observation effects. Review automated data, time-stamped alarms, video if permitted, quality records and operator accounts. Compare conditions across shifts and product variants. Make the investigation non-punitive so people do not hide workarounds. The problem may be an intermittent condition, setup variation or an unofficial recovery method.

Lean and quality questions

"When would you use a value-stream map?"

Use it when the problem spans material/information flow across multiple steps and you need to distinguish processing from waiting, inventory and handoffs. It is less useful for a narrowly isolated machine fault where detailed equipment diagnostics are the real need.

"How are PFMEA and a control plan connected?"

PFMEA identifies and prioritizes process risks and existing controls. The control plan translates important prevention, detection and reaction controls into the operating process. A weak answer treats them as separate documents updated for an audit; a stronger answer explains how process changes should flow through both.

"What would you do if a process is in control but not capable?"

Do not tamper with stable common-cause variation one point at a time. Investigate centering, process design, equipment capability, material variation and other common-cause sources. The improvement requires changing the system, not chasing normal noise.

Equipment and process questions

"A machine stops intermittently. How would you troubleshoot it?"

Lead with safety and authorization boundaries. Preserve fault information before resetting when possible. Check the fault history and sequence state. Determine whether the stop is mechanical, electrical, controls-related, material-related or operator-induced. Check sensors, I/O and interlocks only within your role's safe access level.

Explain when you would escalate to maintenance or controls specialists rather than making unauthorized changes.

"How do you reduce cycle time without hurting quality?"

Separate value-added process time from handling, waiting, motion, inspection and recovery. Look for parallel work, fixture improvements, sequence changes, automation or parameter optimization. Then define guardrails: CTQs, capability, safety, tool life and equipment stress.

The answer should show that "faster" is not automatically "better."

Behavioral questions

"Tell me about a process improvement you led."

Use an engineering version of STAR:

Situation: process and business/quality problem.

Task: what you personally owned.

Analysis/Action: observations, data, hypotheses, experiments, stakeholders and change.

Result: validated outcome and what was standardized.

If a metric is confidential or unavailable, use an accurate qualitative result and describe the validation method.

"Tell me about a time production disagreed with your recommendation."

Show how you handled constraints. Production may know practical failure modes you missed. Explain how you listened, returned to evidence, ran a controlled trial or changed the design. The interviewer is testing whether you can improve a live system without treating operators as implementation obstacles.

"Describe a failure."

Choose a technical or project decision you can analyze. Explain the assumption that failed, the signal you missed, how you contained impact and what changed in your engineering process afterward.

How to structure technical evidence

For every major resume bullet, prepare five layers of detail:

  1. one-sentence summary;
  2. process context;
  3. data and method;
  4. decision/trade-off;
  5. validation and lesson.

That lets you answer at the depth the interviewer needs without memorizing a speech.

Questions to ask the employer

Useful questions reveal the actual engineering work:

  • Which processes or lines would this role own?
  • Is the role weighted toward NPI, daily production support, continuous improvement or capital equipment?
  • Which metrics are the team's main constraints today?
  • How are responsibilities split between manufacturing engineering, quality, maintenance and controls?
  • What does a successful first six months look like?
  • Which process or product changes are coming next?
  • How much authority does the role have to change process parameters, tooling or control logic?

The answers help you understand whether the title matches the job you want.

Graduate interview questions

For graduates, expect more emphasis on projects and fundamentals:

  • Walk me through a manufacturing project.
  • How did you validate your data?
  • What tolerance or measurement issue did you face?
  • How would you improve a manual assembly?
  • What happens when a process variation increases?
  • How would you choose between two fixture concepts?
  • Describe a time your first technical approach failed.

You are not expected to invent plant experience. Show engineering judgment using the evidence you actually have.

Related content

Sources