API Design Internship Interview Questions for Freshers (with Answers)
By K. Boopathikumar, CEO & Founder · 16 November 2026 · 7 min read
API design interns help build interfaces other developers depend on. Interviews test whether your APIs are consistent, predictable, secure and well documented.
Design
- How do you name REST resources? Plural nouns for collections (/students), ids for items (/students/42), nesting only for clear ownership (/students/42/marks).
- PUT vs PATCH? PUT replaces the whole resource; PATCH changes only the fields sent.
- Which status code for validation errors? 400 Bad Request, or 422 Unprocessable Entity, with a body listing each field error.
- How should errors be returned? A consistent JSON shape with a code, a human message and details, never a stack trace.
Scale and evolution
- Offset vs cursor pagination? Offset (page=3) is simple but slow and inconsistent on large changing data; cursor pagination uses a pointer to the last item and stays stable.
- How do you version an API? In the URL (/v1) or a header, adding fields without breaking clients and announcing removals early.
- What is a breaking change? Removing or renaming fields, changing types or meanings, or tightening validation that old clients fail.
- What is rate limiting and how do you signal it? Capping requests per client; return 429 with a Retry-After header.
Security and docs
- API keys vs OAuth? API keys identify an application; OAuth lets users grant limited access to an app without sharing passwords.
- What is OpenAPI? A standard description of an API's endpoints, inputs and outputs that generates docs, tests and client code.
- REST vs GraphQL? REST has fixed endpoints per resource; GraphQL has one endpoint where clients ask for exactly the fields they need.
- What is idempotency and why does it matter for payments? Repeating a request has the same effect as once; idempotency keys stop double charges when clients retry.
How to answer well in the interview
- Show an OpenAPI file from your project.
- Explain one design decision and its trade-off.
- Mention backward compatibility in every change.
- Keep error formats consistent and show an example.
Next steps
- Study the free API Design learning path and take its module quizzes for a free certificate.
- Follow the API Design skill track from basic to advanced.
- Do real, reviewed work in a API Design internship and keep every project in your own GitHub.