Skip to contentSkip to content
Verified credentials. On-chain. Forever.Learn more
Ewance
Sign in
Cover image for Design a Versioning Strategy for a Public REST API
Design

Design a Versioning Strategy for a Public REST API

FreeVerified credential3 weeksAdvanced

Overview

What this challenge is about.

Design a Versioning Strategy for a Public REST API. Advanced challenge in design. Designing real products under real constraints, earn a blockchain-verified ...

CredentialBlockchain-anchored
ShareableLinkedIn-ready
LanguageEnglish
PaceSelf-paced

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.

This is not a design exercise. It is the work a product designer does between a brief and a shipped interface. That distinction matters to every hiring manager who has seen candidates redesign Spotify's homepage and none who have worked under real product constraints.

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

  • 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.

API Design and GraphQL

Master · Software Engineering

Strong alignment

This challenge maps to API Design and GraphQL at the Master level. It sharpens the same practical skills your coursework expects — but in a real industry context with actual constraints and deliverables.

One more thing

You can put a credential on your CV by Friday.