Code Review
If you like applying Code Review, every challenge here gives you a chance to practice it on a real industry brief.
- CodeBeginnerNew
Refactor a Tangled Java Pricing Engine With Design Patterns
Start from a provided Java 21 codebase with the legacy PricingEngine class, 38 example fixtures (input cart, expected price), and one failing test demonstrating a bug from last …
- Java
- Design Patterns
- Refactoring
Open coursework - StrategyBeginnerNew
Set Up Trunk-Based Development on a 3-Branch Workflow
Audit the current branch + merge data over 8 weeks (frequency, conflict count, time-to-green). Pick one product team for a 4-week pilot: introduce a feature-flag system (Unleash…
- Version Control
- Trunk Based Development
- Feature Flags
Open coursework - CodeIntermediateNew
Specification-First Refactor of a Payments Module
Read the module, the last 12 months of incidents touching it, and the existing tests. Write a 6-page specification using a precondition / postcondition / invariant format per pu…
- Specifications
- Refactoring
- Characterization Testing
Open coursework - CodeIntermediateNew
Refactor a Big-Ball-of-Mud Java Servlet Application
Week 1: install JUnit 5 + Testcontainers harness, write characterization tests for the 2 target workflows (PolicyIssue + ClaimSubmit) reaching at least 80 percent branch coverag…
- Refactoring
- Characterization Testing
- Legacy Systems
Software Evolution and Maintenance 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
- CodeBeginnerNew
Add a Test Harness to an Untested Open-Source CLI
Fork the repo (test mirror provided), set up Vitest with coverage and a CI workflow that fails under 75 percent on the targeted modules. Write characterization tests first (asse…
- Unit Testing
- Integration Testing
- Test Coverage
Software Construction - ResearchIntermediateNew
Design an Empirical Study of Pull Request Review Throughput
Using the provided pull request dataset and the stakeholder brief, design and run an empirical software-engineering study on review throughput. State three falsifiable hypothese…
- Empirical Software Engineering
- Software Analytics
- Statistical Analysis
Open coursework - StrategyBeginnerNew
Code Review Bootcamp for an Early-Stage Mobile Team
Read the team's last 100 merged PRs (export provided) and tag the 10 worst review threads (rubber-stamp, bikeshed, missing context). Draft a 4-page code-review guideline coverin…
- Code Review
- Team Coaching
- Process Design
Software Construction - DesignIntermediateNew
Design an Upstream Contribution to a CNCF Service-Mesh Project
Using the internal fork dossier (case-file) for the business context, the prior rejection feedback, and the targeted roadmap area, design an upstream contribution that a careful…
- Oss Contribution
- Rfc Design
- Pr Etiquette
Open coursework - Browse challenges
Explore role
Product Manager
Ship product that solves real user problems. Combine user research, prototyping, and stakeholder alignment to turn ambiguous briefs into measurable wins — the role at the centre of modern software teams.
- CodeIntermediateNew
Debug a Race Condition in a Real-Time Collaboration Service
Build a deterministic load-test harness (k6 or Playwright) that reproduces the corruption within 3 attempts on a clean local stack. Capture traces with OpenTelemetry to localize…
- Debugging
- Concurrency
- Load Testing
Software Construction
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.