Last updated: September 21, 2026
By Dave Manchester, Scientific Recruiting, KORE1
What should a quality control analyst job description actually say? A quality control analyst job description works when it names the instruments and methods the analyst will run, the product types, the shift, whether the lab records are paper or electronic, and the pay range. Most postings skip all five and open with a degree requirement instead.
Most of what I know about that list came out of a screen I run blind.
Let me define that, because the phrase gets used for something else entirely. “Blind hiring” normally means stripping names off resumes so the shortlist comes together without bias. Mine runs the other direction. The candidate is the one who can’t see. She doesn’t know the role. She doesn’t know the company. She doesn’t know the pay. So when I ask what she wants out of a career, nothing in the answer is bent toward a job she is hoping to land, because she has no idea which job I might be holding in the first place. I call it the Blind Recruit. No pitch first. Just the question.
Ask a QC analyst what she wants while a specific job is sitting on the table and you get the polite answer. Growth. Good team. Ask her before she has any idea who is hiring and the answer turns specific, occasionally a little ungrateful, and far more useful to whoever has to write the req.
Where I’m standing, so you can weigh it. I recruit for pharma, CDMO, and lab quality teams inside KORE1’s life sciences staffing group, part of the wider scientific staffing practice, and a stalled search is how I get a phone call in the first place. So take a recruiter’s advice on job descriptions with that in mind. Every figure below comes from federal data or a published study, and I’ll name the source each time. Where I’m only giving you my read, I’ll say so. If you’re hiring the manager too, QC and QA manager salary ranges sit in a separate guide.

