Overview
What this challenge is about.
Set up Nx for affected-graph computation across 14 services, parallelize GitHub Actions jobs, benchmark the pipeline, and deliver configs plus a verifiable certificate.
The scenario
The devtools SaaS (around 30 engineers, trunk-based deployment, no formal release cadence) sells on its own engineering velocity — slow CI is both a productivity tax and a marketing problem.
The Brief
What you'll do, and what you'll demonstrate.
Cut monorepo CI from 47 minutes to under 12 minutes commit-to-deploy with affected-only builds + tests across 14 services.
Earning criteria — what you'll demonstrate
- Use a monorepo build tool's affected-graph to skip unaffected work
- Configure remote build cache that is shared across CI and developer machines
- Parallelize CI jobs with matrix strategies bounded by runner concurrency
- Diagnose cache-miss spikes and adjust hashing inputs accordingly
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Aligned coursework coming soon.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Ci Cd
Apply ci cd to solve real industry problems and demonstrate production-level capability.
- Monorepo
Apply monorepo to solve real industry problems and demonstrate production-level capability.
- Nx
Apply nx to solve real industry problems and demonstrate production-level capability.
- Github Actions
Apply github actions to solve real industry problems and demonstrate production-level capability.
- Remote Cache
Apply remote cache to solve real industry problems and demonstrate production-level capability.
- Affected Graph
Apply affected graph to solve real industry problems and demonstrate production-level capability.
Careers
Career paths this challenge builds toward
Completing this challenge demonstrates skills that transfer directly to these roles: