What is JSON and why is it commonly used?

Q: What is JSON and why is it commonly used?

**Target Audience:** Engineers preparing for JavaScript fundamentals and data-interchange interview questions. **Difficulty:** Easy > **How to read this doc:** Concepts are explained in plain language first, then tagged with 📌 Interview term: . Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text. ## 1. Why This Even Matters — A Story First Imagine shipping a package overseas. A JS backend, a Python service, and a Java service all have their own native ways of representing data in memory, and none of those internal representations can survive being copied directly to another language. JSON is the neutral shipping crate everyone agreed on: strip a value down to plain text built from just a handful of universal building blocks (strings, numbers, booleans, null, and nested arrays or objects), so that whatever opens the crate on the other side can read it correctly, regardless of what language se

The problem

Question presented to candidate: "What is JSON, and why do you think it became the default format for APIs and config files instead of just sending native language objects?"

What a strong answer should cover:

JSON (JavaScript Object Notation) is a lightweight, text-based data format for exchanging structured data, and despite the name it is language-independent -- Python, Java, Go, and every other mainstream language can read and write it.
JSON supports exactly six kinds of values: objects, arrays, strings, numbers, booleans, and null -- notably no functions, no undefined, no Date, no Map or Set, no BigInt.
JSON.stringify() serializes a JS value into a JSON string; JSON.parse() does the reverse; both accept an optional second argument (a replacer function/array, or a reviver function) for filtering or transforming values during the conversion.
JSON is stricter than a JavaScript object literal -- unquoted keys and trailing commas are both syntax errors to JSON.parse(), even though they would be perfectly valid inside real JS source code.
Real lossy edges worth naming unprompted: functions and undefined properties are dropped, Date becomes a plain ISO string (not restored as a Date on parse), Map and Set serialize to an empty object, BigInt throws, and a circular reference throws a TypeError.

Clarifying questions expected:

"Do you want me to also cover structuredClone as a modern alternative for deep cloning, or keep this focused on JSON itself?"

Code / implementation expected: Yes -- a short, runnable snippet demonstrating stringify/parse and the lossy edges.

json
data format
api
web

Try it yourself

Sketch your approach before you read the solution. That is what the interview tests.

Stuck? Get a hint.

A short nudge toward the approach. It will not give the answer away.

Solution

Target Audience: Engineers preparing for JavaScript fundamentals and data-interchange interview questions. Difficulty: Easy

How to read this doc: Concepts are explained in plain language first, then tagged with 📌 Interview term:. Every result below was actually run on Node.js v24.19.0 — the printed output is real, captured output, not illustrative sample text.

1. Why This Even Matters — A Story First

Imagine shipping a package overseas. A JS backend, a Python service, and a Java service all have their own native ways of representing data in memory, and none of those internal representations can survive being copied directly to another language. JSON is the neutral shipping crate everyone agreed on: strip a value down to plain text built from just a handful of universal building blocks (strings, numbers, booleans, null, and nested arrays or objects), so that whatever

The solution is hidden so you can try first

8 min read · 9 sections

Run the code

Edit the code and run it here. Each console line with an expected value becomes a test.