Where are data engineer roles actually advertised?

Why the obvious job boards are giving you so little

If you've been searching "data engineer" on LinkedIn and Indeed and getting a wall of noise or silence, that's not a sign you're doing something wrong. It's a sign those boards are the wrong instrument for this particular search. Data engineer postings on the big generalist boards are disproportionately reposts from applicant tracking systems (Greenhouse, Lever, Workday, SmartRecruiters) that are already live on the company's own careers page, often days or weeks earlier, plus a large volume of agency postings for the same handful of roles, plus roles that are technically open but functionally filled — the hiring manager has an internal candidate lined up and HR is running the req for compliance reasons. None of that is specific to data engineering, but it matters more here than in some fields because the title itself is unstable: "data engineer", "analytics engineer", "platform engineer (data)", and "ML infrastructure engineer" often describe near-identical work at different companies, which fragments the postings you'd otherwise find under one search term.

The practical fix isn't a better search string. It's going to where the postings originate rather than where they're aggregated.

Where the roles actually surface

Company engineering blogs and their own careers pages. Teams that run a real data platform — Snowflake or Databricks warehouses, Airflow or Dagster orchestration, dbt for transformation, Kafka for streaming — tend to write about their stack publicly before or around the time they hire for it. If a company's engineering blog has a post about migrating to Iceberg tables or rebuilding their ingestion layer, check their careers page directly; the req is often live there before it's anywhere else, and it's specific enough that you can address the exact problem in your application rather than a generic job description.

Hacker News "Who is Hiring" thread. Posted on the first weekday of each month. It's unfiltered and text-only, but data platform and infrastructure roles show up in volume, many from companies that don't otherwise advertise, and you can search past threads by keyword (dbt, Airflow, Spark, Kafka, warehouse) going back years.

r/dataengineering and the dbt Community Slack. The dbt Slack in particular has a jobs channel used by companies already running dbt in production — which tells you something about the maturity of the data function before you even apply. Locally Optimistic's Slack (aimed at analytics and data leadership) carries similar postings, skewed toward more senior or lead roles.

Specialist newsletters. Data Engineering Weekly aggregates roles alongside its technical content. It's a smaller pool than a job board but a more relevant one — the roles listed tend to be for teams doing the kind of work the newsletter covers, not generic BI support dressed up with the title.

Wellfound (formerly AngelList) and We Work Remotely for startup and remote-first data roles specifically — useful if you're targeting smaller companies building a data function from scratch rather than joining an established platform team.

None of these replace the generalist boards entirely — plenty of legitimate roles do sit on LinkedIn — but they surface roles earlier and with better signal about the actual tech stack and team maturity, which matters more in data engineering than in roles where the tooling is less varied.

Agencies and recruiters: what they actually do here

Data engineering has its own specialist recruitment agencies, distinct from general tech recruiters, because the skill set (distributed systems, warehouse modelling, orchestration, sometimes streaming infrastructure) doesn't map cleanly onto a generalist software engineering search. In the UK, Harnham and Understanding Recruitment both run dedicated data engineering desks and are worth being on the books of even when you're not actively looking, because they see roles before they're advertised publicly — companies frequently give an agency first refusal for a few weeks to avoid the volume of a public posting. Nigel Frank International specialises specifically in the Microsoft data stack (Azure Synapse, Fabric, Power BI, SQL Server), which is a distinct niche from the Snowflake/Databricks/open-source side that most other data recruiters focus on — worth knowing if your stack skews Microsoft, because a generalist data recruiter may not have the right requisitions.

What agencies are genuinely good for: contract and interim data engineering work (data migration projects, warehouse rebuilds with a fixed scope), and roles at companies that don't want to run a public search. What they're less good for: getting you into a role you're not already a close match for on paper — the agency is paid by the employer to filter, not to advocate for a stretch candidate, so a CV that doesn't already show the specific tools in the job spec (a named cloud warehouse, a named orchestrator, a named streaming system) is unlikely to get put forward regardless of your ability to pick the tool up.

One UK-specific mechanic worth knowing if you do contract work: IR35 status determinations affect which contract data engineering roles are actually open to you as an outside-IR35 contractor versus requiring you to go on an umbrella company or client payroll. Agencies handling contract data engineering roles will tell you the determination up front — it's worth asking before you invest time in the process, because it changes the take-home rate materially.

Internal movement: the roles you never see advertised

A meaningful share of data engineering hiring doesn't go through any external channel at all. The two common internal paths are:

• Analyst or BI developer to data engineer, within the same company, as the data function matures and someone who's been writing SQL against the warehouse for two years is given the remit to also build and own the pipelines feeding it. This is a training-and-promotion path, not a recruitment event, so there's no posting to find.
• Software engineer into a platform or data team, particularly at companies scaling their data infrastructure — a backend engineer who's touched Kafka or built internal tooling around the data warehouse gets pulled sideways into the data platform team as headcount opens up.

This doesn't mean external hiring doesn't happen — it clearly does — but it does mean that a company's public job board is not a complete picture of who they're bringing into data engineering roles this quarter. It's part of why a direct approach to a specific team (referencing a specific piece of infrastructure they've written about, or a specific gap you can see in their public data documentation or job history) sometimes gets a reply when a generic application to the same company's open req doesn't: you're reaching past the point where the internal candidate has already been considered and ruled out or in.

Timing and seasonality

Data engineering hiring follows budget cycles more than most tech roles, because headcount for a data platform team is usually tied to a specific infrastructure project (a warehouse migration, a new pipeline for a product launch) rather than steady-state growth. That produces some patterns worth knowing:

• New fiscal year, new headcount. For companies on a calendar fiscal year, new reqs tend to open in January as budgets are confirmed. For UK companies on an April fiscal year, expect a similar bump from March into April.
• November and December are slow for new postings but not for process — roles opened in October often run their interview process through the end of the year, so a lack of new adverts doesn't mean a lack of active hiring.
• Notice periods lengthen the pipeline. Senior data engineers in the UK are frequently on one to three months' notice, so a company that's found their preferred candidate may leave a req open (and visible) for months after they've effectively stopped considering new applicants, because the incumbent is still working out their notice elsewhere.

None of this is a reason to time your search around the calendar — it's a reason not to read a quiet October or a crowded January as a signal about your own candidacy.

What to do with this

Pick three specific companies whose stack matches yours (same warehouse, same orchestrator) and check their careers page and engineering blog directly this week, rather than searching a board. Get onto the books of one specialist data recruiter whose focus matches your stack — Harnham or Understanding Recruitment for general data engineering, Nigel Frank if you're Microsoft-stack — even if you're not actively applying anywhere yet. Read the next Hacker News "Who is Hiring" thread in full rather than skimming; it takes twenty minutes and the roles in it don't show up on the generalist boards at all. And if reading every advert closely enough to know which of these channels to prioritise, and where your specific pipeline experience does and doesn't match what's being asked for, is itself the bottleneck, that's the specific problem jobmarket.pro is built to take on.