QC vs QA in Pharma: Two Departments, Two Different Hires

Last updated: September 17, 2026

By Dave Manchester, Scientific Recruiting, KORE1

QC or QA, which one are you actually hiring? In pharma, quality control tests raw materials, in-process samples, and finished product in the lab, while quality assurance owns the system around that testing, from batch record review and deviations to CAPA and audits. Two departments, two different hires, and mixing them up is one of the quieter ways a quality search stalls.

“How can I find the right quality control candidates for my pharmaceutical company?”

That’s the search I picture a lab manager typing late at night, a few weeks into an opening that should have closed by now. It deserves a straight reply. My first answer is usually another question, though. Are you sure it’s QC you need?

Often it is. But a job posting titled “QA/QC Specialist” tends to come from a company that hasn’t decided yet, and it pulls in two very different crowds. One wants the lab. The other would rather live inside batch records and deviation reports and hasn’t held a pipette in years. Both crowds have strong people in them. Neither one is the person you’re picturing.

I’ve recruited scientific talent for 16 years. These days that work runs through KORE1’s life sciences staffing practice, which makes me a less-than-neutral party on how pharma companies should hire, so weigh what follows with that in mind. I minored in chemistry, too, and started college on a pre-med track. Science nerd. I just ended up on the hiring side. KORE1 placements carry a 92% retention rate at twelve months, and a number like that starts with getting the role right before anybody posts it.

Quality Control vs Quality Assurance, in One Plant

Quality control is the testing function. QC analysts sample and test incoming materials, in-process material, finished product, and stability samples against written specifications. Quality assurance is the oversight function. QA writes and controls the procedures, reviews the records, investigates deviations, runs CAPA and audits, and gives management and regulators confidence that the whole system works.

The American Society for Quality says nearly the same thing. Its QA vs QC explainer defines quality control as the “part of quality management focused on fulfilling quality requirements” and quality assurance as the part “focused on providing confidence that quality requirements will be fulfilled.” ASQ also admits the two terms get used interchangeably and calls QC a subset of QA. I like that honesty. So if your org chart blurs them, you’re in good company.

Here’s where the difference shows up once you start writing the job description.

Even FDA Mixes Up the Names

This one makes me laugh. The federal rule that gives a drug company’s quality function its authority doesn’t call that function QA.

Under 21 CFR 211.22, a drug manufacturer needs a “quality control unit” with the authority to approve or reject components, in-process materials, labeling, and finished drug products, and to review production records so that errors get caught and fully investigated. That’s the release decision. The regulation hands it to a unit named quality control.

Now look at FDA’s 2016 guidance on quality agreements with contract manufacturers, which defines “quality unit” as synonymous with “quality control unit.” And when inspectors actually show up, the agency files those visits under drug quality assurance inspections. Its FY2025 Report on the State of Pharmaceutical Quality counted 1,248 of them, and 18% of the inspections FDA classified that year came back official action indicated, the most serious outcome on its scale. Nearly one visit in five landed there.

So the regulation says control, the inspection program says assurance, and the posting down the street says whatever its last hiring manager typed. Nothing in the rules decides how your company splits the work. You decide that. Which also means a title tells a candidate almost nothing until they read the duties.

One more naming trap while we’re here. A job called “QA Analyst” with no industry word in the title will draw software testers, because in tech hiring that’s what QA means. The fix is cheap. Put “GMP” or “pharmaceutical” in the title itself, not three paragraphs down.

How a Batch Moves Between the Two

Following one batch of tablets through a plant is the fastest way to see who does what, since the handoffs are where each department earns its name.

1. A drum of raw material arrives at the dock. QC samples it and runs at least an identity test before production can touch it, and QA has already qualified that supplier and decided how much weight its certificate of analysis gets.
2. Manufacturing makes the batch. In-process checks happen along the way.
3. Finished tablets go to the QC lab for release testing against the specification. Assay, impurities, dissolution, micro, whatever that product calls for.
4. A result fails. Under FDA’s guidance on out-of-specification results, the analyst and the lab supervisor look first, checking for a lab error before anybody decides the batch is bad. If the lab comes up clean, the investigation widens past the lab, and QA usually takes the wheel from there.
5. Meanwhile somebody in QA reads the executed batch record page by page, missing initials and late entries included.
6. Release or reject. That call belongs to the quality unit, and at a lot of companies the signature sits in QA.
7. Stability samples get pulled on a schedule for the rest of the product’s shelf life, and that testing lands back in QC.

See the pattern? QC produces evidence. QA decides whether the evidence, and everything around it, holds up. Someone who loves the first job rarely wants the second one, which is fine, as long as you hire for the job you actually have.

Hiring for the QC Bench

A QC search is a hands-on skills search. When a quality control resume lands in front of me, I read for instruments, methods, and sample types before anything else. “HPLC experience” is a start. I need the method too. Someone who ran assay and related substances on a small-molecule tablet, in Empower, against a validated method? That’s a candidate.

Then I ask about a result that came back out of specification. FDA’s OOS guidance puts the first responsibility for accurate results on the analyst who ran the test, and good analysts perk up at this question. They talk about system suitability, about holding onto their preparations until a supervisor has looked, about why nobody retests a sample until they like the answer. Vague answers worry me.

