Build a Technical Debt Register for a Legacy Banking Monolith
Overview
What this challenge is about.
Build a Technical Debt Register for a Legacy Banking Monolith. Advanced challenge in analysis. Analyzing real datasets and building models that drive decisio...
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.
This is not a data exercise. It is the work an analyst does when stakeholders need answers from messy data. That distinction matters to every hiring manager who has seen candidates describe statistical methods and none who have extracted insight from messy, real-world data.
When you finish, you will have something most graduates do not: a real-world deliverable, verified by Ewance, that you can show to a hiring manager and say "I did this. Here is the proof."
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.
Technical Debt Management
Master · Software Engineering
Strong alignment
This challenge maps to Technical Debt Management at the Master level. It sharpens the same practical skills your coursework expects — but in a real industry context with actual constraints and deliverables.
Skills
Skills you'll demonstrate.
Each one shows up on your verified credential.
- Technical Debt
Apply technical debt to solve real industry problems and demonstrate production-level capability.
- Debt Quadrant
Apply debt quadrant to solve real industry problems and demonstrate production-level capability.
- Code Quality
Apply code quality to solve real industry problems and demonstrate production-level capability.
- Stakeholder Communication
Apply stakeholder communication to solve real industry problems and demonstrate production-level capability.
- Static Analysis
Apply static analysis to solve real industry problems and demonstrate production-level capability.
- Refactoring
Apply refactoring 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: