System designHard~20 minCore Designs / 21 of 30

Interview question

Design an admin workflow where users upload a CSV or JSON file, preview validation results, and then confirm a bulk import.

Design bulk import preview and validation

Designs a safe admin import flow with upload staging, validation, preview, confirmation, idempotency, and rollback strategy.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

I would split the import into upload, validate, preview, confirm, and apply. The upload stores the file or parsed rows in staging and creates an import batch record. Validation checks schema, required fields, references, duplicates, limits, and permissions, then returns row-level errors and warnings. Confirmation starts the actual write only when the batch is valid enough for the chosen mode.

Full answer below

Practice focus

Import staging, validation, preview models, confirmation, partial failure behavior, idempotency, authorization, and operational safety.

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
Bulk imports create many records quickly, so small validation mistakes can become large data quality problems. A good workflow gives admins a preview and makes the final write deliberate.
I would split the import into upload, validate, preview, confirm, and apply. The upload stores the file or parsed rows in staging and creates an import batch record. Validation checks schema, required fields, references, duplicates, limits, and permissions, then returns row-level errors and warnings. Confirmation starts the actual write only when the batch is valid enough for the chosen mode.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would make apply behavior explicit: all-or-nothing, skip invalid rows, or import valid rows with a report. The system needs idempotency so refreshing the confirm request does not import twice. For large files, validation and apply can run as background jobs with progress and cancellation. The preview should show normalized values, not just raw file text, because admins need to see what the system will actually create.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would add quotas, malware checks for uploads, retention for staged files, and audit records for who imported what. I would store enough batch metadata to reproduce counts and diagnose failures without keeping sensitive raw data forever. The workflow would include a recovery plan: a compensating delete, a generated rollback batch, or clear manual repair guidance depending on the domain. Metrics would cover validation failure rate, import duration, row counts, and apply failures.

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

Writing directly to final tables during upload.
Only validating the file format, not domain references.
No idempotency around the confirm action.
No summary of what changed after the import.

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

Details

Cannot define partial failure behavior.
Ignores authorization for what the imported rows affect.
Has no staging or preview model.
No recovery story for bad imports.

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 choose all-or-nothing versus partial success?
How would you make confirm idempotent?
What data would you keep after the import finishes?

Continue the section

Next in Core Designs: Approval Workflow

Step 22 of 30

Design content approval and publishing

Opening drill

System designHard~20 minCore Designs / 21 of 30

Interview question

Design an admin workflow where users upload a CSV or JSON file, preview validation results, and then confirm a bulk import.

Design bulk import preview and validation

Designs a safe admin import flow with upload staging, validation, preview, confirmation, idempotency, and rollback strategy.

1Say itAnswer out loud first

2CompareCompare with Core answer

3RefineRefine with Stronger and Advanced

TL;DR

Full answer below

Practice focus

Import staging, validation, preview models, confirmation, partial failure behavior, idempotency, authorization, and operational safety.

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
Bulk imports create many records quickly, so small validation mistakes can become large data quality problems. A good workflow gives admins a preview and makes the final write deliberate.
I would split the import into upload, validate, preview, confirm, and apply. The upload stores the file or parsed rows in staging and creates an import batch record. Validation checks schema, required fields, references, duplicates, limits, and permissions, then returns row-level errors and warnings. Confirmation starts the actual write only when the batch is valid enough for the chosen mode.
Checkpoint
Stronger answer
Optional upgrade with examples, trade-offs, and sharper phrasing.
I would make apply behavior explicit: all-or-nothing, skip invalid rows, or import valid rows with a report. The system needs idempotency so refreshing the confirm request does not import twice. For large files, validation and apply can run as background jobs with progress and cancellation. The preview should show normalized values, not just raw file text, because admins need to see what the system will actually create.
Finish
Advanced answer
Optional deeper angle for production judgment and nuance.
In production I would add quotas, malware checks for uploads, retention for staged files, and audit records for who imported what. I would store enough batch metadata to reproduce counts and diagnose failures without keeping sensitive raw data forever. The workflow would include a recovery plan: a compensating delete, a generated rollback batch, or clear manual repair guidance depending on the domain. Metrics would cover validation failure rate, import duration, row counts, and apply failures.

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

Writing directly to final tables during upload.
Only validating the file format, not domain references.
No idempotency around the confirm action.
No summary of what changed after the import.

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

Details

Cannot define partial failure behavior.
Ignores authorization for what the imported rows affect.
Has no staging or preview model.
No recovery story for bad imports.

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 choose all-or-nothing versus partial success?
How would you make confirm idempotent?
What data would you keep after the import finishes?

Continue the section

Next in Core Designs: Approval Workflow

Step 22 of 30

Design content approval and publishing

Design an admin workflow where users upload a CSV or JSON file, preview validation results, and then confirm a bulk import.

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section

Design an admin workflow where users upload a CSV or JSON file, preview validation results, and then confirm a bulk import.

Practice focus

Answer path

Why this question matters

Review signals

Follow-up prompts

Continue the section