Data engineer, London.
The eight weeks nobody puts in the press release.
R.02 · Digital & AI
The role
ServiceDigital & AI
OfficeLondon, hybrid
LevelConsultant
Salary£85–105k, no bonus, published band
Closes17.10.26
What the role is for, and who it is for.
You will build the data foundations under every Digital & AI engagement (ownership, definitions, quality gates, lineage) in the client’s environment and repository, alongside their engineers. The role is measured on whether the model that follows holds a year later.
You will
01Rebuild field definitions, ownership and lineage from source to decision.
02Wire quality gates into the client's pipeline so bad data fails loudly.
03Pair with the client's engineers so the handover is a formality.
04Write the evaluation harness and agree thresholds before launch.
You have
Shipped data pipelines that other people depended on, in a regulated setting.
Opinions about definitions of 'customer' and the scars to back them.
Comfort in someone else's codebase, under someone else's access controls.
If two of these are true and the third is close, write anyway.
What it is not.
A candidate who discovers these in week three has been sold a brochure. They are here so nobody is.
A research role. You will not train novel models; you will make existing ones trustworthy.
A greenfield role. Every environment is someone else's.
How we hire, in order.
The page is about a number you moved and how you know. We read every one; a partner, not a screener.
With the partner for the service. You ask most of the questions.
Three hours with an anonymised ledger from a closed engagement. We want to see how you check a number, not whether you get the answer we got.
Paid. You sit in on live work and we sit in on you.
From a published band. No negotiation theatre: the band is the band.