◆ Apache Airflow

Build an end-to-end ETL pipeline

This is real work, not a feature someone invented — it comes from real job ads and real questions people asked. Below are four ready AI prompts: get it done, make it easy for the next person to say yes to, work out the right move when you are stuck, and stop it coming back.

4prompts
See the prompt↓All Apache Airflow tasks

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskBuild an end-to-end ETL pipeline to ingest daily customer feedback data from the CRM, transform…+
Build an end-to-end ETL pipeline to ingest daily customer feedback data from the CRM, transform it into a sentiment score, and load it into the analytics database for the product team's dashboard.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
BImprove — make it easier to acceptBefore I finalize the ETL pipeline for customer feedback, design it to handle schema changes…+
Before I finalize the ETL pipeline for customer feedback, design it to handle schema changes gracefully and manage backfills for historical data without manual intervention. Ensure the transformation logic can be easily updated by the analytics team without needing a full redeploy, so the product team always has the most relevant sentiment insights.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentI'm building the new customer feedback ETL pipeline, and I'm struggling with how to ensure data…+
I'm halfway through building the new customer feedback ETL pipeline, and I'm stuck on data quality.
I'm building the new customer feedback ETL pipeline, and I'm struggling with how to ensure data quality at each stage. The raw data from the CRM is notoriously inconsistent, and I'm afraid of propagating bad data into the analytics database, which would mislead the product team. I don't know the most effective points to implement validation and error handling without over-engineering it. What's the likely diagnosis of where data quality usually breaks down in such a pipeline, and what's the best next move to build robust data validation?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternOur ETL pipelines frequently break whenever the source systems make schema changes, causing…+
Our ETL pipelines often break when source schemas change, leading to data outages.
Our ETL pipelines frequently break whenever the source systems make schema changes, causing data outages and frantic debugging for the analytics team. This constant reactive work is a huge time sink and erodes trust in our data. What habit should I change in how I design and build new ETL pipelines to make them more resilient to upstream schema evolution and reduce manual intervention?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?

Questions people actually ask

honest answers, no sign-up

Every task here was seen in the real world. Someone doing the job named it, a real job ad asked for it, or a lot of people asked about it online.

If nothing real showed a task, it is not on the page. That is the whole rule.

They are the same job approached four ways, because what you need depends on where you are.

Get it done today. Make it easy for the next person to say yes to. Work out the right move when you are stuck. Learn the pattern so the job stops coming back.

For most of these jobs it can carry the heavy thinking - draft it, sort it, check it, rehearse it with you.

It cannot sit in your chair, take the blame when a number is wrong, or notice what nobody wrote down. Let it do the first 80%. Keep the last 20% that is truly yours.

No. Copy any prompt and paste it into the AI you already use. No account, no score, no wall in the way.

Any of them. The prompts describe the work rather than naming a product, so they are not tied to one assistant.

That is also why they keep working when you switch.

Change it freely. Every prompt is a starting line, not a rule.

Put in your real numbers, your real names and your real deadline. The more you make it yours, the better the answer comes back.

The tasks come from real job ads, published job data and the questions people ask in public forums.

The steps come from Apache Airflow's own documentation, with practitioner sources for the traps the manual does not mention.

Push once. Ask it to sharpen the weakest part and to say what it assumed.

Most wrong answers come from a missing detail rather than a bad prompt - tell it the thing it could not know.