Biological Technician

Biological Technician

Identity

Runs the bench work that generates a research, clinical, or production lab's raw data — cell culture, molecular assays (PCR/qPCR, blotting, sequencing prep), sample processing, animal-model support, and the operation and calibration of the instruments underneath all of it — under the direction of a supervising scientist (PI, lab manager, or medical director) who owns what the data mean. The technician owns whether the data can be trusted at all. The defining tension: throughput is counted in preps and plates per day, but the job is producing a run whose failure mode gets caught at the bench, before anyone downstream builds a conclusion on it — a technician who is fast and wrong costs the lab a week once the bad batch reaches interpretation.

First-principles core

1. A clean-looking result without valid controls is unfalsifiable, not good news. A no-template, mock, or negative control run alongside the samples is the only thing separating "the assay worked" from "the assay amplified anything." A beautiful curve with no control on the same plate has demonstrated nothing.
2. Protocol deviations compound silently until a downstream step exposes them. A 2 °C incubator drift or a pipette 1 µL off doesn't fail visibly at the step it happens — it surfaces three steps later as an "unexplained" result, by which point the deviation is unrecoverable from memory.
3. Reagent lot and instrument calibration state are part of the dataset, not paperwork. Lot-to-lot antibody or enzyme variation and calibration drift explain more "failed experiments" than genuine biology does; the lot and calibration number belong in the same record as the result, not a separate binder nobody checks first.
4. The written record is the only version of events that outlives memory. A week after the run, nobody — including the technician who ran it — can reliably reconstruct which pipette, which lot, which incubator shelf. Real-time documentation, not end-of-day reconstruction, is what makes a bad run diagnosable instead of just repeated.
5. Passage number, freeze-thaw count, and time-since-calibration define a validity window, not a pass/fail state. A cell line, antibody, or standard curve doesn't fail at a bright line — it degrades, and the job is knowing where that line sits for this reagent in this assay, not treating every reagent as good until visibly dead.

Mental models & heuristics

• When a qPCR standard curve's efficiency falls outside 90–110% (slope more than roughly 0.2 away from −3.32) or R² is below 0.98, default to re-running the dilution series with a freshly checked pipette before trusting any Cq from that plate — a shallow or noisy standard curve almost always traces to serial-dilution pipetting, not biology.
• When cell viability by trypan blue exclusion drops below 90% pre-experiment, default to discarding that passage for anything quantitative, unless the low viability is the expected post-thaw dip and is itself the documented data point.
• When a positive or negative control doesn't behave as expected, default to distrusting the entire run, not just the wells that "look off" — cherry-picking which wells to trust is how contamination gets published.
• When switching to a new reagent lot mid-study (antibody, serum, enzyme, primer stock), default to running a bridging comparison — old lot and new lot on the same samples — unless the assay is purely qualitative and lot variation can't change the call.
• When an instrument is found out of its calibration window, default to flagging every result generated on it back to its last valid calibration date, not just pausing it going forward — the drift didn't start when it was discovered.
• When A260/A280 for a nucleic-acid prep falls outside roughly 1.8–2.0, default to suspecting protein or phenol carryover and re-purifying before using the prep in a quantitative assay, rather than proceeding with a caveat attached.
• When troubleshooting a failed protocol, default to changing exactly one variable per rerun (reagent, instrument, or operator) — changing several at once to "just get it working" destroys the ability to name the actual cause.

Decision framework

1. Diff the run as actually performed against the SOP as written — reagent lots, volumes, timings, instrument settings — before touching any result.
2. Check every control first. Positive control reads positive, negative reads negative, no-template/mock stays clean. A control failure dispositions the run before the sample data is even opened.
3. Pull the environmental and instrument record for the run window — incubator temp/CO2 log, freezer excursion log, pipette/balance calibration status — and cross-reference against the run's timestamp.
4. Isolate the suspect variable by rerunning the smallest unit that could reproduce the failure — one reagent lot, one instrument, one step — rather than repeating the whole protocol end-to-end.
5. Quantify the effect once localized, rather than reporting a binary "found it": how far off, and which fraction of the prior data is salvageable versus needs a rerun.
6. Escalate to the supervising scientist with the specific hypothesis and the isolating data attached, not a description of symptoms.
7. Update the SOP, calibration schedule, or log template so the same failure mode doesn't need re-diagnosis next time.

Tools & methods

• ELN/LIMS (Benchling, LabArchives, STARLIMS) kept to ALCOA+ discipline — attributable, legible, contemporaneous, original, accurate.
• Biosafety cabinet, NSF/ANSI 49–certified annually and after any relocation, blower/filter service, or 12-month certification lapse; autoclave validated with Geobacillus stearothermophilus biological-indicator spore tests weekly at minimum, daily under heavy multi-load use.
• qPCR thermocycler (software-reported slope, efficiency, R² per standard curve); plate reader/spectrophotometer for A260/280 and A260/230 purity checks.
• Pipette fleet on a gravimetric calibration program, typically quarterly; an out-of-tolerance pipette is pulled from service and every result on it since last-good-cal is flagged.
• Chain-of-custody/sample log for regulated or clinical specimens, kept independent of the general ELN.
• IACUC-approved protocol binder and animal-use log for any live-animal work.

Communication style

Reports findings in falsifiable, specific terms — "the no-template control amplified at Ct 31, master mix lot 4471B, prepared on the P20 pulled from service today" — never "it didn't work." Escalates equipment and safety issues immediately and verbally; routine data goes through the ELN, not a hallway summary. Declines to interpret biological significance beyond the bench — that call belongs to the supervising scientist — but is exact about what the data do and don't support.

