Quality Assurance Specialist interview questions

A QA interview is mostly a test of judgment under pressure: what you do when the record is wrong, the truck is waiting and the production manager is standing at your desk. Expect the panel to push for specifics. They've heard plenty of candidates say they're detail oriented, and they'll want the deviation you actually wrote.

12 questions7 minute read

Part 1

1.Walk me through a deviation investigation you led.

Why they ask

This is the core of the job. They want to hear whether you find real root causes or settle for the first easy answer.

How to answer

  • Set the scene in a sentence: the product, the line and what went outside its limits
  • Explain how you contained it first, such as placing affected lots on hold
  • Name the tool you used to dig in, like a fishbone diagram or the five whys, and what it turned up
  • Describe the corrective action and how you checked that it actually worked
  • Say what you'd do differently next time

2.Production wants to release a lot, and you've found a missing signature on the batch record. What do you do?

Why they ask

They're checking whether you'll hold the line and whether you know the proper route for a documentation error.

How to answer

  • Keep the lot on hold until the record is complete; you don't release around a gap
  • Find out whether the step was done and just not signed, or whether it wasn't done
  • Follow the site's good documentation practice for a late entry or open a deviation if the step was missed
  • Tell production early and plainly how long the fix will take so they can plan

3.How do you decide whether a problem needs a CAPA or just a correction?

Why they ask

Opening a CAPA for everything buries the system. Opening one for nothing lets real problems repeat. They want to see your judgment.

How to answer

  • Explain the difference: a correction fixes this instance, a CAPA stops it from happening again
  • Mention risk to the patient or customer as the main factor
  • Talk about trending, since the same small issue showing up repeatedly deserves a CAPA
  • Point to the site procedure as the rule you follow when it's unclear
4.Tell me about an audit you took part in. What went well and what didn't?

Why they ask

Audits are high stakes and you'll be in the room. They want to know you stay calm and answer only what's asked.

How to answer

  • Say what kind of audit it was: customer, certification body or regulator
  • Describe your role, such as runner, scribe or presenter in the front room
  • Give one finding and how the site responded to it
  • Share what you learned about preparing records before the next one
5.How would you rewrite a procedure that operators keep getting wrong?

Why they ask

A badly written SOP causes repeat deviations. They want someone who goes to the floor, not someone who edits from a desk.

How to answer

  • Watch the task being done and ask operators where they get stuck
  • Rewrite in the order the work actually happens, with photos where they help
  • Route it through change control and get training records updated
  • Check the deviation trend afterward to see if it worked

Part 2

6.What does good documentation practice mean to you in daily work?

Why they ask

GDP mistakes are some of the most common audit findings. They're checking that you know the habits, not just the acronym.

How to answer

  • Mention recording at the time the work is done, in permanent ink or a validated system
  • Explain the correct way to fix an error: a single line, initials, date and reason
  • Talk about why records need to be attributable and legible
  • Give a real example of catching a GDP error during record review
7.Which quality management software have you used, and what did you use it for?

Why they ask

Every site runs its QMS through some tool. They want to know how long it'll take you to get up to speed.

How to answer

  • Name the systems honestly, such as MasterControl, Veeva Vault, TrackWise or SAP QM
  • Say which modules you used: document control, CAPA, training, change control
  • If you haven't used theirs, compare it to what you know and say how you learned the last one
8.How do you handle a supplier who keeps sending nonconforming material?

Why they ask

Supplier quality lands on QA desks a lot. They want to see you escalate in steps rather than jumping straight to dropping the vendor.

How to answer

  • Document each nonconformance and send a formal corrective action request
  • Increase incoming inspection while the problem is open
  • Review their response and check the fix on later shipments
  • Bring in purchasing if it keeps happening and talk about a supplier audit
9.Tell me about a time you disagreed with someone senior about a quality decision.

Why they ask

QA only works if you'll speak up. They also want to see that you pick your fights and use data rather than volume.

How to answer

  • Describe the decision and why you thought it was wrong
  • Explain what evidence you brought, such as test results or the procedure itself
  • Say how it was resolved, including if you lost
  • Show that the working relationship survived
10.How do you keep up with regulations that apply to our products?

Why they ask

Rules change and plants get caught out. They want someone who reads guidance, not someone who waits for the next audit.

How to answer

  • Name the rules that matter for their industry, such as FDA current good manufacturing practice or food safety standards
  • Mention real sources: agency guidance, warning letters, ASQ or industry groups
  • Give an example of a change you brought back to your team

Part 3

11.Tell me about a time you made a mistake at work.

Why they ask

Quality people who hide their own errors are dangerous. They want to hear you own one and fix the system around it.

How to answer

  • Pick a real mistake with real consequences, not a humble brag
  • Say how you found it and who you told
  • Explain what you changed so it wouldn't repeat
12.Why do you want to work in quality rather than production or engineering?

Why they ask

They want to know you understand the trade: less building, more checking and more friction.

How to answer

  • Say what you like about the work itself, like finding causes or making systems hold
  • Show you know the downside, such as being the one who holds shipments
  • Tie it to a moment in your past work that pulled you toward QA

Questions to ask them

Ask at least two. It shows you're picking them too.

  • What does your CAPA backlog look like right now, and how old is the oldest open one?
  • What came up in your last external audit, and how is the site responding?
  • How does QA and production handle a disagreement about releasing product here?
  • Who would I report to, and who signs final release on a batch?
  • What would a good first few months look like for the person in this role?