> Markdown version of [/jobs/ext/3211411-data-engineer](https://www.wearedevelopers.com/jobs/ext/3211411-data-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Data Engineer

- **Company:** Planther Ltd
- **Location:** UK (Remote available)
- **Salary:** £40,000.0 - £55,000.0
- **Contract:** Permanent contract
- **Skills:** Query Performance, Artificial Intelligence, Databases, Data Control, Reverse Engineering, Automation Anywhere
- **Published:** September 2, 2026
- **Apply:** https://uk.indeed.com/viewjob?jk=97062e6a389a536a

## About the Role

We're not hiring against a set checklist. What matters most is that you're highly flexible, learn fast, and are willing to pick up whatever the data needs next - even when it's something you've never done before. Mid-level with high potential is the right picture: we care more about whether you can genuinely own things than about years served.

One thing that is crucial to the role: you're not wedded to your own way of working. We have established ways of building, and they'll keep evolving - we need someone who'll adopt them and change their habits when there's a better way.

You'll need the right to work in the UK. You must be entirely fluent in written and spoken English.

## Description

You'd work right across our data - getting it in, keeping it right, and getting it used.

You won't need prior experience across all of it. What matters is that you're willing to learn fast and be moulded by how we build and manage.

 * Getting it in. Writing the code that pulls data out of hundreds of separate sources.
 * Keeping it running. The pipelines, schedules etc that keep dozens of automated jobs fetching and refreshing on their own.
 * Making it usable. Cleaning, deduplicating and standardising it into a database the product can query.
 * Keeping it healthy. A database in the hundreds of millions of rows and growing. Query performance, storage, cost and monitoring.
 * Keeping it honest. Knowing what we hold, where it came from and how complete it really is, so the product never claims more than that.
 * Getting it used. Wiring each dataset into front end tools.

Development here is heavily AI-assisted. We build with AI coding agents day to day, and a lot of the routine data monitoring already runs as automated AI workflows. You should be keen to work that way - it's a big part of how a team our size delivers as much as it does.

Be aware: this is a demanding job. The breadth is unusual - one week you might be reverse-engineering a stubborn source, the next tuning a slow spatial query, the next reporting on what a dataset does and does not cover. You would be relied on across all of it, with an established framework that already does a lot of the heavy lifting and serious AI assistance behind you. We'd rather say that plainly now than surprise you later. If that range excites you rather than worries you, read on.