When users upload multiple résumés at once, the system handles each file independently, since not all files behave the same. Some upload successfully, some fail due to formatting issues, and others may still be in progress. To keep the workflow clear and prevent confusion, the interface separates files into three distinct buckets Uploading, Failed Uploads, and Successfully Uploaded so recruiters always understand the current state of the batch.

To preserve system stability, the “Parse Resumes” action is disabled while files are still uploading. This prevents users from accidentally triggering parsing on incomplete batches. If a user chooses to cancel the upload, only the files currently uploading are paused and moved into the Failed Uploads section, while all fully uploaded files remain intact. This ensures users never lose progress on successful uploads.

This approach reduces frustration by:

• Showing failures early rather than at the end

• Explaining why each file failed (e.g., unsupported format, wrong file type, corrupted file)

• Allowing users to remove or replace failed files without restarting the entire batch

• Keeping successfully uploaded files untouched and ready for parsing

• Preventing accidental parsing before all files are ready

Why it matters:

Large hiring teams often upload 30 -100 résumés at once. A single problematic file or an impatient click should not derail the entire process. This edge-case design ensures the workflow remains stable, transparent, and fully recoverable, even with large, messy data sets.