Concept questionMedium~7 min

Interview question

How would you implement keyset pagination for a large EF Core-backed API list?

Implement keyset pagination with EF Core

Explains stable EF Core pagination using cursor predicates, deterministic ordering, and index-aligned queries.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I first define a deterministic order, for example CreatedAt DESC, Id DESC, where Id breaks timestamp ties. The cursor contains the last row's ordering values. The next EF Core query applies the equivalent seek predicate, orders by the same columns, and takes one bounded page. That avoids the growing skip cost of deep offset pages and gives more stable navigation while rows are being inserted.

Full answer below

Practice focus

Cursor pagination, deterministic ordering, LINQ predicates, indexes, filter interaction, and API contract design.

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.
Why this question matters
Pagination sits at the boundary between API design and database performance. EF Core makes offset pagination easy, but large and changing lists often need a cursor-style approach.
I first define a deterministic order, for example CreatedAt DESC, Id DESC, where Id breaks timestamp ties. The cursor contains the last row's ordering values. The next EF Core query applies the equivalent seek predicate, orders by the same columns, and takes one bounded page. That avoids the growing skip cost of deep offset pages and gives more stable navigation while rows are being inserted.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
For descending order, the next-page predicate is CreatedAt < lastCreatedAt || (CreatedAt == lastCreatedAt && Id < lastId). I encode those values into an opaque, versioned cursor and bind it to the active filter and sort contract so it cannot be reused with a different query. The database needs an index aligned with the fixed filters and ordering. Keyset pagination does not support arbitrary page numbers naturally, so offset pagination can still be the clearer choice for small, stable admin lists.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I define the consistency users should expect when rows are inserted, removed, or updated between page requests. Keyset pagination prevents the shifting cost of OFFSET, but a row whose sort key changes can still move across the traversal, so mutable ordering fields need deliberate product semantics. I fetch one extra row to determine whether another page exists and keep page size bounded. Cursor decoding validates version, shape, and value ranges without treating opacity as authorization; tenant and permission filters are always rebuilt on the server. I inspect the generated SQL and plan for both common and worst-case filters, and regression tests cover tied sort values, forward navigation, changed filters, and malformed cursors.

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

Sorting by a non-unique field without a tie-breaker.
Using a cursor after changing filters or sort order.
Implementing keyset logic in memory after loading rows.
Offering many sort options without matching indexes.

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

Details

Cannot explain what values go into the cursor.
No deterministic ordering.
Ignores index support for the order.
Treats pagination as only a frontend concern.

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.

How would the LINQ predicate look for descending sort?
What happens when filters change?
When is offset pagination still fine?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

Keyset Pagination

Opening drill

Concept questionMedium~7 min

Interview question

How would you implement keyset pagination for a large EF Core-backed API list?

Implement keyset pagination with EF Core

Explains stable EF Core pagination using cursor predicates, deterministic ordering, and index-aligned queries.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Cursor pagination, deterministic ordering, LINQ predicates, indexes, filter interaction, and API contract design.

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.
Why this question matters
Pagination sits at the boundary between API design and database performance. EF Core makes offset pagination easy, but large and changing lists often need a cursor-style approach.
I first define a deterministic order, for example CreatedAt DESC, Id DESC, where Id breaks timestamp ties. The cursor contains the last row's ordering values. The next EF Core query applies the equivalent seek predicate, orders by the same columns, and takes one bounded page. That avoids the growing skip cost of deep offset pages and gives more stable navigation while rows are being inserted.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
For descending order, the next-page predicate is CreatedAt < lastCreatedAt || (CreatedAt == lastCreatedAt && Id < lastId). I encode those values into an opaque, versioned cursor and bind it to the active filter and sort contract so it cannot be reused with a different query. The database needs an index aligned with the fixed filters and ordering. Keyset pagination does not support arbitrary page numbers naturally, so offset pagination can still be the clearer choice for small, stable admin lists.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I define the consistency users should expect when rows are inserted, removed, or updated between page requests. Keyset pagination prevents the shifting cost of OFFSET, but a row whose sort key changes can still move across the traversal, so mutable ordering fields need deliberate product semantics. I fetch one extra row to determine whether another page exists and keep page size bounded. Cursor decoding validates version, shape, and value ranges without treating opacity as authorization; tenant and permission filters are always rebuilt on the server. I inspect the generated SQL and plan for both common and worst-case filters, and regression tests cover tied sort values, forward navigation, changed filters, and malformed cursors.

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

Sorting by a non-unique field without a tie-breaker.
Using a cursor after changing filters or sort order.
Implementing keyset logic in memory after loading rows.
Offering many sort options without matching indexes.

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

Details

Cannot explain what values go into the cursor.
No deterministic ordering.
Ignores index support for the order.
Treats pagination as only a frontend concern.

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.

How would the LINQ predicate look for descending sort?
What happens when filters change?
When is offset pagination still fine?

Continue practice

Move to the linked follow-up, next path step, prerequisite, or deeper variant.

1 linked

Go deeper

Practice the next layer of the same subject.

Keyset Pagination

How would you implement keyset pagination for a large EF Core-backed API list?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper

How would you implement keyset pagination for a large EF Core-backed API list?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper