Quality Assurance Interview Questions and Scorecard
Six question sets for the owner or manager running the interview: core QA, manufacturing and inspection, customer service QA, process and audit, a graded write-up exercise, and a scoring rubric with red flags. Download as DOCX.
The first quality hire I watched a small manufacturer make was a disaster, and not because the person was bad at the job. The owner interviewed for attention to detail, liked a careful, quiet candidate, and hired. Six months later the company was catching more defects and shipping the same number, because nobody had ever asked the candidate how they change a process.
Quality assurance is the one hiring decision where the obvious interview is the wrong interview. Detection questions are easy to ask and easy to answer. The questions that predict the hire are about prevention, risk, root cause, and what the person does when someone senior tells them to release an order they have flagged.
At FirstHR, we build for companies that hire without an HR department, where the owner or the operations lead runs the interview alone. These six sets are written for that reader. Every question carries a note on what a good answer sounds like, and there is a graded written exercise you can score without a quality background of your own.
TL;DR
Interview a quality assurance candidate on four things: prevention versus detection, risk-based judgment about what to check, root cause discipline, and whether they hold a decision under pressure. Ask the same set of every candidate, run one 20-minute write-up exercise graded against a checklist, and score six areas from 1 to 5 immediately afterward. Download six question sets and the scorecard as DOCX.
What You Are Actually Hiring For
You are hiring someone to stop problems from reaching a customer, which is a different job from finding problems after they exist. That distinction, prevention versus detection, is the single most useful line in the whole interview, and it is the one most generic question lists never draw.
In practice, four capabilities predict success in the role. Whether the candidate changes processes or only sorts output. Whether they can rank risk when checking everything is impossible. Whether they find causes rather than symptoms. And whether they will hold a call when production is behind and a manager wants the order out the door.
Everything else, the tools, the standards, the software, can be taught to a candidate who has those four. The reverse is not true. Someone who knows every acronym and defers on every judgment call will give you a well-documented record of the defects you shipped.
Which Kind of QA Are You Hiring?
Quality assurance covers at least four different jobs that share a name, so decide which one you are filling before you write the interview. A manufacturing inspector and a support-quality reviewer both do QA, and almost none of their day-to-day work overlaps.
Product and manufacturing QA
Inspects parts, batches, and finished goods
Works from drawings, specs, and tolerances
Owns nonconformances and corrective actions
Process and system QA
Writes and controls procedures
Runs internal audits and training records
Keeps the operation audit ready
Service and support QA
Scores calls, chats, and tickets
Runs calibration between reviewers
Turns findings into coaching
Software QA
Tests features and writes bug reports
Plans coverage under release pressure
May automate part of the suite
If the role is software testing specifically, use the QA engineer interview questions instead; the sets on this page cover the operational and service side of quality in more depth. If you have not written the posting yet, the quality assurance job description templates split the role the same way, by industry.
The standard your operation works under shapes the questions as well. General manufacturers and service businesses usually work to ISO 9001, food operations to the seven HACCP principles published by the FDA, and device or drug makers to current good manufacturing practice rules. Ask what the candidate personally did inside the standard rather than whether they can name it.
Name the Role Before You Name the Questions
The fastest way to run a bad quality interview is to interview for a generic QA person. Write down, in one sentence, what this hire will own in six months: inspecting product, owning procedures and audits, reviewing service interactions, or testing software. That sentence tells you which set below to use, what level to pay for, and what the written exercise should look like.
Which Question Set Should You Use?
Start with the core set for every candidate, then add the one that matches your operation. The exercise and the rubric work with any combination. Ask the same sets in the same order of every candidate for the same role, which is what makes the comparison fair.
Core QA Questions
Every candidate
The starting set for any quality hire in any industry: prevention versus detection, risk-based checking, root cause, escalation, and standards. Start here.
Manufacturing and Inspection
Parts and product
For a floor or warehouse role: measuring tools, reading a spec, sampling plans, nonconformance handling, corrective actions, supplier issues, and calibration.
Customer Service QA
Calls, chats, tickets
For a service or call-center reviewer: scorecards, sample size, calibration sessions, disputed scores, and turning findings into coaching instead of punishment.
Process, Audit, Documents
Owns the system
For a specialist or manager who will own procedures, document control, internal audits, training records, and readiness for a customer or regulatory audit.
Write-Up Exercise
Work sample
A 20-minute nonconformance scenario with a 12-point grading checklist. The single most useful stage, and one you can grade without a quality background.
Rubric, Levels, Red Flags
Score and decide
A six-area scorecard, a guide to what inspector, specialist, and manager answers sound like, and a red-flag list so you compare candidates on evidence.
6 Free QA Question Sets to Download
Download all six as one Word document, or copy the sets you need. Each follows the same structure: when to use it, the questions with good-answer notes, what to listen for, and space for notes. The exercise adds a scenario and a grading checklist; the rubric adds scoring areas, a seniority guide, and red flags.
Download All 6 Quality Assurance Question Sets
Core, manufacturing, customer service, process and audit, a graded write-up exercise, and a scoring rubric with red flags. All in one DOCX.
Set 1: Core Quality Assurance Questions
The starting set for any quality hire in any industry: prevention versus detection, risk-based checking, root cause, escalation, standards, and documentation. Nine questions, each with what a good answer contains.
Core Quality Assurance Interview Questions
CORE QUALITY ASSURANCE INTERVIEW QUESTIONS
Candidate: __
Company: __
Interviewer: __
Date: _
HOW TO USE THIS SET
Ask these of every quality candidate, whatever the industry: manufacturing,
food, services, or a support team. Pick 7 to 9 for a 45-minute conversation.
The note in parentheses describes what a good answer sounds like, so you can
judge the response without a quality background yourself. Score at the end
while the conversation is fresh, and ask the same questions of every candidate.
QUESTIONS
1. In your own words, what is quality assurance, and how is it different from
quality control?
(Good answer: assurance builds and monitors the process so defects do not
happen; control checks the output and catches the ones that do. Says both
are needed and gives an example of each from their own work.)
2. Walk me through your first two weeks here. How would you find out where our
quality risks are?
(Good answer: reads the specs and the complaint history, watches the work
being done, talks to the people doing it, then ranks risk. A candidate who
arrives with a finished plan before seeing the operation is guessing.)
3. Tell me about a defect or an error that reached a customer. What did you do?
(Good answer: contained it first, then found the cause, then changed the
process. Owns their part of it instead of naming the person who erred.)
4. You cannot check everything. How do you decide what gets checked?
(Good answer: risk based. Highest customer impact, newest change, and the
steps with a history of failure come first, with a stated sampling logic.)
5. Describe how you find the root cause of a problem that keeps coming back.
(Good answer: names a method they actually use, such as five whys or a
fishbone diagram, starts from data, and separates cause from symptom.)
6. A supervisor tells you to release an order you have flagged. What do you do?
(Good answer: states the facts and the risk, offers options, escalates
through a known path, and documents the decision and who made it. Neither
caves quietly nor turns it into a fight.)
7. How do you write up a problem so that someone can act on it?
(Good answer: what, where, when, how many, evidence, severity, and the
action requested. Plain language, no blame of an individual.)
8. Which quality standards or systems have you worked under?
(Good answer: names the standard, for example ISO 9001, HACCP, or cGMP, and
describes what they personally did inside it, not just the acronym.)
9. What would you want to know about our product before you started?
(Good answer: asks about customers, complaint history, tolerances, and the
steps that hurt most. A candidate with no questions is a warning sign.)
WHAT TO LISTEN FOR
•Prevention thinking: fixes the process, not just the bad unit
•Risk judgment: can rank what matters instead of checking everything equally
•Evidence habits: specific numbers, lots, dates, and records, not "it was bad"
•Backbone: will hold a decision under pressure and escalate on facts
•Plain language: explains a quality problem to someone outside the department
QUICK SCORE (1 = no evidence, 5 = strong, specific evidence)
Root cause and problem solving [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Documentation and communication [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
NOTES
__
__
Set 2: Manufacturing and Inspection Questions
For a hands-on role on a floor or in a warehouse: measuring tools, reading a spec, sampling plans, what happens in the hour after a failed inspection, corrective actions, supplier issues, and calibration.
Manufacturing and Inspection QA Questions
MANUFACTURING AND INSPECTION QA INTERVIEW QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
Use this set for a hands-on quality role on a production floor, in a warehouse,
or in a food or device operation: inspector, quality technician, or quality
specialist. Ask these alongside the core set. Bring one of your own drawings,
specs, or labels to the interview and use it as a prop for question 2.
QUESTIONS
1. Which measuring tools have you used, and what do you check with each?
(Good answer: names the tools, for example calipers, micrometers, gauges, or
a coordinate measuring machine, and matches them to real features.)
2. Here is one of our specs. How would you turn it into an inspection plan?
(Good answer: picks out critical dimensions or attributes, reads tolerances,
states a sample size and a frequency, and says what triggers a stop.)
3. What sampling plan have you used, and how did you choose the sample size?
(Good answer: a written plan or an AQL table, not a habit. Can explain the
tradeoff between inspection cost and escaped-defect risk.)
4. A part fails inspection. Walk me through the next hour.
(Good answer: quarantine and tag the material, define the scope, which lot
and since when, write the nonconformance, notify production, then get a
documented disposition of rework, scrap, or use as is with approval.)
5. Walk me through a corrective action you ran all the way to closure.
(Good answer: containment, root cause, the action taken, and a verification
step that proves the problem stopped. Weak answers end at the fix.)
6. Incoming material from a supplier fails. What do you do?
(Good answer: documents it, notifies purchasing and the supplier, requests a
corrective action, and tracks repeat offenders rather than re-sorting alone.)
7. How do you keep records so a customer or an auditor can follow them?
(Good answer: dated, legible, and traceable to a lot, batch, or serial
number. Understands that an unrecorded check did not happen.)
8. What is calibration, and how have you managed it?
(Good answer: a schedule, due dates, and a plan for what happens to product
already checked when an instrument is found out of tolerance.)
9. How do you raise a quality problem to a production manager under deadline?
(Good answer: leads with the customer risk and the numbers, brings options
and cost, and does not make it personal.)
WHAT TO LISTEN FOR
•Reads a spec confidently and talks in tolerances, not opinions
•Contains first, investigates second: the order matters
•Treats records as part of the job rather than paperwork after the fact
•Thinks about suppliers, not only about what is already in the building
NOTES
__
Still Using Spreadsheets for Onboarding?
Automate documents, training assignments, task management, and track onboarding progress in real time.
Set 3: Customer Service and Call Center QA Questions
For a reviewer who scores calls, chats, or tickets: scorecard design, sample size and why, calibration sessions, disputed scores, and turning findings into coaching rather than a disciplinary file.
Customer Service and Call Center QA Questions
CUSTOMER SERVICE AND CALL CENTER QA INTERVIEW QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
Use this set when the quality hire will review calls, chats, tickets, or
service visits rather than parts. The job is scoring interactions against a
rubric, spotting patterns, and turning findings into coaching. Ask these
alongside the core set.
QUESTIONS
1. Walk me through a scorecard you have used to evaluate interactions.
(Good answer: named criteria with weights, tied to customer outcomes such as
resolution and accuracy, not just tone and greeting scripts.)
2. How many interactions per person per month did you review, and why that many?
(Good answer: a defensible sample they can explain, adjusted for new hires
and for people on a coaching plan. A number with no reasoning is a guess.)
3. What is a calibration session, and how do you run one?
(Good answer: several reviewers score the same interaction independently,
compare scores, and tighten the criteria where they disagreed.)
4. An agent disputes your score. Walk me through what happens.
(Good answer: goes back to the recording and the written criteria, explains
the standard, and will change the score when the evidence says so.)
5. How do you turn a QA finding into coaching instead of punishment?
(Good answer: one or two focus behaviors, a specific example the person can
hear, a follow-up review, and credit when it improves.)
6. Tell me about a time your QA data changed the process, not just one score.
(Good answer: found a pattern and fixed the script, the policy, the macro,
or the training, then measured whether the pattern went away.)
7. You will be the only reviewer here. How do you keep your scoring consistent?
(Good answer: written definitions with example clips, periodic re-scoring of
their own earlier samples, and openness to a second reviewer spot-check.)
8. What would you look at first in our support queue?
(Good answer: repeat contacts, escalations, and the interactions that ended
in a refund or a lost customer, because that is where the money is.)
WHAT TO LISTEN FOR
•Scores against written criteria, not personal taste
•Separates the interaction from the person while giving feedback
•Looks for patterns across agents, not only individual scores
•Comfortable being the single reviewer without becoming the single opinion
NOTES
__
Set 4: Process, Audit, and Documentation Questions
For a specialist or manager who will own the quality system: writing procedures people follow, document control, internal audits, training records, and readiness for a customer or regulatory audit.
Process, Audit, and Documentation QA Questions
PROCESS, AUDIT, AND DOCUMENTATION QA INTERVIEW QUESTIONS
Candidate: __
Company: __
Interviewer: __
WHEN TO USE THIS SET
Use this set when the hire will own the quality system itself: procedures,
document control, internal audits, and readiness for a customer or regulatory
audit. This is the set for a quality specialist or quality manager, and it is
the one small businesses most often skip and later regret.
QUESTIONS
1. How do you write a procedure that people actually follow?
(Good answer: short, written in the words of the person doing the job, with
the reason for each step and a built-in check. Written with the operator,
not at a desk alone.)
2. How do you control documents so everyone is using the current version?
(Good answer: one controlled location, version numbers, old copies pulled,
and a record that affected people were trained on the change.)
3. Walk me through an internal audit you ran, from scope to follow-up.
(Good answer: a scope and plan, evidence sampled rather than everything,
findings written against a specific requirement, agreed actions with owners
and dates, then verification that the action worked.)
4. How do you write a finding so it is factual rather than personal?
(Good answer: cites the requirement, states the observed evidence, avoids
naming the individual, and describes the risk in business terms.)
5. The written procedure and the way the work is actually done do not match.
What do you do?
(Good answer: finds out why first. Sometimes the floor is right and the
procedure is wrong. Fixes whichever one is wrong instead of only rewriting
the paper or only blaming the crew.)
6. How do you get ready for a customer or regulatory audit?
(Good answer: records complete and retrievable, people know what they own,
open corrective actions closed or explained. No week-long scramble.)
7. How do you track who is trained on which procedure and version?
(Good answer: a simple matrix tied to the document version, kept current,
with retraining triggered when a procedure changes.)
8. What is a deviation, and how have you handled one?
(Good answer: an approved, documented departure from the procedure with a
risk assessment, not a quiet workaround discovered later.)
WHAT TO LISTEN FOR
•Writes for the person doing the work, not for a binder
•Audits against requirements and evidence, not personalities
•Treats the gap between written and actual practice as information
•Keeps the system small enough that a small business can maintain it
NOTES
__
Companies Using FirstHR Onboard 3x Faster
Join hundreds of small businesses who transformed their new hire experience.
A 20-minute scenario with a 12-point grading checklist and a score interpretation. Hand it to every candidate, grade it the same way, and compare. The most informative stage in the process.
Nonconformance Write-Up Exercise
NONCONFORMANCE WRITE-UP EXERCISE (20 MINUTES)
Candidate: __
Company: __
Interviewer: __
HOW TO RUN IT
Give the candidate the scenario below, paper or a laptop, and 20 minutes alone.
Ask for two things: what they do in the first hour, and the written report they
would file. Then spend 10 minutes asking why they made each call. Grade with
the checklist. This stage tells you more than any answer to any question, and
you can grade it without a quality background of your own.
Swap the scenario for one from your own operation if you have a real past case.
Use the same scenario and the same checklist for every candidate.
SCENARIO (READ OR HAND OVER)
You are the quality specialist. It is 2 p.m. A packer finds that three units
out of a finished pallet of 200 are labeled with the wrong product code. The
pallet was built this morning. The same line ran two earlier orders today, and
one of them shipped at noon to your largest customer. The line is still
running. Production says the remaining order must ship tomorrow morning.
Write the nonconformance report and list what you do in the first hour.
GRADING CHECKLIST (CHECK EACH ITEM PRESENT)
[ ] Stops or holds the line before investigating anything
[ ] Quarantines and tags the pallet rather than leaving it in flow
[ ] Defines the scope: which orders, which time window, how many units
[ ] Recognizes the shipped order and raises customer notification
[ ] Records evidence: photos, label samples, lot or batch numbers, times
[ ] Separates immediate containment from root cause
[ ] Proposes a root cause path, for example a label changeover check
[ ] States a disposition and who has authority to approve it
[ ] Names who must be told and when: production, sales, the customer
[ ] Adds a verification step to confirm the fix worked
[ ] Writes in plain, factual language with no blame of an individual
[ ] Does not promise the shipment date before the scope is known
Score: ______ / 12
WHAT THE SCORE MEANS
10 to 12 Strong. Contains first, defines scope, and thinks past the pallet.
7 to 9 Solid. Coach the gaps; usually notification or verification.
4 to 6 Weak. Fixes the three units and stops there. Escaped defects follow.
0 to 3 No. Cannot structure a quality problem under time pressure.
NOTES
__
Set 6: Scoring Rubric, Seniority Guide, and Red Flags
A six-area scorecard with space for evidence, a guide to what inspector, specialist, and manager answers sound like, and a red-flag checklist. Use it with any set above.
Scoring Rubric, Seniority Guide, and Red Flags
QUALITY ASSURANCE SCORING RUBRIC, SENIORITY GUIDE, AND RED FLAGS
Candidate: __
Company: __
Interviewer: __
Date: _
HOW TO SCORE
Score each area from 1 to 5 right after the interview, while it is fresh, and
anchor every score to something the candidate actually said. If more than one
person interviews, each scores independently before anyone discusses. Use the
same rubric for every candidate for the role.
Rating scale:
5 = Strong, specific evidence 4 = Solid evidence 3 = Some evidence
2 = Weak or mixed evidence 1 = No evidence or red flags
SCORING AREAS
Standards and technical knowledge: the standards, tools, and checks of your work
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Risk judgment: ranks what to check when checking everything is impossible
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Root cause and problem solving: finds causes, not just symptoms
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Documentation: records and reports someone else can act on and audit
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Independence and escalation: holds a call under pressure, escalates on facts
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Communication and coaching: explains a problem without making it personal
Score [ 1 ] [ 2 ] [ 3 ] [ 4 ] [ 5 ]
Evidence: ______
Written exercise score: ______ / 12
SENIORITY GUIDE: WHAT EACH LEVEL SOUNDS LIKE
INSPECTOR OR QUALITY TECHNICIAN
Runs the checks accurately and records them. Knows the tools and the specs.
Escalates rather than deciding disposition alone. Depth over breadth is fine.
QUALITY SPECIALIST OR ANALYST
Designs the checks, not only runs them. Owns nonconformances and corrective
actions to closure, writes procedures, and can face a customer complaint.
QUALITY MANAGER
Owns the system: audits, document control, supplier quality, training, and the
metrics leadership sees. Can build the function from very little and hire into
it. Should be able to say what they would drop, not only what they would add.
RED FLAGS (WEIGH CAREFULLY)
[ ] Cannot describe a single specific defect or complaint from past work
[ ] Talks only about catching defects, never about preventing them
[ ] Blames operators or agents for every problem they describe
[ ] Wants to inspect or review everything, with no sense of cost
[ ] Ends every story at the fix, with no verification that it held
[ ] Vague about standards they claim on the resume
[ ] Would release flagged product because a manager asked, with no record
[ ] Treats documentation as someone else's job
DECISION
Total rubric score: ______ / 30 Exercise: ______ / 12
The Core Questions and Why Each One Earns Its Place
Every question below is on the list for a specific reason, and none of them can be answered well from a script. If a question in your own interview does not have a reason attached, cut it and use the time for a follow-up instead.
Question
Why it is worth asking
What a strong answer contains
How is QA different from QC?
Separates system builders from sorters
Both defined, one example of each from their work
Your first two weeks here
Tests whether they look before prescribing
Reads specs and complaints, watches the work, then ranks risk
A defect that reached a customer
Real ownership shows up here or nowhere
Contained, found the cause, changed the process, owns their part
A named method, data first, cause separated from symptom
Told to release a flagged order
Predicts behavior on your worst day
States facts and options, escalates, documents the decision
How you write a problem up
Reports are the output of the job
What, where, when, how many, evidence, severity, action requested
Standards you have worked under
Filters resume acronyms
Names it and describes what they personally did inside it
Two follow-ups do most of the work. Ask what happened four weeks later, which tests verification, and ask what it cost, which tests whether they understand that quality competes with throughput. Candidates who have owned the function answer both without hesitating.
Judging Answers Without a Quality Background
You do not need to grade the technical content. You need to tell a specific, evidence-based answer from a rehearsed one, and the pattern is consistent enough that a non-specialist can hear it. Strong answers have numbers, sequence, and an admission somewhere in them.
What is the difference between quality assurance and quality control?
Strong answer: Assurance is the process that keeps defects from happening: procedures, training, supplier controls, and checks built into the work. Control is the inspection that catches what still slips through. A strong answer says both are needed, gives one example of each from their own experience, and does not treat inspection as the whole job.
Weak answer: A weak answer recites a textbook line, treats the two as the same thing, or describes a career of only sorting good units from bad ones.
A supervisor tells you to release an order you have flagged.
Strong answer: States the facts and the customer risk plainly, offers options such as a full sort or a partial shipment, escalates through a known path, and records the decision and who made it. A strong candidate is calm about it and treats the record as protection for everyone, including the supervisor.
Weak answer: A weak answer either releases the order to keep the peace with no record, or turns the disagreement into a standoff with no options offered.
Walk me through a corrective action you ran to closure.
Strong answer: Containment first, then a root cause found from evidence, then the action taken, then a verification step weeks later that proves the problem stopped. A strong answer names the method used to find the cause and admits what the first theory got wrong.
Weak answer: A weak answer ends at the fix. If there is no verification step, they have been closing tickets rather than solving problems, and the same defect usually comes back.
Push for specifics whenever an answer stays general: how many units, which lot, what the customer said, what changed afterward. A candidate with real operating history produces those details easily, and one who has been adjacent to quality work runs out of them by the second follow-up.
This is also where attention-to-detail questions pull their weight, as long as you treat them as a supplement. Detail orientation matters in this role, but on its own it describes a careful inspector, not someone who will keep defects from being made in the first place.
The Nonconformance Write-Up Exercise
Give every candidate the same 20-minute scenario and grade the result against the same checklist. This is the single most informative stage in a quality interview, and unlike the technical questions, it requires no quality background from you to score, only the ability to check whether each element is present.
The scenario in Set 5 puts a labeling error on a finished pallet, with one earlier order already shipped and a deadline in the morning. The write-up shows you how the candidate thinks under time pressure, which is the condition the job is actually done in.
What you are looking for
Why it matters
Holds the line before investigating
Every minute of delay adds units to the problem
Quarantines and tags the affected stock
Untagged suspect product finds its way back into flow
Defines scope: which orders, what window
Three bad units are a symptom, the scope is the risk
Raises the order that already shipped
The escape is the expensive part, not the pallet in front of them
Separates containment from root cause
Confusing the two produces a fix that does not hold
Adds a verification step
Without it, nobody ever learns whether the fix worked
Keep the exercise short, job-related, and identical for everyone, and grade it with the written checklist rather than an impression. Consistency is what makes a practical test useful, and it is also what keeps the decision defensible if a rejected candidate ever asks how it was made.
Red Flags in a QA Interview
Most weak quality candidates fail in the same four ways, and all four are audible in the first half hour if you know what you are listening for. None of them is disqualifying on its own; two or more in the same conversation usually is.
No specific defect they can describe
Someone who has run quality remembers the interesting failures. If every example is generic, they may have watched a quality process rather than owned one.
Catching, never preventing
A candidate who only talks about finding bad units will build you an inspection habit, not a quality system. Listen for a process change in at least one story.
Blames the operators or agents
Most defects come from the way the work is set up. A candidate who builds a case against colleagues will not get cooperation on your floor or in your queue.
Ends every story at the fix
No verification means no proof the problem stopped. Ask what happened four weeks later. A blank look there is one of the most reliable signals in the interview.
One more is worth its own mention. A candidate who would release flagged product because a manager asked, with no record of who decided, is telling you exactly how the worst day of the year will go. You are not looking for defiance here. You are looking for facts, options, an escalation path, and a written record of who decided.
Scoring the Interview
Score every candidate on the same six areas immediately after the interview, while the answers are fresh, and anchor each score to something the person actually said. Written evidence is what lets you compare a candidate from Tuesday against one from Friday without relying on which conversation felt better.
Scoring area
What a 5 looks like
Standards and technical knowledge
Names the standard and what they did inside it
Risk judgment
Ranks checks by impact, change, and failure history
Root cause and problem solving
A method, data first, causes separated from symptoms
Documentation
Reports another person can act on and an auditor can follow
Independence and escalation
Holds the call, offers options, records the decision
Communication and coaching
Explains a problem without making it personal
If more than one person interviews, each scores independently before the group talks, so the most senior voice does not anchor everyone else. A shared interview evaluation form keeps the format identical across interviewers, and a short written interview feedback step turns the scores into a decision instead of a debate.
Fair, Legal, and Structured Interviewing
Asking every candidate the same job-related questions and scoring them on the same rubric is simultaneously the fairest, the most defensible, and the most accurate way to interview. That is the whole case for a structured interview, and it costs nothing except the discipline of preparing the questions in advance.
Structure Beats Impression
A structured interview, where every candidate answers the same questions scored against a consistent rubric, predicts on-the-job performance more reliably than an unstructured conversation, and keeping every question tied to the job is also how you stay inside the EEOC rules against decisions based on protected characteristics such as age, race, religion, national origin, disability, or family status.
Two practical cautions specific to quality roles. Physical requirements, such as lifting or standing on a production floor, belong in the job description as essential functions and should not turn into questions about a candidate's health or disability. And if you use a written exercise, give it to everyone in the same form, since a test used inconsistently is harder to defend than no test at all.
Keep the rest of the interview on the work itself: what they have done, how they decided, what happened next. Reviewing the list of questions employers cannot ask before your first interview takes ten minutes and prevents the small-talk mistakes that cause most problems. This is general information, not legal advice.
Quality Assurance Pay and Classification
Quality pay depends almost entirely on which quality job you mean, and the federal data separates them cleanly. Decide the level before you interview, because the difference between an inspector and a system owner is a different candidate pool, not a different number on the same offer.
Median $48,570 for Inspectors, $104,300 for Software QA
According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), inspectors, testers, sorters, samplers, and weighers had a median wage of $48,570 a year, about $23.35 an hour, with the lowest 10 percent under $35,510 and the highest 10 percent over $77,860 (BLS OEWS 51-9061). Software quality assurance analysts and testers, a separate occupation, had a median of $104,300 a year (BLS OEWS 15-1253).
Percentile
Inspectors, testers, sorters, samplers, weighers
10th
$35,510
25th
$39,890
Median
$48,570
75th
$61,440
90th
$77,860
Federal employment projections put roughly 69,900 openings a year in that inspector occupation over the 2024 to 2034 decade, mostly from replacement rather than growth, so you are usually competing with other employers for experienced people rather than choosing from a surplus. Pay at least the 50th percentile if you want someone who has closed a corrective action before.
Classification follows duties, not titles. Most inspection and hands-on quality roles are non-exempt and paid hourly with overtime, while a genuine quality manager may qualify for a white-collar exemption only if the role meets both the duties test and the federal salary threshold of $684 per week set by the U.S. Department of Labor. The exempt versus non-exempt distinction is worth settling before you post, and several states set a higher floor than the federal one. This is general information, not legal advice.
Hiring QA Without an HR Department
A large manufacturer hires quality people through a quality director who already knows what good looks like. A small business hires through an owner or an operations lead who knows the product cold and the quality profession not at all, usually while running everything else. That reality shapes what a good process looks like at your size.
You are hiring for quality, but nobody here has run a quality function
This is the normal case at a small company. The first quality hire is often made by an owner or an operations lead who knows the product well and the quality profession not at all. That is exactly why every question in these sets carries a note on what a good answer sounds like. You are not grading a technical exam, you are telling a specific, evidence-based answer from a rehearsed one. Add the written exercise, which is graded against a checklist rather than expertise, and one reference call that asks what the person actually owned. Those three together beat a long unstructured conversation with a candidate you liked.
The first quality hire has to build the system, not inherit one
At a large employer the new hire steps into a documented system with audits already scheduled. At a small business there is usually a folder of specs, a spreadsheet, and a lot of knowledge inside two long-tenured people. So ask directly what they would build first and what they would deliberately leave out for the first year. A candidate who wants to import a full corporate quality system into a small operation will produce binders nobody reads. The right answer is small, written with the people doing the work, and expanded only where a real failure justifies it.
Quality authority only works if it is written down
A quality hire who cannot hold a decision costs more than no hire at all, and holding a decision depends on authority you granted in advance. Before the first interview, decide who can stop a shipment, who approves a disposition, and who gets told when a customer is affected. Then ask candidates how they would use that authority. After you hire, put it in the offer and the role documentation, and store the signed records where you can find them. FirstHR handles that side: e-signature on the offer, task workflows for the first-week access and training, and document management for signed acknowledgments. Applicant tracking is coming soon to FirstHR.
What the hire will do
Inspector or technician
Quality specialist or manager
Runs checks and records results
Designs the checks and the sampling plan
Owns corrective actions to closure
Writes and controls procedures
Faces the customer on a complaint
Can decide disposition alone
The simplest rule: if this person will be your only quality hire and has to build the system rather than run it, interview with the process and audit set and pay for that level. If they will run defined checks with someone else deciding disposition, the core and manufacturing sets are enough. More hiring templates cover the posting, the evaluation form, and the offer.
From Interview to Onboarding
The interview is step one. A quality hire needs two things on day one that other roles do not: written authority to stop work or hold product, and access to the records that tell them what has already gone wrong here. Both belong in onboarding, not in a conversation six weeks later.
Put the authority in writing
The offer and the role description should state who can hold product or stop a process, who approves a disposition, and who gets notified when a customer is affected.
Set up access on day one
Specs and drawings, the complaint log, the recording or ticket system, the document library, and the measuring equipment they will need, ready before the first morning.
Give them a real first assignment
One product line, one queue, or one procedure to review in week one beats a week of reading. Pair it with a named person who answers questions.
Store the records
Keep the signed offer, I-9, W-4, training acknowledgments, and the interview scorecards for the role organized and retrievable.
Standard new-hire paperwork still applies alongside the role-specific setup, including the I-9 and W-4. Collect it before day one so the first morning goes to the product and the complaint history instead of forms.
FirstHR connects the offer, e-signature, task workflows, training modules, and document management in one place, so a small business can take a quality hire from signed offer to a documented first week without a stack of spreadsheets. FirstHR is an onboarding and HR platform, not a quality management system, so keep your specs, nonconformance records, and audit files where they live today. Applicant tracking is coming soon to FirstHR.
One last habit worth building: keep the interview scorecards and the graded exercises with the rest of the hiring records. When you hire the second quality person, the file tells you what you asked, what you scored, and how the answers matched the way the first hire worked out. That is also the point where a reference check pays off, because you can ask specifically about the areas your rubric flagged. Applicant tracking is coming soon to FirstHR.
Key Takeaways
Hire for prevention, not detection: the candidate who only catches defects will build you an inspection habit, not a quality system.
Decide which quality job you are filling first, because product inspection, the quality system, service review, and software testing share a name and little else.
Ask the same set of every candidate and use the good-answer notes to judge responses without a quality background of your own.
Run the 20-minute write-up exercise and grade it against the checklist; it is the most informative stage and the easiest to score fairly.
Two follow-ups do most of the work: what happened four weeks later, and what did it cost.
Use the federal wage data as the baseline: a median of $48,570 for inspectors and $104,300 for software QA analysts and testers (BLS OEWS, May 2025).
Frequently Asked Questions
What questions should I ask a quality assurance candidate?
Ask questions that test four things: whether they prevent problems or only catch them, how they decide what to check when checking everything is impossible, how they find a root cause, and how they behave when someone senior pushes back on a hold. Strong openers are: how is quality assurance different from quality control; tell me about a defect that reached a customer and what changed afterward; walk me through a corrective action you ran to closure; and a supervisor tells you to release an order you flagged, what do you do. Then add the set that matches your operation, whether that is manufacturing inspection, customer service review, or the quality system itself. Every question on this page comes with a note on what a good answer contains, so you can judge the response without a quality background of your own.
How do I interview for QA if I have never worked in quality myself?
You do not need to grade the technical content, you need to tell a specific answer from a rehearsed one. Use three tools. First, ask the same questions of every candidate and use the good-answer notes in each set as your reference while you listen. Second, run the written exercise on this page: a 20-minute nonconformance scenario graded against a 12-point checklist that requires no quality expertise to score, only the ability to check whether each element is present. Third, call one reference and ask what the candidate personally owned rather than what their team did. Specific numbers, lots, dates, and named methods are the signal. Vague claims about standards on a resume that the candidate cannot describe in plain language are the counter-signal.
What is the difference between quality assurance and quality control?
Quality assurance is the process that keeps defects from happening: written procedures, training, supplier controls, audits, and checks built into the work. Quality control is the inspection and testing that catches defects that still occur, such as measuring a part against a tolerance or reviewing a support call against a scorecard. Assurance is preventive and system-wide, control is detective and output-focused, and a working operation needs both. This matters in the interview because many candidates have spent their careers on the control side only. That is fine for an inspector role, but if you need someone to build the system, ask specifically for an example where they changed a process rather than sorted a batch. A candidate who cannot produce one will give you inspection, not assurance.
Should I use a work sample or practical test in a QA interview?
Yes. A short written exercise is the most informative stage of a quality interview and the easiest to grade fairly. Give every candidate the same 20-minute scenario, ask them to write the nonconformance report and list what they would do in the first hour, then score the result against the same checklist for everyone. It reveals whether they contain a problem before investigating it, whether they define the scope of what is affected, whether they think about the shipment that already left, and whether they add a verification step. Keep the exercise short, job-related, and identical for all candidates, and grade it with a written checklist rather than an impression. That consistency is also what keeps a practical test defensible if a rejected candidate ever asks how the decision was made.
What are red flags in a quality assurance interview?
The clearest red flag is a candidate who only ever talks about catching defects and never about preventing them, because that person will build an inspection habit rather than a quality system. Others worth weighing: no specific defect or complaint they can describe from past work, stories that blame operators or agents for every problem, a stated desire to inspect or review everything with no sense of cost, and answers that end at the fix with no verification that the problem stopped. Ask what happened four weeks after their corrective action; a blank response there is one of the most reliable signals in the interview. Finally, listen for how they handle a manager who overrides a hold. Releasing flagged product because someone asked, with no record of the decision, is a serious warning sign.
What does a quality assurance role pay?
It depends heavily on which quality role you mean, and the federal data separates them. According to the Bureau of Labor Statistics Occupational Employment and Wage Statistics survey (May 2025), inspectors, testers, sorters, samplers, and weighers had a median wage of $48,570 a year, about $23.35 an hour, with the lowest 10 percent under $35,510 and the highest 10 percent over $77,860. Software quality assurance analysts and testers, a separate federal occupation, had a median of $104,300 a year, about $50.14 an hour. Quality managers and quality engineers sit above the inspector range and are usually benchmarked against management and engineering occupations instead. Adjust for your industry, your local market, and whether the role owns a system or runs checks, then decide the level before you interview so you are not negotiating against yourself later.
Are quality assurance roles exempt or non-exempt?
Most inspection and hands-on quality roles are non-exempt and paid hourly with overtime, because the work is production and inspection rather than the exercise of independent judgment on matters of significance. A quality manager or a senior quality professional may qualify for a white-collar exemption, but only if the role meets both the duties test and the salary basis test under the federal Fair Labor Standards Act, where the standard threshold is $684 per week. Classification follows the actual duties, not the job title, so a title of quality manager on a role that spends its days inspecting product does not create an exemption. State rules can be stricter than the federal floor, and several states set higher salary thresholds. Confirm the classification before you post the role. This is general information, not legal advice.
What quality standards should I ask about?
Ask about the standards that actually apply to your operation rather than collecting acronyms. General manufacturing and service businesses most often work under ISO 9001, food operations under HACCP and preventive controls rules, and medical device or pharmaceutical operations under current good manufacturing practice requirements. Many small manufacturers work primarily to customer-specific requirements instead of a certified system, which is a perfectly good answer. The useful follow-up is always the same: what did you personally do inside that standard? A candidate who names the standard but cannot describe a document control routine, an internal audit they ran, or a corrective action they closed has been near the system rather than running it. If you are pursuing certification, say so in the interview and ask what they would build in the first six months.
