How to Be an Excellent Quality Engineer (QE)

Quality Engineer (QE) — the builder of the quality management system (QMS), the resolver of quality issues, and the driver of continuous improvement.

A QE is not a "senior QC" but a professional role that uses engineering methods to solve quality issues.

Chapter One: Revisiting the Role of a QE

1.1 The Essential Differences Between QC and QE

Key Differentiation: QC answers "Is this product conforming?" QE answers "Is this process stable? Is this system complete?"

1.2 The Four Core Roles of a QE

Four Roles of a Quality Engineer (QE)

1.3 Growth Stages of a QE

Typical Path: QE Intern → Junior QE → Independent QE → Senior QE → Quality Expert → Quality Director (specific titles vary by company).

Chapter Two: Core Technical Competencies of a QE

2.1 Statistical Process Control (SPC) — The "Stethoscope" of a QE

2.1.1 In-depth Understanding of Basic Concepts

SPC is not just about "drawing a few control charts." An excellent QE's understanding of SPC should reach the following levels:

Common Cause vs. Special Cause

Common Cause — Inherent process variation (e.g., minor fluctuations in raw materials, routine environmental temperature changes)

• Characteristics: Stable, predictable, follows a normal distribution
• Responsibility: Management / System level
• Response: Improve process design (e.g., replace equipment, optimize parameters)

Special Cause — Variation caused by external factors (e.g., tool breakage, operator error, material batch issues)

• Characteristics: Unstable, unpredictable, does not follow a normal distribution
• Responsibility: On-site operation / maintenance level
• Response: Identify and eliminate specific causes

One of the Most Important Distinctions in Quality Management: Confusing common causes and special causes is the root of most quality failures. Attributing system issues to operators (treating common causes as special causes) or treating sudden issues as "just like that" (ignoring special causes as common causes) will not lead to good quality.

2.1.2 The "Eight Out-of-Control Tests" for Control Charts

Not just looking at whether it "exceeds the control limits"! An excellent QE must master the Western Electric (WE) Out-of-Control Tests:

Note on Test 8: Too good data can be problematic. If 15 consecutive points are all within Zone C, the data may have been "selected" or the measurement system may have issues.

2.1.3 Practical Application of Process Capability Indices

Understanding the Meaning Behind Cpk (Experience Reference)

Pitfalls in Practical Application:

1. Calculating Cpk directly for non-normal data is incorrect — use Box-Cox transformation, Johnson transformation, or non-normal capability indices (e.g., Cpmk, CpQ)
2. Within-group variation vs. total variation — Cp/Cpk use within-group σ (R-bar/d2 or S-bar/c4), Pp/Ppk use total σ. If Cp is much greater than Pp, it indicates significant between-group variation (batch-to-batch instability)
3. High Cpk does not mean a good process — if the control chart is out of control, the capability index is invalid
4. Sample size must be sufficient — at least 25 subgroups, more than 100 data points

2.2 Measurement System Analysis (MSA) — The "Calibration Ruler" of a QE

A QE not only needs to know how to use MSA but also how to determine if the measurement system meets the requirements.

2.2.1 Gauge Repeatability and Reproducibility (GR&R)

Formulas (Illustrative)

• GR&R = √(EV² + AV²) — Total measurement system variation (equipment variation + personnel variation)
• %GR&R = (GR&R / total variation) × 100%

Judgment Criteria

Common Issues in Practical Application:

What Can a QE Do?

• When %GR&R is between 10-30%, evaluate the "correction" effect of the measurement system on process capability
• When MSA is nonconforming, don't just "sum up the references," but find the root cause — replace the gauge if the gauge accuracy is insufficient, standardize methods if personnel variation is large
• The most important aspect of MSA is "acceptability," not just "≥10%"

2.2.2 Hypothesis Testing and Measurement Systems

A good QE will use hypothesis testing to analyze issues:

• Null Hypothesis H₀: No significant change in the process mean before and after improvement
• Alternative Hypothesis H₁: Significant change in the process mean before and after improvement
• t-test: Compare whether the means of two data sets are significantly different
• Analysis of Variance (ANOVA): Compare three or more data sets
• Chi-square Test: Compare count data (conforming / nonconforming rates, etc.)

Case: Verify the Effectiveness of Improvement Measures

