Technical Debt
If you like applying Technical Debt, every challenge here gives you a chance to practice it on a real industry brief.
- AnalysisIntermediateNew
Build a Technical Debt Register for a Legacy Banking Monolith
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 qu…
- Technical Debt
- Debt Quadrant
- Code Quality
Technical Debt Management - StrategyBeginnerNew
Negotiate a Technical-Debt Paydown Budget Into the Roadmap
Using the engineering debt case file, build a debt-paydown budgeting framework that fits the sprint cadence and committed work shown in the roadmap snapshot. For each of the thr…
- Technical Debt
- Stakeholder Communication
- Refactoring Budgets
Open coursework - DesignBeginnerNew
Backfill Architecture Decision Records for a Mainframe Modernization Program
Work entirely from the three provided materials: the architecture-channel chat log excerpt (architecture-channel-log), the consolidated architecture-review meeting notes (archit…
- Architecture Decision Records
- Technical Debt
- Stakeholder Communication
Open coursework - CodeIntermediateNew
Refactor the Untouchable ReturnsProcessor Class Safely
Start from the representative ReturnsProcessor module extract and the behavior contract supplied in the provided materials, and use the change-and-incident history to decide whe…
- Refactoring
- Mikado Method
- Characterization Testing
Open coursework Practice your coursework on real scenarios.
Every challenge is shaped from real-world context — not generic exercises. The work mirrors what your degree prepares you for.
Why Ewance
- AnalysisIntermediateNew
Technical-Debt Quantification for an Acquired SaaS
Run a static-analysis sweep (SonarQube + custom dependency scripts) and a 4-hour structured walkthrough with the acquired team's 3 senior engineers. Categorize debt into: code-q…
- Technical Debt
- Code Analysis
- Estimation
Software Evolution and Maintenance - DesignIntermediateNew
Rate and Reduce Technical Debt in a Telecom OSS Codebase
Design a SQALE-based technical-debt rating and improvement proposal for Lumera Telekom's OSS. Using only the static-analysis findings export, the module inventory and rating gri…
- Sqale Method
- Technical Debt
- Code Quality
Open coursework
How it works
From brief to credential, in six steps.
Step 01
Browse challenges aligned to your studies.
Step 02
Accept the one that fits your goals.
Step 03
Work through it with AI Copilot guidance.
Step 04
Submit for structured evaluation.
Step 05
Earn a verified credential.
Step 06
Add it to LinkedIn with one click.
Industry teams behind a decade of practitioner briefs
Hiring from this pool?
Sponsor a challenge and meet candidates through actual work.
Industry teams can shape briefs around the skills they hire for, then evaluate students on rubric-scored deliverables — not resumes.