API design and a production bug
Design a small REST API for bookings, then find and fix the bug behind a real-looking incident report.
What you hand in
Your design and your bug write-up as text (code blocks welcome), or a link to a gist or repository.
How it's marked
A person scores each line from 0 to 4. Lines carry different weight. You pass with 70% or more of the weighted total and no line at 0.
| What's marked | Weight |
|---|---|
| API designEndpoints, status codes and payloads are sensible and consistent. | ×3 |
| ConcurrencyDouble booking is prevented in a way that holds under load. | ×3 |
| DebuggingFinds the real cause (email before commit) and fixes it properly. | ×2 |
| TestingThe proposed test would actually fail before the fix. | ×1 |
| CommunicationClear enough for a teammate to act on without a meeting. | ×1 |