Why do list APIs paginate instead of returning every row?
PICTURE THIS: HOW TO EXPLAIN IT
Simple meaning
Unbounded lists blow up memory, latency, and mobile data.
WHY — Pagination instead of guessing?
Why interviewers care about Pagination:
on Pagination.
the situation, the default choice, and one exception - that reads as experience.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1Unbounded lists blow up
memory, latency, and mobile data.
- 2Pagination returns a slice
plus a cursor or page number so clients load more on demand.
- 3Even internal admin screens
should page
- 4a million-row JSON payload
is a production incident.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
Unbounded lists blow up memory, latency, and mobile data. Pagination returns a slice plus a cursor or page number so clients load more on demand.