A bioinformatics scientist exists to turn the flood of molecular data — genomes, transcriptomes, proteomes — into biological knowledge that holds up. The bottleneck has moved from generating data to interpreting it correctly. The job is to extract real biological signal from noisy, biased, high-dimensional measurements, reproducibly enough that the result survives a second cohort, a second pipeline, and a hostile reviewer. The discipline exists because biology became a data science faster than biologists became statisticians, and a confident wrong answer can send a clinical trial chasing a ghost for years.
\n","wordCount":90},{"heading":"Core Mission","id":"core-mission","markdown":"Extract biological signal from large-scale molecular data through reproducible, statistically defensible pipelines, and validate every consequential finding in independent data before anyone acts.","html":"Extract biological signal from large-scale molecular data through reproducible, statistically defensible pipelines, and validate every consequential finding in independent data before anyone acts.
\n","wordCount":24},{"heading":"Primary Responsibilities","id":"primary-responsibilities","markdown":"The visible output is figures and gene lists, but the actual work is defending an inference against the many ways high-dimensional biology lies. A bioinformatics scientist frames a biological question into a computational test; assesses data quality and provenance before trusting a single number; parameterizes alignment, variant-calling, or quantification tools whose defaults are rarely right; corrects for batch effects and the thousands-of-tests problem; builds containerized, version-controlled pipelines so a result can be regrown bit-for-bit; interprets hits through biological knowledge rather than p-value alone; and partners with wet-lab scientists to validate the few findings worth the cost. Underneath it all is suspicion of the data: the reference is biased, the batches differ, the dimensionality dwarfs the sample size.","html":"The visible output is figures and gene lists, but the actual work is defending an inference against the many ways high-dimensional biology lies. A bioinformatics scientist frames a biological question into a computational test; assesses data quality and provenance before trusting a single number; parameterizes alignment, variant-calling, or quantification tools whose defaults are rarely right; corrects for batch effects and the thousands-of-tests problem; builds containerized, version-controlled pipelines so a result can be regrown bit-for-bit; interprets hits through biological knowledge rather than p-value alone; and partners with wet-lab scientists to validate the few findings worth the cost. Underneath it all is suspicion of the data: the reference is biased, the batches differ, the dimensionality dwarfs the sample size.
\n","wordCount":126},{"heading":"Guiding Principles","id":"guiding-principles","markdown":"- **Garbage in, garbage out — so audit the input first.** No analysis is better than its data. Check read quality, contamination, batch structure, and sample swaps before computing anything downstream.\n- **Correct for multiple testing or report noise.** Twenty thousand genes tested at p < 0.05 yields a thousand false positives by chance. Benjamini-Hochberg FDR is not optional.\n- **A finding in one cohort is a hypothesis; validation in an independent cohort is a result.** Discovery data overfits; the second dataset is the referee.\n- **Batch is a confound until proven otherwise.** If cases were sequenced in one run and controls in another, you may be measuring the machine, not the biology.\n- **Reproducibility is a property of the pipeline, not the person.** If you cannot rerun last year's analysis and get the identical figure, you have an anecdote, not a method.\n- **The reference is a choice with consequences.** Genome build, annotation version, and the reference's source populations all bias what you can detect.","html":"Bioinformatics sits at the seam between the wet lab and the cluster, and most of the job is translation. The analyst works with molecular biologists and clinicians who own the biological question, sequencing-core staff who control library prep and batch structure (and must be lobbied to randomize), statisticians who sharpen the inference, software engineers who harden pipelines, and data stewards who enforce FAIR and consent. The recurring friction is the dry-lab/wet-lab gap: the analyst sees confounds the bench scientist designed in months ago, and the bench scientist knows context the ranking ignores. The best results come from analysts embedded early enough to shape experimental design.
\n","wordCount":109},{"heading":"Ethics","id":"ethics","markdown":"Genomic data is among the most identifying information that exists — it cannot be truly anonymized, it implicates relatives who never consented, and it can reveal disease risk a person did not want to know. Consent must be specific, data access controlled (dbGaP, EGA tiers), and secondary use governed. Reference bias is an equity issue: genomic medicine built largely on European-ancestry references underserves everyone else. The analyst owes honesty about uncertainty — a variant interpretation that overstates confidence can drive a prophylactic surgery or a missed diagnosis. Reproducibility is an ethical commitment: irreproducible biomarkers waste public money and patient hope.","html":"Genomic data is among the most identifying information that exists — it cannot be truly anonymized, it implicates relatives who never consented, and it can reveal disease risk a person did not want to know. Consent must be specific, data access controlled (dbGaP, EGA tiers), and secondary use governed. Reference bias is an equity issue: genomic medicine built largely on European-ancestry references underserves everyone else. The analyst owes honesty about uncertainty — a variant interpretation that overstates confidence can drive a prophylactic surgery or a missed diagnosis. Reproducibility is an ethical commitment: irreproducible biomarkers waste public money and patient hope.
\n","wordCount":99},{"heading":"Scenarios","id":"scenarios","markdown":"**A striking differential-expression result.** An analyst finds 300 genes \"significantly\" up-regulated in disease versus control at p < 0.05. The expert runs the checks first. Benjamini-Hochberg FDR at 0.05 collapses 300 hits to 12. Then PCA: samples separate by sequencing run, and disease cases cluster in run 1 — the \"signature\" is largely a batch effect confounded with condition. The fix is to model batch as a covariate in the DESeq2 design (better, to randomize cases across runs). What survives correction and batch adjustment, and replicates in a held-out cohort, is the real finding.\n\n**Building a diagnostic classifier on p >> n.** A team wants a classifier to predict treatment response from 60 patients across 20,000 genes, and an early model reports 97% accuracy. The expert is suspicious: with p >> n, near-perfect separation is the expected artifact, and the likely culprit is leakage — feature selection and normalization on the full dataset before cross-validation. They rebuild the evaluation so every preprocessing and selection step happens inside each fold, on that fold's training data only. Honest nested cross-validation drops accuracy to 68% — disappointing but real. They refuse to deploy until it validates on an independent cohort.\n\n**A variant absent from the reference.** A clinical analysis fails to find a suspected pathogenic variant in a patient of non-European ancestry. Rather than concluding it is absent, the expert finds the reference region poorly represented and the haplotype divergent — reads carrying the variant aligned poorly and were filtered. Realigning against a graph-based reference recovers the reads, and the variant appears. The lesson, recorded in the protocol: \"not found\" against a biased reference is not \"not present.\"","html":"A striking differential-expression result. An analyst finds 300 genes "significantly" up-regulated in disease versus control at p < 0.05. The expert runs the checks first. Benjamini-Hochberg FDR at 0.05 collapses 300 hits to 12. Then PCA: samples separate by sequencing run, and disease cases cluster in run 1 — the "signature" is largely a batch effect confounded with condition. The fix is to model batch as a covariate in the DESeq2 design (better, to randomize cases across runs). What survives correction and batch adjustment, and replicates in a held-out cohort, is the real finding.
\nBuilding a diagnostic classifier on p >> n. A team wants a classifier to predict treatment response from 60 patients across 20,000 genes, and an early model reports 97% accuracy. The expert is suspicious: with p >> n, near-perfect separation is the expected artifact, and the likely culprit is leakage — feature selection and normalization on the full dataset before cross-validation. They rebuild the evaluation so every preprocessing and selection step happens inside each fold, on that fold's training data only. Honest nested cross-validation drops accuracy to 68% — disappointing but real. They refuse to deploy until it validates on an independent cohort.
\nA variant absent from the reference. A clinical analysis fails to find a suspected pathogenic variant in a patient of non-European ancestry. Rather than concluding it is absent, the expert finds the reference region poorly represented and the haplotype divergent — reads carrying the variant aligned poorly and were filtered. Realigning against a graph-based reference recovers the reads, and the variant appears. The lesson, recorded in the protocol: "not found" against a biased reference is not "not present."
\n","wordCount":195},{"heading":"Related Occupations","id":"related-occupations","markdown":"A bioinformatics scientist sits between biology and computation, sharing the inferential discipline of science with the engineering discipline of reproducible software. The research scientist supplies the hypothesis-driven method; the biologist supplies the molecular questions and wet-lab validation. The data scientist and machine-learning engineer share the high-dimensional statistics and cross-validation, with peculiar p >> n hazards. The data engineer shares the pipeline craft.","html":"A bioinformatics scientist sits between biology and computation, sharing the inferential discipline of science with the engineering discipline of reproducible software. The research scientist supplies the hypothesis-driven method; the biologist supplies the molecular questions and wet-lab validation. The data scientist and machine-learning engineer share the high-dimensional statistics and cross-validation, with peculiar p >> n hazards. The data engineer shares the pipeline craft.
\n","wordCount":66},{"heading":"References","id":"references","markdown":"- *Bioinformatics and Functional Genomics* — Jonathan Pevsner\n- *Modern Statistics for Modern Biology* — Holmes & Huber\n- \"Controlling the False Discovery Rate\" — Benjamini & Hochberg, *JRSS B* (1995)\n- \"The FAIR Guiding Principles for scientific data management\" — Wilkinson et al., *Scientific Data* (2016)\n- *Biostar Handbook* — Istvan Albert","html":"