What a QC Analyst Actually Does All Week
Start with the official list, which runs longer than most people expect. O*NET, the Labor Department’s occupational database, files quality control analysts under code 19-4099.01 and publishes 26 tasks for the job.
Read them in the order O*NET prints them and something shows up. The first fourteen are bench work. Run the analyses on raw materials, in-process samples, finished goods, and stability pulls. Interpret results against specification. Calibrate instruments. Keep the lab clean and safe. Inspect finished product. Fill in the logbooks and the data capture forms. Compile the data. Troubleshoot the equipment when it drifts. Write the deviation report. Flag a questionable result. Confirm the test followed the method. Recommend a fix. Sit in on the out-of-specification investigation. Receive and inspect the incoming drums.
Then the list changes character.
| Tasks 15 through 26, in O*NET’s words | What an analyst hears |
|---|---|
| Train other analysts to perform laboratory procedures and assays | A route to lead analyst that doesn’t require a supervisor to quit first |
| Write or revise standard quality control operating procedures | Her name on the SOP everyone else has to follow |
| Perform validations or transfers of analytical methods | The one skill that reliably moves an Analyst II to Senior |
| Develop and qualify new testing methods | Science. Not a worklist. |
| Evaluate analytical methods and procedures to determine how they might be improved | Permission to change something that annoys her daily |
| Prepare or review required method transfer documentation | Project work with an end date and a result she can point at |
| Supply quality control data necessary for regulatory submissions | Her data leaving the building with the company’s name on it |
| Participate in internal assessments and audits as required | Audit exposure, which is close to the most portable line on a QC resume |
| Serve as a technical liaison between quality control and other departments, vendors, or contractors | Talking to someone outside the lab for once |
| Review data from contract laboratories to ensure accuracy and regulatory compliance | Judgment, plus a look at how somebody else’s lab runs |
| Coordinate testing with contract laboratories and vendors | Ownership of a relationship outside the building |
| Evaluate new technologies and methods to make recommendations regarding their use | A say in what the lab buys next |
Source: O*NET OnLine, occupation 19-4099.01, Quality Control Analysts, tasks 15 through 26 as listed.
Twelve of twenty-six. Close to half the job, in the government’s own description of it, and I’d wager the last QC posting your team wrote mentioned two of them. Possibly one.
None of this is an argument for stapling twelve extra duties onto a seat you’re funding at the 25th percentile. It’s the opposite argument. The work is already in the role. Most analysts pick up some of the second group by their second year whether anybody wrote it down or not, which means the posting isn’t promising anything new, it’s just describing the job accurately for once. Costs nothing, too.
The Answers That Come Back When Nobody Knows Who’s Hiring
So what do QC analysts say they want, when the question isn’t attached to a job?
Four things surface often enough that I’d build a req around them. I’m not going to hand you percentages. I don’t run a survey, I run screens, and an invented number would be worth less than the pattern it was pretending to measure.
Growth comes up first, and they mean something narrower than the word suggests. Almost nobody says they want to manage people. What they describe is a method they own, a validation or transfer they get to run, a chance to train the next analyst. Now look at that table again. Every one of those things is already sitting on the federal task list for the job she currently holds, which tells you the problem is almost never that the work doesn’t exist at your site, because it does, and somebody is doing it. It’s that somebody senior has quietly kept all of it.
Second is the instrument mix, and it’s the simplest of the four. An analyst who has run the same three assays for four years is looking. Not because she’s bored, exactly. Because she can read a job board as well as you can, and she has already worked out what a line about method development or validation on somebody else’s posting is going to do to her next offer.
Shift is third, and it produces the most honest conversations I have. Plenty of analysts will take second or third shift. Some prefer it. What nobody forgives is finding out about it in round two, after two interviews and a drive, and when that happens I don’t get a negotiation. I get a short email. If your seat is off-hours, or if it’s days now with a weekend rotation arriving the moment the second line comes up, put that in the posting where she can see it before she spends an evening on your application. You’ll lose a few applicants. Week one, though. Not week five.
The fourth is the one hiring managers least expect. Analysts ask whether the lab is paper or electronic. A candidate coming out of a site running Empower and a validated LIMS thinks hard before stepping back into bound notebooks and wet signatures, and an analyst who has only ever worked on paper wants to know if this is where she finally learns the systems. Either way it’s a real question about her next five years. Two sentences in the posting settle it.
There is published work pointing the same direction, though it needs a caveat before I quote it. A 2026 study in Laboratory Medicine surveyed 302 clinical laboratory professionals and found compensation named by 75.9% of those intending to leave within the year, with lack of growth opportunities second at 51.9%. Among people merely thinking about leaving, compensation again led at 73.5%, followed by stress or burnout at 61.2%. Now the caveat. Those are hospital and clinical labs, not GMP labs, and the pressures aren’t identical. The ranking still matches what I hear. The study also found that feeling appreciated tracked with both thinking about leaving and planning to, which is not something a retention bonus fixes. Hiring for a hospital or reference lab rather than a GMP one runs under CLIA instead, which our page on medical technologist staffing covers.
Pay belongs in the posting too, and I’ve written about where the number should come from in the quality control analyst salary guide. It goes into more depth than this page can.

