Comparison questionEasy~7 minPrompting & Structured Output / 7 of 20

Interview question

Compare plain JSON output, JSON mode, and schema-constrained output.

Separates prompt-requested JSON, parseable JSON modes, and provider-enforced schema adherence.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Asking for JSON in ordinary text gives no formal guarantee. A JSON mode generally guarantees parseable JSON but not a particular shape. Schema-constrained output asks the provider to produce a response matching a supported schema. Even then, the application must validate business meaning because schema-valid data can still be wrong.

Full answer below

Practice focus

Whether the candidate understands syntax guarantees, schema guarantees, semantic limits, and provider capability differences.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
These options solve different levels of the output-contract problem and should not be described as interchangeable.
Asking for JSON in ordinary text gives no formal guarantee. A JSON mode generally guarantees parseable JSON but not a particular shape. Schema-constrained output asks the provider to produce a response matching a supported schema. Even then, the application must validate business meaning because schema-valid data can still be wrong.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
If I need a final classification with a fixed category and explanation, I prefer structured output with an enum and required fields when the chosen model supports it. If only JSON mode is available, I parse and validate against my own schema and handle failures explicitly. For human-facing prose, forcing JSON may add complexity with no benefit.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
Provider implementations differ in their supported JSON Schema subsets, model families, streaming behavior, refusal handling, and latency. I verify those capabilities for the selected model instead of assuming a schema is portable. Where possible, deployment validates or compiles the schema and exercises refusal and truncation paths before traffic arrives. The application keeps one stable internal contract while provider adapters translate it into the parameters each API supports.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Claiming JSON mode guarantees a supplied schema.
Treating parseable JSON as semantically correct.
Using structured output for every human-readable response.
Assuming all providers support the full JSON Schema standard.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Downstream code trusts model-produced JSON without validation.
Unsupported schema keywords are silently assumed to work.
Refusals and incomplete responses are parsed as ordinary results.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When is plain text the better contract?
What remains to validate after schema adherence?
How would you handle a provider without structured outputs?

Continue the section

Next in Prompting & Structured Output: Design an output schema

Step 8 of 20

How would you design a useful JSON schema for model output?

Practice route

Read core answer Review checklist Follow-up prompts Track progress

Finished this drill?

Practice freely. Sign in only when you want to save completion, confidence, notes, or bookmarks.

New to Aporeon? Create account

Drill details

Human editorial direction

Aporeon is shaped by Aleksandar Tomovski, a software developer with experience on both sides of technical interviews. Content is reviewed for accuracy, natural spoken delivery, useful depth, and honest trade-offs.

About the creator Editorial standards

Was this drill useful?

Help improve the interview library.

Found this answer useful?

Say thanks with a standalone, one-time $5 contribution. No account required.

No subscription or perks.Choose another amount

Opening drill

Comparison questionEasy~7 minPrompting & Structured Output / 7 of 20

Interview question

Compare plain JSON output, JSON mode, and schema-constrained output.

Separates prompt-requested JSON, parseable JSON modes, and provider-enforced schema adherence.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Whether the candidate understands syntax guarantees, schema guarantees, semantic limits, and provider capability differences.

Answer first

Answer path

Core answer first, then checkpoints toward a stronger answer.

Start
Core answer
Start here. This is the direct spoken answer to practice first.
Overview
These options solve different levels of the output-contract problem and should not be described as interchangeable.
Asking for JSON in ordinary text gives no formal guarantee. A JSON mode generally guarantees parseable JSON but not a particular shape. Schema-constrained output asks the provider to produce a response matching a supported schema. Even then, the application must validate business meaning because schema-valid data can still be wrong.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
If I need a final classification with a fixed category and explanation, I prefer structured output with an enum and required fields when the chosen model supports it. If only JSON mode is available, I parse and validate against my own schema and handle failures explicitly. For human-facing prose, forcing JSON may add complexity with no benefit.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
Provider implementations differ in their supported JSON Schema subsets, model families, streaming behavior, refusal handling, and latency. I verify those capabilities for the selected model instead of assuming a schema is portable. Where possible, deployment validates or compiles the schema and exercises refusal and truncation paths before traffic arrives. The application keeps one stable internal contract while provider adapters translate it into the parameters each API supports.

Review signals

Use these to catch weak phrasing, shallow reasoning, and risky claims.

Common mistakesCandidateCommon mistakesMistakes that weaken the answer or signal shallow understanding.Open details

Details

Claiming JSON mode guarantees a supplied schema.
Treating parseable JSON as semantically correct.
Using structured output for every human-readable response.
Assuming all providers support the full JSON Schema standard.

Red flagsCandidateRed flagsSignals that an interviewer may treat as risky.Open details

Details

Downstream code trusts model-produced JSON without validation.
Unsupported schema keywords are silently assumed to work.
Refusals and incomplete responses are parsed as ordinary results.

Follow-up prompts

Quick interviewer prompts inside this drill.

Follow-up questionsCandidateFollow-up questionsLikely next questions after the main answer.Open details

Details

Treat these as the next interviewer turn. Answer one out loud, then save the gap in your practice notes.

When is plain text the better contract?
What remains to validate after schema adherence?
How would you handle a provider without structured outputs?

Continue the section

Next in Prompting & Structured Output: Design an output schema

Step 8 of 20

How would you design a useful JSON schema for model output?

Compare plain JSON output, JSON mode, and schema-constrained output.

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section

Compare plain JSON output, JSON mode, and schema-constrained output.

Practice focus

Answer path

Overview

Review signals

Follow-up prompts

Continue the section