• Before improvement: 50 samples, mean = 10.05 mm, standard deviation = 0.03 mm
• After improvement: 50 samples, mean = 10.01 mm, standard deviation = 0.02 mm
• Question: Is the 0.04 mm difference a real improvement or just random fluctuation?
• Approach: Two-sample t-test, resulting in p-value = 0.002 (< 0.05)
• Conclusion: The improvement is significant, the mean has indeed decreased

2.3 Failure Mode and Effects Analysis (FMEA) — The "Early Warning Radar" of a QE

2.3.1 Types of FMEA

2.3.2 Core Logic of PFMEA

PFMEA Thought Process (for Each Process Step)

1. What could go wrong? (Failure Mode)
2. What would be the consequences? (Failure Effects)
3. Severity S (1～10)
4. What is the cause? (Failure Cause)
5. Occurrence O (1～10)
6. What controls are currently in place? (Prevention + Detection)
7. Detection D (1～10)
8. RPN = S × O × D (common in older versions; newer versions focus on Action Priority, see below)
9. Rank by risk → Develop improvements for high-risk items → Re-evaluate S/O/D (and new requirements for Action Priority)

Key Thinking of an Excellent QE:

1. Failure modes with S severity > 8 must be prioritized regardless of RPN (safety/legislation related)
2. Detection D is where a QE can add the most value — the inspection methods you design determine whether you can catch the failure
3. Control measures should be divided into "prevention" and "detection":
   • Prevention (Prevention): Poka-Yoke > SPC control > first article inspection > patrol inspection > training
   • Detection (Detection): 100% online inspection > automatic inspection > manual inspection > statistical sampling > visual inspection
4. FMEA is a living document — it must be updated whenever an anomaly occurs, the process changes, or new equipment is added
5. FMEA and control plans are a pair — high-risk failure modes in FMEA must have corresponding control measures in the control plan

2.3.3 Changes in FMEA under the New AIAG-VDA Standard

New version (2019 AIAG & VDA FMEA Manual):

Practical Points: Don't get stuck on RPN numbers. The new FMEA version removes the RPN threshold to avoid mechanical execution like "RPN=99, no action; RPN=101, immediate action."

2.4 Design of Experiments (DOE) — The "Engineering Weapon" of a QE

DOE is a hallmark capability that distinguishes an excellent QE from an ordinary one. You don't need to be an expert in complex full factorial designs, but you should at least understand the following concepts.

2.4.1 When to Use DOE?

Consider DOE when you need to answer the following questions:

2.4.2 Overview of Common DOE Types

2.4.3 Standard DOE Process

① Define the Problem and Objectives

• Clearly define Y (response variable): What is it? How is it measured? Is it repeatable?
• Clearly define X (factors): List all parameters that may affect Y

② Screen Factors

• Fishbone diagram + C&E matrix + expert judgment
• Quick screening with fractional factorial experiments

③ Determine the Experimental Design

• Number of factors, levels (high/low), center points
• Block design (whether to batch)
• Randomization (eliminate unknown biases)

④ Execute the Experiments

• Follow the randomization sequence
• Strictly record environmental conditions
• Avoid unplanned changes

⑤ Analyze the Data

• Effects plot (Pareto of Effects)
• Normal probability plot (determine significant effects)
• Analysis of variance (ANOVA)
• Residual analysis (validate model assumptions)

⑥ Verification and Confirmation

• Conduct confirmation experiments under optimal conditions
• Compare predicted values with actual values

DOE Golden Rule: Do not proceed to the next step until the current step is completed. Factor selection is more important than analysis tools — "Garbage in, garbage out."

Chapter Three: Engineering Methodology for Problem Solving

3.1 8D Problem Solving Method at the QE Level

8D is not just filling out forms — each stage has its own "hidden skills" for a QE.

D2 Problem Description

Common Practice: "Product has scratches" Excellent QE Practice (IS / IS NOT Matrix):

Tool: IS/IS NOT Matrix — this is a "exhaustive elimination method" before DOE screening

D4 Root Cause Analysis

Three Levels of Root Cause (Example)

5Why Requirement for an Excellent QE:

• Each "why" must be supported by data or facts, not guesses
• At least reach the third level (system level), don't stop at the surface level
• If the final issue is a "human" problem → continue asking "why did the person do this? Is it due to insufficient training? Unclear SOP? Or management deficiencies?"

D5-D6 Corrective and Verification Actions

Characteristics of Permanent Corrective Actions (PCA):

1. Can eliminate the root cause (not just control the consequences)
2. Can be horizontally deployed to similar products/processes
3. Have clear verification indicators and verification cycles
4. Mechanisms to prevent recurrence (update FMEA, control plan, standardization)

