◆ Apache Airflow

Orchestrate jobs for data efficiency

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

The same task, four prompts

today's deadline · the next reviewer · the stuck moment · the pattern
AExecute — do the immediate taskSchedule the weekly inventory reconciliation job to run every Sunday at 1 AM, ensuring the…+
Schedule the weekly inventory reconciliation job to run every Sunday at 1 AM, ensuring the finance team has updated numbers by Monday morning.
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 we go live with the new customer segmentation model, optimize the data loading process…+
Before we go live with the new customer segmentation model, optimize the data loading process to run in under 30 minutes, prioritizing the most critical customer attributes first, so the marketing team can react to insights faster and avoid stale data.
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
CDecide — diagnose the stuck momentThe end-of-month financial reports are delayed again, and the CFO is pressing for an…+
The end-of-month financial reports are delayed, and the CFO is asking for answers.
The end-of-month financial reports are delayed again, and the CFO is pressing for an explanation. The data pipeline for general ledger seems to be the bottleneck, but I can't pinpoint why it's so slow this month. I'm afraid of missing the regulatory deadline. What's the best way to quickly identify the performance bottleneck and unblock the reports?
when the reply comes backPush once: ask it to sharpen the weakest part, and to say what it assumed. Helpful?
DBecome — change the patternI frequently find my data pipelines running slower than expected, leading to missed deadlines…+
My pipelines are often slow, leading to missed deadlines and frustrated stakeholders.
I frequently find my data pipelines running slower than expected, leading to missed deadlines and frustrated business users. This constant scramble to optimize after the fact is inefficient. What habit can I change to proactively design and monitor my data orchestration for efficiency, ensuring timely delivery every time?
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.