MediumExperience level: 3-5 years · 8-15 years1 min read

JSON Schema — Interview Questions

Reviewed by Gurusankar M.

Asked inAmazonMicrosoftDeloitteAccenture
#json#json schema#validation#contract#openapi
Report issue

Short Answer

JSON Schema is a standard, itself written in JSON, that describes the expected structure of JSON data — types, required properties, formats, ranges, enums, and nested shapes. It's used to validate payloads, document and enforce API contracts, generate code/forms, and catch bad data automatically instead of with hand-written checks.

On this page

Concept Made Simple

Coffee Chat Question

“What is JSON Schema and why is it useful?”

Remember It Faster

Mind Map Answer

What
JSON that describes JSON
Declares
type, required, format, min/max, enum
Uses
validation, docs, contracts, codegen
Powers
OpenAPI request/response schemas

Learn by Doing

Hands-on Keyboard

json
{
  "type": "object",
  "required": ["name", "email"],
  "properties": {
    "name":  { "type": "string", "minLength": 1 },
    "email": { "type": "string", "format": "email" },
    "age":   { "type": "integer", "minimum": 0 }
  },
  "additionalProperties": false
}

Think Beyond the Expected

What If?

What does "additionalProperties": false do, and why does it matter?

It rejects any property not listed in the schema. That's useful for security and strictness — it blocks unexpected/extra fields (helping prevent mass assignment and typos), so the payload must match the contract exactly. Leaving it true (the default) lets clients send arbitrary extra keys, which the validator will silently allow.

Real World

JSON Schema underpins OpenAPI/Swagger: request and response bodies are described with it, driving validation, interactive docs, mocking, and client SDK generation from one source of truth.

Interviewer's Expectation

Keywords they're listening for:

  • JSON describing JSON
  • type/required/format/constraints
  • validation & contracts
  • additionalProperties
  • backs OpenAPI

Common Mistakes

  • Confusing JSON Schema with a JSON sample
  • Leaving additionalProperties open when strictness is needed
  • Duplicating schema logic in code instead of reusing it

Best Practices

  • Keep one schema as the source of truth
  • Use additionalProperties:false for strict inputs
  • Generate docs/clients from the schema

Follow-up Questions

  1. How does JSON Schema relate to OpenAPI?
  2. What does additionalProperties control?
  3. How do you validate against a schema at runtime?

Continue Learning with AI

Take this question deeper with your favourite AI assistant. Pick a depth, copy the prompt, or open it directly — AI is your learning companion, not a shortcut.

Plain-language foundations

I'm preparing for a software engineering interview and want to understand this from scratch, as a beginner.

Topic: Schema (JSON)
Interview question: "What is JSON Schema and why is it useful?"

Please:
1. Explain the core idea in simple, plain language, using an everyday analogy.
2. Define any technical terms you use.
3. Walk through one small, concrete example.
4. Finish with a single sentence I can easily remember.

Keep the tone friendly and assume I'm new to this topic.
Open inChatGPTGeminiClaude

Was this answer helpful?

Affiliate links

Tools for Your Developer Workspace

Equipment for a comfortable, productive setup.

As an Amazon Associate I earn from qualifying purchases.