Methods to Verify the Effectiveness of Actions:

• Hypothesis testing before and after improvement (p-value < 0.05 is considered effective)
• Process capability comparison before and after improvement (Cpk from 0.8 to 1.33)
• Control chart monitoring (no recurrence in the following three months)

3.2 Classification and Escalation Mechanism for Quality Issues

An excellent QE will establish a tiered response mechanism:

3.3 Quality Cost (COQ) — The "Economic Account" of a QE

An excellent QE not only views quality issues from a technical perspective but also quantitatively analyzes them from an economic perspective.

Components of Quality Cost

Quality Cost = Prevention Cost + Appraisal Cost + Internal Failure Cost + External Failure Cost

Quality Cost 1 : 10 : 100 Rule (Illustrative Magnitude)

Value Proposition of a QE:

• Don't just say "quality is important"
• Say "adding a poka-yoke device at this process step, with an investment of 2000 yuan, is expected to reduce rework losses by 8000 yuan annually — ROI=300%"
• Use the "language" of quality cost to communicate with finance/management

Chapter Four: Deep Involvement in the Quality System

4.1 QE and ISO 9001:2015

An excellent QE is not just "implementing the system" but can understand and drive the implementation of the system.

4.2 Internal Audits — The "Health Check Doctor" of a QE

An excellent QE is often an excellent internal auditor. But not just to "find problems," but to "help the system improve."

Efficient Audit Thinking of a QE:

Before the Audit

• Understand the quality data of the department to be audited over the past three months (customer complaints, nonconforming products, CAPA)
• Prepare a "risk-based audit path" (ask questions based on risk points, not just mechanically follow clauses)

During the Audit

• Ask fewer hypothetical questions (e.g., "What would you do if a nonconforming product appeared?")
• Ask more verification questions (e.g., "When was the last nonconforming product? Show me the handling records")
• Don't believe in "verbal systems," rely on random sampling (e.g., "Can I see the patrol inspection records from that afternoon?")
• Combine observation, interviews, and document reviews

After the Audit

• Nonconformities should have management significance, not just "clause mismatches"
• Each nonconformity must have a root cause analysis and a corrective action plan
• Follow up until closure

4.3 CAPA System (Corrective and Preventive Actions)

CAPA is the "brain" of the quality system — a system that can form a closed-loop improvement after identifying issues.

Typical CAPA Chain

1. Awareness
2. Evaluation — severity, impact scope, urgency
3. Containment — immediate loss prevention (100% screening, traceability, recall, etc.)
4. Root Cause Analysis — 8D, 5Why, fishbone diagram, etc.
5. Corrective Action (CA) — eliminate the root cause of the current nonconformity
6. Preventive Action (PA) — prevent similar issues from recurring in other areas
7. Verification — use data to prove the effectiveness of the measures
8. Standardization — update documents, horizontal deployment

Common Pitfalls in CAPA:

