Overview
What this challenge is about.
Run static dependency analysis on the monolith (using Packwerk + custom Ruby AST scripts, both available) to surface the current implicit modules and the worst cross-module dependencies. Hold a 1-day boundary-design workshop with 8 tech leads to map proposed modules using the dependency report + bounded contexts. Ship the pilot: migrate 2 modules (Quotes + ClaimsIntake) into explicit Packwerk packs with public APIs and zero cross-pack constant violations. Author a 12-month migration plan covering remaining ~18 modules, prioritization (highest violation count first), and a quarterly KPI dashboard (violation count, cycle-time per module, build-time per module). Deliver dependency report, boundary design, pilot PR series, migration plan, and KPI dashboard.
The Brief
What you'll do, and what you'll demonstrate.
Design module boundaries from dependency analysis, ship a 2-module Packwerk pilot, and plan a 12-month modular-monolith migration for a 600K-LOC Rails codebase.
Earning criteria — what you'll demonstrate
- Surface implicit module boundaries from static dependency analysis
- Design explicit module APIs in a Packwerk-style modular monolith
- Plan a multi-year migration with leading + lagging KPIs
- Sequence pilot vs full-migration work to maintain delivery throughput
Program Fit
Where this fits in your program.
Sharpens the same skills your degree expects you to demonstrate.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
Careers
Roles this prepares you for.
Real titles. Real skill bridges. Pick the one closest to your trajectory.
Career mappings coming soon.