OpenAPI
OpenAPI describes an HTTP API as a document: operations, JSON Schema payloads, reusable components and security schemes. Interviewers ask because a spec makes a contract testable and generatable.
part ofAPI stylesoverview, primer and where to startread it →on this pageshowhide
explore
- Spec Structure5 questions
- Schema Objects6 questions
- Parameters & Request Body5 questions
- Security Schemes5 questions
- Reuse & $ref5 questions
- Codegen & Tooling6 questions
- Backend Developerroleanchors this topic
- Frontend Developerroleanchors this topic
- Full Stack Developerroleanchors this topic
- Java Backend Developerroleanchors this topic
- Java SDETroleanchors this topic
- Kotlin Backend Developerroleanchors this topic
- QA Engineerroleanchors this topic
- AI Red Teamingrole
- API Designskill
- Forward Deployed Engineerrole
- Server-Side Game Developerrole
- Software Architectrole
questions
page 2 of 2How would you stop published OpenAPI documents from drifting away from the running services?
basics
~20 sMake the document impossible to bypass: one generation path per service, a CI check that fails when the regenerated spec differs from the committed one, publication from the deploy pipeline rather than by hand, and runtime checks that responses still match the schemas.
How do you decide whether to extract a schema into OpenAPI components or leave it inline?
basics
~20 sExtract when several operations genuinely describe the same thing and should change together; leave it inline when the shape is incidental to one operation. A shared component is a coupling decision — every consumer of every referencing operation inherits its changes.
showing 31–32 of 32