Eight roles, described by what you do on a Tuesday rather than by what the job advertisement says. Including the ones nobody tells students exist.
Deep-science roles divide most usefully along two axes: how much of your day is spent at a bench and how much is spent writing code. Roles that are genuinely half of each are rare and usually represent two jobs a company has not yet separated. The qualification employers ask for is frequently not the one the work requires, and the gap is largest at the computational end.
Advice on careers in deep science tends to describe fields rather than jobs: nanotechnology is exciting, biotechnology is growing, AI is everywhere. None of that helps someone decide what to do, because you do not do a field. You do a job, on a Tuesday, with specific tools, and either the shape of that day suits you or it does not.
So here are eight real roles, described by the day.
The day: reading papers, implementing something from one, and discovering it does not reproduce. Long stretches of debugging training runs that fail silently. Occasional experiments that work.
Asked for: BTech or MS. Actually weighs: a portfolio of work where you handled real, messy data and can explain your choices. This is the role where demonstrated work most clearly outranks credentials.
The day: pipelines, file formats, and statistics. A great deal of the work is getting data from one tool's output into another tool's input without silently corrupting it. The biology arrives in short, high-value bursts.
Asked for: MSc in a life science plus genuine Python or R. The common failure: people who have one half and assume the other is a weekend's work.
The day: setting up simulations, waiting for cluster time, and interpreting results against experimental data that rarely agrees exactly. Heavier physics than the other two.
Asked for: usually a PhD, and here that is genuine rather than a filter — the judgement about which approximations are safe is hard to acquire otherwise.
The day: running TEM, AFM or XRD on other people's samples, and telling them what their material actually is rather than what they hoped. Substantial instrument time, substantial image interpretation.
Asked for: MSc plus instrument training. Why it is underrated: the skill transfers across every materials employer, the instruments are expensive enough that trained operators are scarce, and almost nobody chooses it deliberately.
The day: programming liquid handlers, integrating instruments that were not designed to talk to each other, and translating a biologist's protocol into something a robot executes identically every time.
Asked for: BTech plus enough protocol literacy to know why a step exists. Growing quickly, and sits in a gap that neither pure engineers nor pure biologists usually fill.
The day: taking something that works in a flask and making it work in a reactor. Mixing, heat transfer, yield, cost per gram. Deeply unglamorous and the stage where most materials projects actually die.
Asked for: chemical or mechanical engineering. Why it matters: discovery is oversupplied with people and scale-up is not.
The day: executing protocols, keeping cell lines alive, and recording everything. Repetitive by design, because reproducibility requires it.
Asked for: BSc or MSc. This is the standard entry point into biotechnology and the role where hands-on competence is established.
The day: reading patents, drafting submissions, and working out whether a planned experiment infringes something. Science degree plus a great deal of careful writing.
Why students never consider it: nobody mentions it. It pays well, it is stable, and it needs people who genuinely understand the science rather than lawyers who have read a summary.
You can practise machine learning tonight with a laptop. You cannot practise nanotechnology or wet-lab biology without a facility, and that asymmetry should weigh heavily on how you choose a programme. For the computational path, what you build matters more than where you studied. For the other two, access to instruments and bench time is most of what a programme is actually providing.
Entry-level machine learning is crowded — the low barrier that makes it learnable also makes it competitive. Characterisation, scale-up and regulatory work are not crowded, are hiring, and are almost never chosen on purpose. That gap is an opportunity for anyone willing to take a role that does not sound impressive at a family dinner.
Machine learning engineering, on average and by a clear margin, particularly at senior levels. Process engineering and regulatory work are more stable and less exposed to hiring cycles.
For research-lead and computational materials roles, usually. For applied machine learning, characterisation, automation, process engineering and regulatory work, usually not — and a PhD taken for the wrong reason costs five years.
Along an axis, easily — research associate to characterisation specialist is a normal path. Across both axes at once is hard, because you are changing tools and evidence standards simultaneously.
For computational roles: one project where the data was genuinely messy and you can explain every decision. For bench roles: documented hands-on time. In both cases specificity beats breadth — one thing you can discuss in depth outranks six you cannot.
What machine learning has actually changed in biology, what it has not, and why the loop between a prediction and a measurement is still the part that takes months.
A working order for reading a paper outside your field — figures first, abstract last — and the four questions that separate a supported claim from a plausible one.
AI, nano and bio compared on the axes that decide it in practice: what you need to start, how fast the feedback comes, and whether you can practise without a facility.
