Concept questionMedium~7 min

Interview question

How would you shape an EF Core query for an API list that needs related names and summary counts?

Project an EF Core query into an API DTO with nested summary data

Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would start from the response DTO and select only the fields the API needs. For example, an order list might project order id, status, customer name, created time, and item count. EF Core can translate many projections and aggregates into SQL, so the database does the set-based work. I would avoid loading full entities and then mapping in memory when the endpoint only needs a summary.

Full answer below

Practice focus

DTO projection, query shape, aggregation, nested data, row multiplication, and API read-model boundaries.

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
API list and detail screens usually need purpose-built read shapes rather than complete tracked entity graphs. Projection can push related names, counts, totals, and selected fields into set-based SQL while keeping payloads bounded.
I would start from the response DTO and select only the fields the API needs. For example, an order list might project order id, status, customer name, created time, and item count. EF Core can translate many projections and aggregates into SQL, so the database does the set-based work. I would avoid loading full entities and then mapping in memory when the endpoint only needs a summary.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would pay attention to cardinality. Many-to-one values such as customer name usually project cleanly, while one-to-many collections can multiply rows or create heavy nested results. For counts or totals, I would use aggregate expressions in the projection. For nested collections, I might use a separate query keyed by parent ids or a purpose-built read model. The shape needs to keep SQL understandable and the payload bounded.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would validate the generated SQL and page behavior with realistic data. A projection can still be slow if it contains expensive filters, correlated subqueries, or missing indexes. I would measure duration, logical reads, and row counts, and I would keep endpoint contracts stable so future fields do not casually expand the query into a large graph. The API read model and SQL read path need to evolve together.

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

Loading full entities for a list endpoint that needs a few fields.
Computing counts in memory after loading child rows.
Ignoring one-to-many row multiplication.
Adding response fields without checking generated SQL.

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

Details

Cannot explain projection versus entity loading.
Does not consider aggregation in SQL.
Has no answer for nested collections.
Ignores realistic data volume.

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 would you use two queries instead of one projection?
How would you return child counts efficiently?
What generated SQL would you inspect?

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.

API Read Shape

Opening drill

Concept questionMedium~7 min

Interview question

How would you shape an EF Core query for an API list that needs related names and summary counts?

Project an EF Core query into an API DTO with nested summary data

Explains EF Core projections for API read models that need related names, counts, and summaries without loading full graphs.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

DTO projection, query shape, aggregation, nested data, row multiplication, and API read-model boundaries.

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
API list and detail screens usually need purpose-built read shapes rather than complete tracked entity graphs. Projection can push related names, counts, totals, and selected fields into set-based SQL while keeping payloads bounded.
I would start from the response DTO and select only the fields the API needs. For example, an order list might project order id, status, customer name, created time, and item count. EF Core can translate many projections and aggregates into SQL, so the database does the set-based work. I would avoid loading full entities and then mapping in memory when the endpoint only needs a summary.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would pay attention to cardinality. Many-to-one values such as customer name usually project cleanly, while one-to-many collections can multiply rows or create heavy nested results. For counts or totals, I would use aggregate expressions in the projection. For nested collections, I might use a separate query keyed by parent ids or a purpose-built read model. The shape needs to keep SQL understandable and the payload bounded.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would validate the generated SQL and page behavior with realistic data. A projection can still be slow if it contains expensive filters, correlated subqueries, or missing indexes. I would measure duration, logical reads, and row counts, and I would keep endpoint contracts stable so future fields do not casually expand the query into a large graph. The API read model and SQL read path need to evolve together.

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

Loading full entities for a list endpoint that needs a few fields.
Computing counts in memory after loading child rows.
Ignoring one-to-many row multiplication.
Adding response fields without checking generated SQL.

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

Details

Cannot explain projection versus entity loading.
Does not consider aggregation in SQL.
Has no answer for nested collections.
Ignores realistic data volume.

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 would you use two queries instead of one projection?
How would you return child counts efficiently?
What generated SQL would you inspect?

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.

API Read Shape

How would you shape an EF Core query for an API list that needs related names and summary counts?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper

How would you shape an EF Core query for an API list that needs related names and summary counts?

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue practice

Go deeper