Parameterized Runs and Backfills
Assignment: Build an Orchestrated Data Pipeline
Week 11 Lesson Plan (Teachers)
Career relevance: Week 11 in the NL data job market
Going Further: Optional Deep Dives
This page answers two questions students ask every week: why am I learning this, and how does it help me find a job?
It is scoped to Week 11 content (orchestration, Airflow). Week-1, Week-6, and Week-12 versions of this page each cover their week's tool, not this one. Generic NL junior-data career content (salary bands, day-to-day work, what employers do not expect from juniors) lives in one shared place and is not repeated here.
The numbers below are a rough reading of public NL postings as of April 2026. They are indicative, not measured. A separate project crawls Dutch data postings and will replace the qualitative claims here with measured percentages once the dataset is ready; placeholders are marked ~XX% for that swap.
Orchestration is one of the most reliable signals in NL data engineer postings. Most postings either name Airflow directly or use a generic phrase like "experience with workflow orchestration tools" with Airflow as the first example. Roles that touch a production data pipeline are nearly always expected to know an orchestrator; roles that only query data (most analyst work) are almost never expected to.
Frequency by role (rough, based on scanning NL postings on Indeed / Glassdoor / DataJobs.nl in early 2026):
| Role | Postings mentioning Airflow | Postings mentioning any orchestrator |
|---|---|---|
| Data Engineer | ~XX% (high; majority) | ~XX% (very high) |
| Analytics Engineer | ~XX% (mid) | ~XX% (mid; often paired with dbt) |
| Data Analyst | ~XX% (low; single digits) | ~XX% (low) |
| Data Scientist | ~XX% (low-mid) | ~XX% (low-mid; often "nice to have") |
The directional shape (DE > AE > DS > DA) holds across NL job boards even without exact numbers. If you are aiming for Data Engineer roles, treat Airflow as table stakes. If you are aiming for Analytics Engineer, the focus is dbt and SQL; Airflow is a strong second skill but not always central. If you are aiming for Data Analyst, Airflow is a differentiator on your CV, not a requirement.
<aside> 📝 The crawler-backed version of this section will give measured per-role percentages. Until then, treat the table as a shape, not a statistic.
</aside>
Airflow dominates the NL market. Alternatives appear, but at much lower volumes:
Practical implication: knowing Airflow well covers the majority of the NL market and makes Dagster/Prefect easy to pick up later. The reverse (Dagster-only) leaves you behind on the largest hiring pool.
Postings phrase the Airflow expectation differently by level:
A common posting pattern is "Airflow experience is a strong plus" on a junior role: that means it is a tiebreaker, not a hard requirement. Showing up with a working DAG flips the tiebreaker in your favor.
The strongest single line you can put on a CV after this week is something like:
Built and operated an Airflow pipeline that ingests NYC TLC taxi data into Postgres, runs dbt transformations + tests, and supports idempotent backfills. Deployed via PR to a shared Airflow instance.
That sentence carries five recruiter keywords (Airflow, pipeline, dbt, idempotent, backfill) and one signal of operational maturity (deployed via PR to shared infrastructure). Compare to a weaker alternative like "Used Airflow to schedule a Python script," which says nothing about pipeline structure, idempotency, or testing.
If your assignment includes the Target tier (shared-Airflow deploy + runbook), add one more line:
Wrote the runbook covering the two most common failure modes (source 4xx and dbt-test failures) with first-response steps for each.
That line signals you have thought about operating the pipeline, not just shipping it. NL postings increasingly list "on-call", "data ops", or "incident response" as expectations, even at junior level.
When an interviewer asks "tell me about a data pipeline you have built", three sentences cover the assignment cleanly:
If the follow-up is "what would you do differently?", two honest answers work:
Either signals that you know where the project's edges are without overclaiming.
Useful to know, especially when reading senior-shaped postings that look intimidating:
If a posting demands all three of the above for a "junior" role, the level is mislabeled. That is a useful filter, not a gap in your skills.
<aside> 💭 For generic NL junior data-career content (salary bands, day-to-day work, what employers do not expect from any junior), one shared page across all weeks is the right home. That page does not exist yet; for now, treat this page as Week-11-specific only.
</aside>
The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*
Built with ❤️ by the HackYourFuture community · Thank you, contributors
Found a mistake or have a suggestion? Let us know in the feedback form.