Home/Puestos relacionados con la IA/Ingeniero de datos
AI-native role

Ingeniero de datos

Makes your data AI-ready — pipelines, quality gates and retrieval foundations, because agents are only as good as what they can reach.

Start within 2 weeks 60-day trial CET ±1 · EN C1
What they do

The unglamorous work AI depends on.

01

Pipelines & warehousing

Reliable ETL/ELT into a warehouse your team and your agents can trust.

02

Embeddings & vector stores

The retrieval layer for RAG — chunking strategy, refresh jobs, index hygiene.

03

Data quality gates

Validation, deduplication and freshness checks — garbage stops before it reaches the model.

04

Schema & governance

Ownership, lineage and access — the audit answers before the auditor asks.

05

SaaS source integration

CRM, support, billing, product events — unified instead of scattered across ten tools.

06

Cost-efficient infrastructure

Storage and compute tuned so the data platform doesn't eat the AI budget.

When you need one

The moment this role pays for itself.

Hired the week someone admits the RAG demo fails because the data is the problem — scattered, stale, duplicated and unowned.

Signals we hear from clients
Retrieval returns garbage
The model is fine; the data isn't
Common trigger
Data scattered across tools
Ten SaaS silos, no single source of truth
Common trigger
Compliance needs lineage
Auditors and the EU AI Act ask where data comes from
Common trigger
How we vet

Vetted on the work, not the résumé.

Every data engineer on our bench has passed a role-specific battery — designed for the AI era, where the portfolio matters more than the years.

Pipeline design exercise

Messy multi-source data to unify — we score modeling choices and failure handling.

SQL & dbt depth

Hands-on, on real-shaped data. No whiteboard trivia.

Quality war stories

How they caught bad data before it hit production — or what they changed after it did.

Cost sense

We ask what their last platform cost and what they'd cut. Good data engineers know.

What good looks like

The first 90 days, concretely.

Every placement starts with agreed outcomes. This is the typical shape for a data engineer — calibrated to your context in the intro call.

01

Days 1–30

Audits sources, schemas and quality; the data map exists and the worst pipeline is stabilized.

02

Days 31–60

Core pipelines rebuilt with tests and freshness checks; the warehouse becomes trustworthy.

03

Days 61–90

Retrieval layer feeding AI features properly; lineage documented for the auditors.

On the bench

Skills you can expect.

SQLdbtPythonwarehousesvector databasesETL / ELTgovernanceAirflow
Related roles

Often hired together.

Ingeniero de IA Ingeniero de automatización con IA
Preguntas frecuentes

Hiring a data engineer, answered.

Straight answers to what clients ask before the first placement — the rest is a 30-minute call.

Do we need a data engineer before hiring AI talent?

If your data is scattered and unowned — often yes, or in parallel: AI features are only as good as retrieval, and retrieval is only as good as the pipelines behind it.

Which stack do they work in?

SQL and Python as the core; dbt, Airflow-class orchestration, the major warehouses and vector stores on top. Tooling follows your estate — the discipline is what's constant.

How is vetting different for AI-era roles?

Classic CV screening barely works for roles this new — so we vet on artifacts and exercises instead: shipped work, live design or build tasks, and evaluation-writing. The battery is role-specific and documented, so you see exactly what was tested.

How does the 60-day trial period work?

The first 60 days are the proof: if the match isn't right, the placement ends without long-term obligation — or we replace the profile. The risk of a wrong hire stays with us, not with you.

Where do these specialists work from?

From our network across the Netherlands, Ukraine, Hungary, Romania, Poland and Bulgaria — CET ±1 and fluent English, so they join your standups live. Probegin contracts and payrolls them; you get one Dutch counterparty.

Empieza esta semana

Meet your first data engineer candidates within days.

A 30-minute brief is all we need. Two to three vetted profiles follow — you interview, you choose.

Reserva una llamada de presentación