Optional: Enriching with an LLM
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 15 content (the capstone: end-to-end Azure data product, cross-track delivery, demo). Other weeks' career pages each cover their week's tool. Generic NL junior data-career content (salary bands, day-to-day work, what employers do not expect from juniors) lives in one shared page across the curriculum and is not repeated here.
The numbers below are indicative placeholders (~XX%) until measured from NL postings. Treat them as market signal, not precision.
| Skill / signal | Data engineer | Analytics engineer | Data scientist | Data analyst |
|---|---|---|---|---|
| End-to-end pipeline ownership | Very common (~XX%) | Common (~XX%) | Occasional (~XX%) | Rare (~XX%) |
| Azure (storage, containers, orchestration) | Common (~XX%) | Occasional (~XX%) | Rare (~XX%) | Rare (~XX%) |
| dbt in production | Common (~XX%) | Very common (~XX%) | Rare (~XX%) | Occasional (~XX%) |
| Airflow / scheduled workflows | Common (~XX%) | Occasional (~XX%) | Rare (~XX%) | Rare (~XX%) |
| Cross-team data contracts | Common (~XX%) | Common (~XX%) | Occasional (~XX%) | Occasional (~XX%) |
What this means in practice: employers rarely hire for "final project week" as a keyword. They hire for evidence you can own a batch data product: ingest real sources, model with tests, deploy on a schedule, and explain trade-offs to non-data teammates. Your demo and README are the portfolio proof.
Week 15 is interview practice disguised as a group project. Strong candidates:
Weak signals: SQL-only demo with no app UI, "it works on my laptop" with no schedule, cannot explain a teammate's ingestion path.
Junior postings typically want:
Medior postings add:
Your capstone role split (ingestion vs platform, then switch) mirrors how small data teams actually divide work.
Use something concrete, not generic:
Built and demo'd a scheduled Azure data pipeline (ingestion, dbt, Airflow) in a cross-functional team; published marts to a production Postgres schema consumed by a live web application.
Adjust the source and product name to your team's project.
| Topic | Strong answer shape |
|---|---|
| Why ACA for ingestion? | Short-lived batch job, pay per run, secrets from Key Vault, same image CI pushes on merge |
| Why dbt not Pandas? | Testable SQL models, lineage, team review; Pandas only with justification |
| Dev vs prod | Personal schemas and dev container locally; prod via merge + scheduled DAG |
| When source blocks cloud IPs | Detect 403 from ACA, prefer API with server-side access, document blocker |
| Inherited tool | Name one weakness in teammate's ingestion you found during handover review |
The capstone stack is one credible path, not the only one:
| Stack | How Week 15 transfers |
|---|---|
| Snowflake / BigQuery + dbt + Airflow | Same modelling and orchestration habits; swap warehouse and deploy target |
| Managed ELT (Fivetran, Airbyte) + dbt | Less custom ingestion code; contracts and marts thinking still apply |
| Spark / Databricks Jobs without Airflow | Platform differs; incremental models and job scheduling concepts transfer |
| Backend-owned analytics in app DB | You still need grain, tests, and publish discipline; sync boundaries matter more |
Frame the project as portable engineering habits, not "we used tool X."
If an interviewer asks "tell me about your final project," answer in 90 seconds:
<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; treat this page as Week-15-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.