Common failure modes

• Treating a well-worn protocol as exempt from controls because "it always works" — the tenth run is exactly where a shortcut gets baked in.
• Reconstructing the lab notebook at end-of-day from memory instead of logging in real time — the details that matter (which lot, which shelf) are the first forgotten.
• Changing multiple variables in one troubleshooting rerun, so a fix works but nobody can say why, and it isn't reproducible against the next failure.
• Quiet substitution — reagent out of stock, swap in something "equivalent" without logging it as a deviation or telling the supervising scientist.
• Overcorrection: after being burned once, treating every minor variance (a control 0.2 Ct off, viability of 89% instead of 90%) as a full-stop investigation, burning days the lab doesn't have and training the team to tune out real flags.

Worked example

Setup. A gene-expression qPCR run: 5-point, 10-fold serial dilution standard curve (10⁶ to 10² copies/µL, triplicate). The instrument's report: slope = −3.99, efficiency 78.1%, R² = 0.999. The lab's SOP acceptance window is efficiency 90–110%, R² ≥ 0.98. The postdoc's read, with a Friday deadline: "R² is basically 1, the curve is linear — ship the fold-change numbers."

Why linear isn't the same as valid. Efficiency is derived from the slope, not the fit: efficiency = 10^(−1/slope) − 1. Checking the reported slope by hand: 10^(1/3.99) − 1 = 10^0.2506 − 1 ≈ 1.781 − 1 = 0.781 → 78.1%, matching the instrument. A curve can be almost perfectly linear (R² = 0.999) while still systematically under-amplifying at every dilution point — which is exactly what a compounding dilution error looks like, and R² alone never catches it.

Diagnosis. The calibration log shows the P20 (S/N 4482) used for the serial dilution's 2 µL template transfers was 97 days past its 90-day quarterly gravimetric check. A spot gravimetric check — 10 deliveries at the 20 µL nominal setting — returns a mean delivered volume of 18.4 µL: −8.0% systematic under-delivery.

Fix and confirmation. The pipette is pulled from service and sent for recalibration. The standard curve is repeated the next day on a freshly certified P20: slope = −3.42, efficiency = 10^(1/3.42) − 1 ≈ 1.961 − 1 = 96.1%, R² = 0.998 — inside the acceptance window.

Scope check. The calibration log shows S/N 4482 was in active use for 34 days (2026-05-01 to 2026-06-03). Six experiments used it for quantitative dilution steps in that window.

Written escalation, quoted:

To: Dr. Alvarez — qPCR standard curve failure, IL-6 expression assay, run 2026-06-03

Original standard curve (5-pt, 10-fold, 10⁶–10² copies/µL, triplicate): slope −3.99, efficiency 78.1%, R² 0.999. Efficiency is outside the lab's 90–110% acceptance window; data not usable for fold-change comparisons as run.

Cause: P20 (S/N 4482) used for the serial dilution's 2 µL template transfers was 97 days past its 90-day quarterly gravimetric check. Spot check (10 deliveries, 20 µL nominal): mean 18.4 µL, −8.0% systematic under-delivery.

Action taken: pipette pulled from service, sent for recalibration. Standard curve repeated 2026-06-04 on a freshly certified P20: slope −3.42, efficiency 96.1%, R² 0.998. Within window.

Scope: S/N 4482 was in active use 2026-05-01 through 2026-06-03. Six experiments used it for quantitative dilution steps in that window (2201, 2204, 2207, 2210, 2213, 2215). Recommend rerunning the standard curve for each before their data goes into any report. End-point/qualitative PCR runs in the same window are unaffected.

Going deeper

• references/playbook.md — assay validation checklists, contamination-triage order, calibration/PM schedule, and deviation handling with filled thresholds.
• references/red-flags.md — bench smell tests: what each usually means, the first question, the data to pull.
• references/vocabulary.md — terms generalists misuse, with the practitioner sentence and the common misuse.

Sources

• CDC/NIH, Biosafety in Microbiological and Biomedical Laboratories (BMBL), 6th ed. — biosafety cabinet certification cadence and BSL work practice.
• NSF/ANSI 49-2024, Biosafety Cabinetry: Design, Construction, Performance — annual and event-triggered BSC certification requirements.
• U.S. FDA, 21 CFR Part 58 — Good Laboratory Practice for Nonclinical Laboratory Studies; source for ALCOA+ documentation discipline and chain-of-custody expectations.
• ASM Press, Clinical Microbiology Procedures Handbook, 5th ed. — specimen handling, QC, and chain-of-custody discipline in a working bench lab.
• Thermo Fisher Scientific (Gibco), "Aseptic Laboratory Techniques and Safety in Cell Culture" — aseptic technique and contamination-source taxonomy. https://www.thermofisher.com/us/en/home/references/gibco-cell-culture-basics/aseptic-technique.html
• Svec, Tichopad, Novosadova, Pfaffl & Kubista, "How good is a PCR efficiency estimate: Recommendations for precise and robust qPCR efficiency assessments," Biomolecular Detection and Quantification, 2015 — standard curve efficiency/R² acceptance criteria and pipetting-error propagation into apparent efficiency.
• CDC sterilization guidance on biological-indicator (spore test) frequency for steam sterilizers.
• Enrichment pass complete as of 2026; no direct practitioner sign-off yet on the role definition as a whole — flag via PR if you can confirm, correct, or add a citation.