The Degree Line, and What the Regulation Actually Requires
Nearly every QC analyst posting I read requires a bachelor’s degree in chemistry, biology, or a related science. Worth asking where that requirement came from, because it didn’t come from the regulation.
Go read 21 CFR 211.25(a). It says each person engaged in the manufacture, processing, packing, or holding of a drug product must have “education, training, and experience, or any combination thereof,” to perform the assigned functions. Any combination thereof. The rest of that paragraph is about training, which has to cover the specific operations the employee performs plus current good manufacturing practice, delivered by qualified people on a continuing basis. FDA cares enormously about whether you trained the person. It has no view on where she went to school.
O*NET’s respondents are split too. Asked how much education a new hire in this occupation needs, 38% of them answered high school diploma or equivalent. Bachelor’s came second, at 28%. A post-secondary certificate took 10%. The database then rates the whole occupation Job Zone Three, medium preparation, which is the tier it uses for work where vocational training, related on-the-job experience, or an associate’s degree is the norm rather than a four-year science degree.
That code covers a lot of ground, so here’s the honest qualification. 19-4099.01 sweeps in food labs, environmental labs, and contract testing services, and a sterile injectables site is not those places. Inside pharma a science degree is common, and for method development and validation work it earns its keep. So keep it.
Just decide which block it belongs in first. “B.S. in chemistry or a related science” sitting in a requirements list is a wall. The identical sentence under a heading that says preferred is a door. A manufacturing operator who moved into the lab six years ago, got GMP-trained properly, and now runs dissolution and assay on commercial product will read the wall, decide the posting wasn’t written with her in mind, and close the tab without applying. She was qualified under 211.25 the whole time.
Quality Control Analyst Job Description Template
Fill the square brackets with your own answers. Parenthetical notes are instructions for you, so strip them before anything gets posted. A blank you can’t fill is usually worth a message to your QC supervisor, because a candidate is going to ask it on the first call anyway.
Job Title
[QC Analyst I / QC Analyst II / Senior QC Analyst / QC Microbiologist / QC Chemist], [Pharmaceutical Manufacturing / GMP Operations] (Put the level in the title. Put a pharma or GMP word in it too, or software testers will apply, and so will food and environmental analysts.)
About the Role and the Lab
[Company] makes [product types: oral solids, sterile injectables, biologics, medical devices] at our [city] site, and this analyst joins a QC lab of [N] on the [chemistry / microbiology / both] bench. You’d report to [title]. The lab supports [commercial production / clinical supply / both], which means the testing load looks like [roughly N samples a week, or the rhythm of it: heavy at month end, driven by the fill schedule].
The Bench: Methods, Instruments, and Systems
- Instruments you’d run: [HPLC, UPLC, GC, GC headspace, dissolution, Karl Fischer, FTIR, UV-Vis, TOC, particle size]
- Assays and methods: [assay and related substances, dissolution, content uniformity, identity, residual solvents, bioburden, endotoxin, sterility, environmental monitoring]
- Compendial work under [USP / EP / JP], and methods that are [validated and routine / still being transferred in from (site or CDMO)]
- Chromatography data system: [Empower / OpenLab / Chromeleon / none yet]
- Records: [a validated LIMS such as LabWare, LabVantage, or STARLIMS / an electronic notebook / paper batch records and bound notebooks / paper today, with (system) going live in (quarter)]
- [Sterile sites: the grade of the areas she’d gown into, and how often]
What You’ll Own
- Release and stability testing on [product or product family], start to finish, including the second-person review you’d perform on other analysts’ data
- Phase 1 out-of-specification lab investigations on your own results, with [supervisor / QA] taking it from there if the lab comes back clean
- [Instrument group or bench she’d be the primary on, plus the calibration and system suitability that comes with it]
- [Deviation reports, trend analyses, and the annual product review sections that draw on QC data]
Room to Grow
(Keep this section. It is the part almost no QC posting has, and it answers the question candidates are actually screening for. Only promise what you’ll genuinely hand over in the first eighteen months.)
- [Method transfers and validation protocols under ICH Q2(R2), starting with (which method or project)]
- [Training new analysts on (assay), once you’re qualified on it yourself]
- [Writing and revising the SOPs for your bench]
- [Reviewing data from our contract lab, and coordinating that testing]
- [Sitting in on internal audits, and on FDA or customer inspections at (this level of involvement)]
- [The path we’d expect: Analyst II to Senior in roughly (N) years, or the lead analyst seat as the second line comes up]
What You Bring
- [N] years of GMP lab experience, or an equivalent combination of education, training, and experience. (That phrasing is lifted from 21 CFR 211.25(a) on purpose. It is the standard your site is actually held to.)
- Hands-on time with [the two or three instruments from the bench list that are genuinely non-negotiable]
- A result you took through an out-of-specification investigation, and what you checked first
- Documentation habits that survive an audit. Contemporaneous entries, no back-dating, and corrections that show what was there before.
- [If the seat is off-hours, say it again here.]
Nice to Have
- [Degree line goes here if it is genuinely a preference, and in the section above if it is genuinely a wall]
- Method validation or transfer experience [if she’d be walking into one]
- [Empower or LIMS administration, which every lab assumes is common until it needs it]
- [Sterile or aseptic experience, gowning qualification, cleanroom time]
Schedule, Pay, and Location
This is [first shift, Monday to Friday / second shift, (hours) / a (N)-day rotation including weekends], on site at [city]. [Say plainly whether a weekend or on-call rotation exists, and how often it comes around.] Base pay runs [$low] to [$high], plus [shift differential of (N)%, bonus, benefits in one line]. (Pull the range from the salary guide, or run the seat through our salary benchmark assistant, and publish it. Several states now require a range in the posting, and analysts skip the ones that make them ask.)

