Grokking Modern API Design Interview
REST, GraphQL, gRPC and event driven interfaces compared on the criteria that actually decide between them: coupling, versioning, latency and who pays the cost of a change. API design rounds are increasingly common and rarely prepared for.
Course
Web Development
Design Gurus
2 weeks
Intermediate
Subscription
What it covers
Interface design as a first class topic. Resource modelling and REST done properly rather than as a naming convention, GraphQL and the problems it solves along with the ones it creates, gRPC and when binary protocols earn their complexity, event driven interfaces, plus pagination, idempotency, versioning, authentication and rate limiting.
Why it is worth a separate course
APIs are the part of a system that is hardest to change, because the cost of a breaking change lands on people you cannot reach. Interviewers know this, which is why a candidate who talks about versioning strategy and idempotent writes unprompted stands out immediately.
How to use it
Take an API you have built and redesign it against the material. The specific things you got wrong are what you will remember.
Best for: backend and platform engineers, and anyone whose loop includes an API design stage.
Ready to start?
Opens on Design Gurus in a new tab.
Stuck on something specific?
Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Every session is free; a few slots open each week.
Follow along
New writing, resources and project ideas land here first.