Data integrity sits right beside that. Every lab record needs a second person’s review for accuracy, completeness, and compliance under 21 CFR 211.194, so an analyst who has done peer review of chromatography data brings two skills to one seat. I notice that.

Now the part hiring managers don’t love. Candidates on the market are like professional athletes. If a QC chemist with real GMP release testing experience is good, several companies want them at the same time, and the one running a five-week interview process tends to finish second. When the resume matches, move.

QC work comes in surges. A tech transfer (moving a product’s process and methods from one site to another), a stability backlog, a launch. Those fit contract-to-hire staffing well, since you get bench hands right away and decide on the permanent seat after watching them work. For a short surge with no permanent seat behind it, pharmaceutical staffing on contract covers the bench without adding headcount.

Hiring for QA

A QA search is a judgment search, and a writing search. The person you hire reads batch records for a living, writes deviation reports that an FDA inspector might read two years from now, and at some point tells a production manager “no” on a Friday afternoon with trucks already booked.

That Friday part matters more than anything on the resume. Plenty of smart people can’t.

A lot of the strongest QA candidates I meet started in QC. Bench time teaches you what a clean chromatogram looks like, which makes it much easier to catch the ugly one stapled into a batch record. QC to QA is a well-worn career path. The reverse trip is rarer. So a QA specialist who hasn’t run a method in five years shouldn’t be the one troubleshooting your lab.

For QA I care about three things, and none of them is a certificate. Can this person write clearly? Do they know the regulations your products live under, which for a drug maker means 21 CFR Part 211? Have they stood in front of an auditor and answered a question they didn’t like? An ASQ Certified Quality Auditor credential is nice to see on top of that. It won’t replace them.

A couple of neighboring searches get filed under QA by mistake. Equipment validation, process qualification, and risk assessments belong to a quality engineer, and our quality engineering recruiters work that side. LIMS administration and computer system validation sit closer to IT, which is where our pharma IT staffing team comes in. For a QA manager or head of quality, I’d run a direct hire search. That person shapes your quality culture for years.

When One Quality Person Has to Be Both

If you run a 30-person company, this is probably the section you scrolled down for.

Many small pharma and virtual biotech companies don’t make anything themselves. A CDMO, short for contract development and manufacturing organization, makes the product, and its lab runs the release testing. You might assume that means you need your own QC analyst to watch their QC. You probably don’t.

FDA’s quality agreement guidance is blunt about who’s on the hook. It’s you. When an owner uses a contract facility, the owner’s quality unit is legally responsible for approving or rejecting what that facility makes, final release included. So the first quality hire at a small sponsor is usually a QA person, somebody who can read the CDMO’s batch records and test data, push back on a deviation, and hold up your end of the quality agreement. They need enough lab background to question a result. Running the instrument is someone else’s job.

The moment to split into two roles tends to arrive with the testing. Bring the lab in-house and you need analysts. Watch release volume outgrow one reviewer, and there’s your second hire. The real alarm, though, is one person approving work they did themselves, because the second-person review in 211.194 assumes two people and nobody gets to be their own second person.

Whichever seat comes first, the screening does more work than the posting ever will. Here’s how KORE1 vets candidates before you see the resume.

Questions Quality Leaders Bring Me

Is QC Part of QA, or Its Own Department?

Both setups are normal. ASQ treats quality control as a subset of quality assurance, and many companies organize it that way, with a QC manager and a QA manager reporting to one head of quality. Bigger sites often run them as sister departments. The part worth protecting either way is that quality never answers to the person whose batches it judges.

Who Actually Signs Off on Batch Release?

The quality unit does, and at many companies that signature lives in QA. The regulation, 21 CFR 211.22, gives release authority to a “quality control unit,” but FDA’s own guidance uses quality unit and quality control unit as synonyms, so each company decides where the signature sits. If a contract manufacturer makes your product, your quality unit still owns final release.

Why Do Software Testers Keep Applying to Our QA Job?

Because in tech hiring “QA” means software testing, and job boards match on titles. Titles fix this fast. Put “GMP,” “pharmaceutical,” or the product type in the title itself.

Can a Good QC Analyst Grow Into a QA Role?

Often, and it’s one of the most traveled paths in pharma quality. Bench experience helps a reviewer spot a bad chromatogram or a thin investigation. What usually needs building is the writing, plus the nerve to challenge people outside the lab, and pairing a new reviewer with an experienced one for their first stretch of batch records builds both faster than a class.

Do We Need a Microbiologist in QC, or Just Chemists?

Your product decides it. Sterile products bring sterility testing and environmental monitoring, which is microbiology work through and through, and even non-sterile products get microbial limits testing under USP chapters 61 and 62. A small site making oral solids can often start with chemists and send the micro work to a contract lab, then bring it in-house once the volume justifies a dedicated microbiologist.

Producing Results or Judging Them

If you’ve read this far, you’ve probably got an open quality seat, or one coming. Before it gets posted, answer one question. Will this person spend most of the day producing results, or judging them?

That answer picks the title for you, and most of the interview panel with it. If you’d like a scientific recruiter to pressure-test the req before it goes live, let’s connect. My LinkedIn inbox works too.