What Quality Managers Ask After They Read the Draft
So what does a quality control analyst actually spend the week doing?
Bench work, mostly. Testing raw materials, in-process samples, finished batches, and stability pulls against specification, documenting every result, and investigating the ones that fail.
O*NET lists 26 tasks for the occupation, and the first fourteen are that testing loop. The other twelve are method transfers, SOP writing, training, audit participation, and contract lab oversight. Plenty of analysts reach into that second group early. Almost no job description admits it exists.
HR wants a bachelor’s degree in the requirements. Leave it?
The regulation doesn’t require one. 21 CFR 211.25(a) asks for “education, training, and experience, or any combination thereof,” and O*NET’s respondents split 38% high school, 28% bachelor’s, 10% certificate.
Plenty of pharma sites still want the degree, and for method development I understand why. Just be honest with yourself about which block it belongs in. A hard requirement screens out the manufacturing operator who crossed into the lab years back and now runs your dissolution bench better than anyone on it.
How specific should we get about instruments and methods?
Name three methods and two instruments, minimum, with the chromatography data system. “HPLC experience required” tells a candidate nothing, because assay and related substances on a validated tablet method is a different job from cleaning verification.
Specificity cuts your application count and raises the quality of what’s left. That trade scares hiring managers until the first screen, when the candidate already knows what she’d be running and the call goes somewhere useful.
Plenty of resumes, not one finalist. Where does a posting go wrong?
Usually the title, not the requirements. “QC Analyst” with no industry word draws food, environmental, and software testing candidates, and a title with no level in it draws everyone from new graduates to lab supervisors.
Volume is the tell. A posting pulling a hundred applications for a GMP bench seat is pulling from the wrong pool entirely, and no amount of screening downstream fixes a problem that was created the moment somebody typed the title. Fix the title first. If you’re still deciding which seat you’re filling, my piece on QC versus QA in pharma sorts that out before the posting goes anywhere.
Should the posting admit the role is second shift?
Yes, and early. Analysts who won’t work nights rule themselves out before anyone books a panel, and the analysts who actively prefer off-hours are out there searching for exactly that line.
Same logic applies to a weekend rotation that starts when the new line comes up. Say it now. A candidate who learns it in round two reads the omission as a preview of how the site communicates, and she isn’t wrong to.
How long should a QC analyst job description be?
Shorter than the one you have, and more specific. Cut the boilerplate about attention to detail and being a team player, then spend the space you freed on methods, instruments, shift, and what she gets to own by year two.
Every analyst has attention to detail. It’s the entry fee for the profession, and printing it tells a candidate you wrote the posting from a template. Which you did. Everyone does. The four specifics are what make it yours.
Ask the Question Before You Write the Req
A good candidate is like a house that shows well. If it’s a great house, several buyers turn up, and the listings that sit are usually the ones that never showed you the floor plan. Your posting is the listing. Vague gets you volume. Specific gets you the analyst.
Before it goes live, try the blind version of the question on your own bench. Ask an analyst you already employ what she’d want out of her next role, and do it without mentioning that you’re hiring for anything, because the moment she thinks there’s a seat involved you’re back to getting the polite answer. Then read your draft again. The gap between those two documents is where the search is going to stall, and it’s usually fixable in an afternoon.
KORE1 placements hold at a 92% retention rate twelve months in, and a posting that tells the truth about the shift and the bench is where that starts. If the seat covers a stability backlog or a tech transfer with an end date, the kind of surge our pharmaceutical staffing desk covers, contract-to-hire lets you watch the work before committing the headcount, and for a permanent bench seat, or a first quality hire at a young company where our biotech recruiters usually start, we’d run it as a direct hire search. Equipment qualification and process validation are a different animal, and our quality engineering recruiters own that side. The QC manager or head of quality above this bench is a different search again, and our pharmaceutical recruiting desk runs those on direct hire or retained terms. Here’s how we vet candidates before you see the resume, which is where the blind screen actually happens.
Send me the draft req before it posts and I’ll tell you what a candidate will ask about it. Let’s connect. My LinkedIn works too.

