APIs

Practice APIs interview questions

API interviews are about the contract you would publish, not only the handler you would write.

API interview preparation is practice with resources, errors, versioning, auth, and idempotency, then testing whether you can explain those choices. NerdBeing asks the questions in that form.

What API interviews actually cover

Expect questions on REST versus RPC, how you version without breaking clients, where auth lives, what you return on a partial failure, and how you make a POST safe to retry. Pagination, rate limits, and timeouts come up as soon as the API is public.

How to practice

Work through one decision per question. Compare two shapes of an endpoint, then read why one of them is painful for clients. That is closer to a backend round than generating another CRUD controller.

What you practice

REST
Versioning
Auth
Idempotency
Pagination
Errors
Rate limits
Timeouts

Questions about APIs interviews

What API design questions do interviewers ask?

How you model resources, version a contract, authenticate a client, and make writes retryable. They often add load: pagination, rate limits, and what the client should do when a dependency is slow.

Is this only REST trivia?

No. The point is the engineering judgement behind an API: contracts, failure, and how the rest of the system talks to it.