Overview
What this challenge is about.
Receive the OpenAPI spec for the 14 endpoints, 8 months of partner-support tickets tagged 'breaking-change', and the partner-mix breakdown (which endpoints which partner uses). Evaluate URI-path versioning (/v2/expenses), header-based versioning (Accept: application/vnd.fintech.v2+json), and evolution-only (additive-only) against client effort, server complexity, and rollback safety. Recommend one. Write a 15-page RFC covering the chosen scheme, the 12-month migration plan (per endpoint), deprecation policy, and the partner-communication plan. Include a worked example for the highest-traffic endpoint.
The Brief
What you'll do, and what you'll demonstrate.
Recommend a public-API versioning strategy and produce a 12-month migration plan that protects 4,500 SMB customers across 14 endpoints.
Earning criteria — what you'll demonstrate
- Compare URI, header, and evolution-only versioning honestly
- Audit an existing OpenAPI surface for breaking-change patterns
- Design a migration plan that respects existing customer code
- Write an RFC that earns engineering and partner sign-off
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.