How do you paginate MongoDB results in an API?
PICTURE THIS: STACK VS QUEUE
Simple meaning
Offset pagination uses skip and limit, which is simple but slow on large skips.
WHY — MongoDB instead of guessing?
Why interviewers care about MongoDB:
question about MongoDB.
trade-offs, and what you would actually do on a Full Stack project - not buzzwords.
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:
- 1Offset pagination uses skip
and limit, which is simple but slow on large skips.
- 2Cursor pagination uses a
last seen _id or timestamp and a range query, which stays efficient.
- 3Always return a total
or a next-cursor so the React table can render pages.
- 4Give an example
One tiny concrete case you can say aloud.
- 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
Offset pagination uses skip and limit, which is simple but slow on large skips. Cursor pagination uses a last seen _id or timestamp and a range query, which stays efficient.