The Scenario
A public library wants a small internal system so staff can look up members, check out books, and see who currently holds which book. There are about 3,000 members and 12,000 books. The backend will be built by a single junior developer.
The Brief
Produce a clear, minimal REST API spec. You do not need to write any implementation code. The goal is to demonstrate that you can scope an API, choose the right resources, and think about edge cases.
Deliverables
- A list of resources and the endpoints for each (method, path, one-line purpose)
- Request and response examples (JSON) for at least 3 key endpoints
- Two edge cases you deliberately designed around (for example, what happens if someone tries to check out a book that is already out)
- One thing you intentionally left out of v1 and why
Submission Guidance
Over-specification is a failure mode here. Aim for crisp and minimal, not exhaustive.
Submit Your Work
Your submission is graded against the rubric on the right. If you pass, you get a public Badge URL you can share on LinkedIn. There is no draft save, so work offline first and paste your finished response here.