PurPassionDigital / Everywhere

Machine Learning Engineer

The pull to understand what isn't yet understood

Discovery · Unknown → Known

The shape of the work

Pace
  • Patient work over a long time, where showing up matters most
  • A hard push you keep up for a long stretch
What your week looks likeQuiet stretches, then deadline storms
How much you move around at workScreen and chair, almost all day
Whether you can work from anywhereWork from anywhere with a signal or internet connection
How quickly you receive feedback on your workTakes a season or a project cycle
What you're actually working withNumbers, measurements, records — things you read on a screen / Concepts, theories, designs, stories — things you think up

Behaviours this work is made of

Core
  • Constructing from parts into a functional whole. Structural, assembled.
  • Manipulating variables, testing, seeing what happens.
  • Seeing structure or signal in what looks like noise.
  • Systematic, methodical pursuit of understanding.
Also present
  • Breaking something into its real components.
  • Applying systematic problem-solving to make things work reliably.
  • Taking something that works and making it work better.
  • Verifying whether something is true or works as claimed.

In words

Machine learning engineers build systems that learn from data instead of being explicitly programmed. Concretely: the work starts in front of a dataset — medical images, transactions, language samples, sensor readings — and the question is how to get a machine to recognise patterns in it that are actually useful. Which model architecture, which training approach, and how to tell whether it is genuinely learning or just memorising the examples it was given. The primary pull is Discovery: the work moves from "we do not know whether this signal is in the data" to "we do," one carefully designed experiment at a time.

The role is part science and part engineering. The science is hypothesis-driven — try an approach, measure, adjust, try again — and the engineering is making it survive contact with reality, because the model that performs beautifully in a notebook still has to run reliably at scale, handle messy real-world input, and fail safely rather than expensively. The gap between "works in the lab" and "works in production" is where much of the real work lives, which is why Creation and Resolution sit close behind the Discovery core.

There's a guide here if you want one

Kitsune can talk through anything on this page — whether it might suit you, what to do next, questions this page doesn't answer. Everything here is yours to read either way.

The public image is breakthroughs and frontier research; the daily reality for most ML engineers is data cleaning. The dataset is messy, incomplete, biased, or mislabelled, and more time goes to fixing the data than to building the model. The field's own joke — that machine learning is eighty percent data plumbing and twenty percent actual machine learning — is accurate, and the engineers who last are the ones who do not resent the plumbing.

This is also the corner of software changing fastest because of AI, which creates a strange recursion: the work is building AI while AI changes how AI gets built, and the tools from two years ago are often already outdated. [Inference, based on the field's recent trajectory rather than a cited forecast] the pace is exciting and destabilising at once, and it rewards engineers who are comfortable treating their own toolkit as provisional.

Entry typically requires more mathematical and statistical depth than other software roles — comfort with linear algebra, probability, and the mechanics of model training. Paths include computer-science or quantitative degrees (often with graduate study), specialised ML programmes, and self-directed routes backed by strong project work, though the bar for the data-heavy, research-adjacent roles tends to be higher than for general software engineering. Demonstrated experience taking a model from experiment to deployed system is the most persuasive hiring signal.

Before you go