Production data pipelines with Airflow
44%
Study time, last 7 days 330m this week
| Day | Minutes |
|---|---|
| Mon | 45 |
| Tue | 60 |
| Wed | 0 |
| Thu | 90 |
| Fri | 30 |
| Sat | 0 |
| Sun | 105 |
| Total | 330 |
Professional academy
Learn the craft behind the work that ships.
The skills your team actually needs, taught by people who ship.
Practice beats theory. We give you the reps.
Cohort-based courses for engineers, designers, and product teams who want to operate at a higher level.
Hands-on tracks in data, engineering, and product — built for teams that measure outcomes.
Studio-grade courses for designers, founders, and operators who want work that earns its place.
- 12 Courses
- 306h Total content
- 3 Instructors
Featured
Courses that earn their place
Data Cohort
Production data pipelines with Airflow
Design, ship, and operate reliable batch and streaming pipelines that survive contact with real traffic.
5 seats left of 24
$480
Product Hybrid
Product analytics for product managers
Read product data like a PM who shipped before — funnels, retention, and the questions that actually matter.
18 seats left of 30
$240
Engineering Self-paced
Systems design foundations
Build a mental model for design interviews and real architectures — without memorizing flashcards.
$320
How a cohort works
Five steps, from application to ship
A cohort is not a playlist. It is a sequence you move through with the same people, against the same project, with the same standard.
-
Apply for a seat
Cohorts are small on purpose. A seat is a commitment, not a transaction. You write a short application, we read it, and you hear back inside a week.
-
Kick off with the cohort
You meet the instructors and the cohort on day one. You leave with a plan, a partner for pair work, and the first assignment already in motion.
-
Build, week by week
Each week is a module, a live session, and a piece you ship. Feedback is specific and written. You do not move on by attending — you move on by shipping.
-
Operate against real traffic
The capstone runs against real, sandboxed traffic. You hold an on-call rotation with the cohort. The pipeline breaks the way production breaks, and you fix it.
-
Ship and certify
You finish with a portfolio piece, a written review from an instructor, and a certificate that maps to the skills you actually demonstrated.
From the cohort
What teams keep, after the cohort
Learning paths
A track, not a pile of courses
- Intermediate 90h
Data engineer track
Go from writing SQL to operating pipelines and serving models in production.
1 Foundations 2 Reporting 3 ServingOutcome: You can own a production pipeline and the model that runs on top of it.
- Advanced 62h
Product leader track
Move from shipping features to owning outcomes — analytics, pricing, and roadmaps.
1 Read the data 2 Set the price 3 Plan the workOutcome: You lead product decisions with data and can defend them up.
- Intermediate 82h
Design systems track
Own a design system from a single component to a governed system teams use.
1 Listen first 2 Build it right 3 Govern itOutcome: You ship and govern a design system that teams actually use.
For teams
Train a team, not just a person
Team plans include seats, a private cohort, a manager dashboard, and an account of what changed. Pricing scales with the people you actually train, with a license calculator that shows the math.
1
Seats that flex
Assign seats, reassign them when people move on, keep the license honest.
2
A manager dashboard
Progress, completion, and time-on-task — without surveillance theater.
3
A private cohort
Run a course for your team only, on your schedule, with your context.
Featured
Courses that earn their place
Data Cohort
Production data pipelines with Airflow
Design, ship, and operate reliable batch and streaming pipelines that survive contact with real traffic.
5 seats left of 24
$480
Product Hybrid
Product analytics for product managers
Read product data like a PM who shipped before — funnels, retention, and the questions that actually matter.
18 seats left of 30
$240
Engineering Self-paced
Systems design foundations
Build a mental model for design interviews and real architectures — without memorizing flashcards.
$320
At a glance
A catalog you can verify, not a number you have to trust
Every figure on this page is computed from the same data file the courses are built from. Change a course, and every count on the site changes with it.
- 12
- Courses
- 30h
- Lessons, on record
- 3
- Instructors
- 4
- Learning paths
- 81
- Lessons in total
Learning paths
A track, not a pile of courses
- Intermediate 90h
Data engineer track
Go from writing SQL to operating pipelines and serving models in production.
1 Foundations 2 Reporting 3 ServingOutcome: You can own a production pipeline and the model that runs on top of it.
- Advanced 62h
Product leader track
Move from shipping features to owning outcomes — analytics, pricing, and roadmaps.
1 Read the data 2 Set the price 3 Plan the workOutcome: You lead product decisions with data and can defend them up.
- Intermediate 82h
Design systems track
Own a design system from a single component to a governed system teams use.
1 Listen first 2 Build it right 3 Govern itOutcome: You ship and govern a design system that teams actually use.
For teams
Train a team, not just a person
Team plans include seats, a private cohort, a manager dashboard, and an account of what changed. Pricing scales with the people you actually train, with a license calculator that shows the math.
1
Seats that flex
Assign seats, reassign them when people move on, keep the license honest.
2
A manager dashboard
Progress, completion, and time-on-task — without surveillance theater.
3
A private cohort
Run a course for your team only, on your schedule, with your context.
How a cohort works
Five steps, from application to ship
A cohort is not a playlist. It is a sequence you move through with the same people, against the same project, with the same standard.
-
Apply for a seat
Cohorts are small on purpose. A seat is a commitment, not a transaction. You write a short application, we read it, and you hear back inside a week.
-
Kick off with the cohort
You meet the instructors and the cohort on day one. You leave with a plan, a partner for pair work, and the first assignment already in motion.
-
Build, week by week
Each week is a module, a live session, and a piece you ship. Feedback is specific and written. You do not move on by attending — you move on by shipping.
-
Operate against real traffic
The capstone runs against real, sandboxed traffic. You hold an on-call rotation with the cohort. The pipeline breaks the way production breaks, and you fix it.
-
Ship and certify
You finish with a portfolio piece, a written review from an instructor, and a certificate that maps to the skills you actually demonstrated.
Featured
Courses that earn their place
Data Cohort
Production data pipelines with Airflow
Design, ship, and operate reliable batch and streaming pipelines that survive contact with real traffic.
5 seats left of 24
$480
Product Hybrid
Product analytics for product managers
Read product data like a PM who shipped before — funnels, retention, and the questions that actually matter.
18 seats left of 30
$240
Engineering Self-paced
Systems design foundations
Build a mental model for design interviews and real architectures — without memorizing flashcards.
$320
Learning paths
A track, not a pile of courses
- Intermediate 90h
Data engineer track
Go from writing SQL to operating pipelines and serving models in production.
1 Foundations 2 Reporting 3 ServingOutcome: You can own a production pipeline and the model that runs on top of it.
- Advanced 62h
Product leader track
Move from shipping features to owning outcomes — analytics, pricing, and roadmaps.
1 Read the data 2 Set the price 3 Plan the workOutcome: You lead product decisions with data and can defend them up.
- Intermediate 82h
Design systems track
Own a design system from a single component to a governed system teams use.
1 Listen first 2 Build it right 3 Govern itOutcome: You ship and govern a design system that teams actually use.
Notes
Writing from the instructors
-
The pipeline after the notebook
Why most data pipelines break at the second stage, and the four changes that make them survive.
By Priya Nair -
Design systems nobody uses
Most design systems fail at adoption, not at craft. Here is what actually moves the number.
By Sara Lindqvist -
Reading an A/B readout
A short field guide to the four questions that separate a real result from a noisy one.
By Marco Reyes