• Only doing CA and not PA (treating symptoms, not the root cause)
• Too short verification cycle (one week's data cannot prove "it won't happen again")
• No horizontal deployment (fixing one line but not the similar other line)
• Closing CAPA without closure (must see verification data to close)

Knowledge code: 13.2.1
Version: v20260502
Author: QTank

Chapter 5: Practical Training in Soft Skills

5.1 Building Cross-Departmental Influence

A Quality Engineer (QE) does not have direct management authority but needs to drive improvements in other departments—influence is more important than authority.

Three Levels of Influence Building:

Level One: Professional Trust

• Others' Perception: "This QE is very professional; I believe the issues he raises."
• Building Method: Accurate data, thorough analysis, no empty talk

Level Two: Collaborative Value

• Others' Perception: "Working with this QE, problems can be solved, and efforts won't be wasted."
• Building Method: Bring solutions to meetings, take responsibility, continuous follow-up

Level Three: Strategic Contribution

• Others' Perception: "This QE can see issues and opportunities that we cannot."
• Building Method: Anticipate quality risks, communicate with management using quality costs

5.2 The "Seven Steps" to Drive Improvement

1. Identify the Problem — Use data to prove the severity (e.g., quality loss amount)
2. Find the Root Cause — Systematic analysis using 8D, 5Why, FMEA, etc.
3. Develop Solutions — At least 2-3 options, with ROI labeled
4. Gain Support — Align with key stakeholders (production supervisors, process engineers, etc.)
5. Pilot Verification — Small batch or short-term trial runs, collect comparative data
6. Full Implementation — Standardize, update documents, provide training
7. Sustain Results — Continuous monitoring using control charts, regular reviews

5.3 Structured Expression for Upward Reporting

Quality reports for directors or general managers should not be a pile of data but a decision-making tool.

Suggested Structure for Monthly Quality Reports

First Page: Quality Dashboard — Readable within about 1 minute

• Customer complaint trends (red / yellow / green status)
• Batch pass rate (target vs. actual)
• Quality cost trends (amount)
• Summary of major anomalies (no more than 3 items)

Second Page: Key Issues Analysis for the Month

• Top 3 quality issues (ranked by Pareto chart)
• Root cause for each issue (one sentence + analysis path)
• Improvement plans and progress

Third Page: Matters Requiring Decision

• Approved investments (e.g., new gauges, renovation costs)
• Cross-departmental decisions to be pushed
• Risk warnings to be escalated to higher levels

Principle: One topic per page, lead with conclusions, support with data, and provide clear recommendations.

5.4 Cultivating Quality Awareness on the Front Line

An excellent QE is not just about being highly capable themselves but also about making those around them stronger.

Chapter 6: Digital Skills for QEs

6.1 Mastery of Data Analysis Tools

6.2 Digital Quality Management

Digital Directions an Excellent QE Should Promote:

1. Automatic inspection data collection (digital gauges, barcode scanners)
2. Real-time quality KPI dashboard (Power BI / JianDaoYun / FeiShu multidimensional tables)
3. Electronic workflow for nonconforming product handling (OA or MES system nonconforming product process)
4. Structured quality issue database (no longer scattered emails but a structured case library)
5. Automated control charts (SPC software replacing manual plotting)

Chapter 7: Daily Habit System for Excellent QEs

7.1 Daily Must-Dos

7.2 Weekly Must-Dos

• Weekly Quality Data Report (Pareto chart + trend analysis + anomaly summary)
• Review Ongoing CAPAs (current status of each CAPA + bottlenecks)
• Front-Line Training and Coaching (at least one in-depth learning session with QC or production line personnel)
• Next Week's Improvement Plan (determine priorities for the next week)

7.3 Monthly Must-Dos

• Monthly Quality Cost Report (provide decision-making basis for management)
• Review and Update Control Plans (any process or equipment changes this month?)
• Dynamic Update of FMEA (any anomalies this month that need to be reflected in the FMEA?)
• Six Sigma / Improvement Project Progress Report
• Self-Assessment Once: How many systemic issues did I resolve this month? How many were one-time fixes?

Final Words: Twelve Guidelines for Excellent QEs

1. Quality is not inspected or shouted into existence; it is designed and controlled.
2. SPC is a stethoscope, FMEA is a CT scanner, and 8D is a scalpel—know how to use the tools and how to choose them.
3. After solving each quality issue, ask yourself: "Is the root cause of this issue systemic?"
4. Data does not lie, but it can be misleading—understand the measurement system and sampling methods behind the data.
5. The root cause of quality issues is almost never just one thing, but there is always one that is the most fundamental.
6. Cpk is a measure of process capability, not a product inspection result—do not use sampling inspection as a substitute for process control.
7. The value of a QE lies not in "how many issues they find" but in "how many issues they prevent."
8. In the face of delivery pressure, a QE is the guardian of quality—not a rubber-stamp machine.
9. Training front-line staff is more important than doing it yourself—quality is everyone's responsibility.
10. A system is not just theoretical—every clause corresponds to actual control points.
11. Digitalization is not the goal but a tool—use better tools to make better decisions.
12. Quality is a systems engineering effort—pursue continuous improvement, not perfection.

Four-Word Guiding Principles for Excellent QEs:

Understand (technology, systems, processes) Master (analysis, tools, data) Document (FMEA, 8D, reports) Communicate (facts, data, conclusions)

Understanding is the foundation, mastery is the capability, documentation is the deliverable, and communication is the influence.

Knowledge code: 13.2.1 Document Version: v1.0 Generated Date: 2026-05-02 Author: QTank

Complementary Training Materials: QE Empowerment Training—Comprehensive Practical Guide for QC to QE Transition (Complete PPT · 113 pages) — 113-page standard template courseware from the QTank, covering the transition from QC to QE, competency models, core APQP tools, 8D/Seven Tools/SPC, supply chain and customer quality, 90-day transition plans, and workshop exercises, suitable for 2-3 days of intensive training and internal trainer instruction.