Build a Technical Debt Register for a Legacy Banking Monolith
Overview
What this challenge is about.
Run 8 structured 45-minute engineer interviews (template provided) capturing one debt item per pain point with reproducible evidence. Run SonarQube against the monolith for a quantified baseline. Classify each item in Fowler's quadrant (deliberate/prudent, deliberate/reckless, inadvertent/prudent, inadvertent/reckless) and estimate carrying cost (hours per month wasted) plus paydown cost (hours to fix). Deliver a structured register (40+ items), a one-page quadrant visualisation, and a 6-page executive brief framing the top 10 items as a budget request the CTO can take to the bank's investment committee.
The Brief
What you'll do, and what you'll demonstrate.
Make a 22-year-old banking monolith's technical debt visible, quantified, and quadrant-classified so leadership can fund the right paydown work.
Earning criteria — what you'll demonstrate
- Classify debt using Fowler's deliberate/inadvertent × prudent/reckless quadrant
- Quantify carrying cost from engineer time and incident data
- Use SonarQube findings to triangulate engineer-reported debt
- Translate technical debt into a budget-request artefact non-engineers act on
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.