Add candidates from resumes without waiting for AI processing

Finish the durable upload first

Candidate uploads from both the Dashboard and Candidates page use the same parser and can recover contact details from image-only PDFs when ordinary text extraction is insufficient. Clear native-text resumes use their visible name and contact block without waiting for AI. Missing or unclear identity details, unusual layouts, and scans retain AI recovery. File type and size checks before saving remain required, and a dropped cover letter is still caught when the file is first read. Review and edit the extracted details as needed.

When a recruiter adds a candidate from the Candidates page, RecruitIQ now confirms success as soon as the candidate record, active resume file, content identity, and resume history are safely saved. Common PDF uploads no longer keep the form open while search and AI processing finish.

A name and either a valid email or phone number are enough to create a candidate. A missing optional contact does not hold up an otherwise clear resume. Fast extraction requires a clear visible owner in the resume itself; a filename or email-derived name is not enough. Recruiter edits are preserved if parsing finishes later.

Save without waiting for the final document check

Save no longer waits for the final check that the attached file is a resume rather than a cover letter. RecruitIQ confirms the save once the candidate and resume file are durably stored, and runs that check right after in the background.

If the background check decides the file looks like a cover letter, the candidate stays saved and the resume card on their profile shows "This looks like a cover letter, not a resume." Use Replace resume to add their resume, or Add document to keep the file as a cover letter. Replacing the resume clears the notice, and contact details are not filled in automatically from a flagged file.

While you type a name and email or phone number, RecruitIQ checks your organization for an existing candidate with the same details. If it finds one, the drawer offers to open or update that candidate before you click Save. Save still re-checks for duplicates when it writes, so a candidate added by a teammate in the meantime is not duplicated.

See the saved candidate without reloading

As soon as RecruitIQ has a durable candidate record, the Dashboard and Candidates views reconcile that exact person into the organization-scoped candidate list. Moving from the Dashboard to Candidates no longer requires a hard refresh to see the candidate that was just added.

The upload control still waits for the resume file and history to be safely stored before it reports the complete upload as successful. A filtered Candidates view continues to respect its active filters, with an Open candidate action available when the new record is outside the current result set.

Continue search and AI work in the background

After the durable save, RecruitIQ adds the resume to organization-scoped search and queues the normal AI candidate-profile process. Recruiters can leave the upload flow while experience, education, skills, categories, location enrichment, and other enriched profile details continue processing. When the same resume clearly supplies a missing contact, background processing can fill an empty field after the usual identity and duplicate checks. Existing or recruiter-edited contacts are preserved; conflicting or unverified contacts stay available for review rather than being silently substituted.

Search indexing still runs before AI profile generation. If automatic AI generation is disabled for the user or organization, the resume remains active and searchable processing follows the existing account settings.

Keep the existing resume safeguards

Manual uploads continue to accept PDF, DOC, and DOCX files up to 10 MB. Candidate identity checks, duplicate review, active-resume history, and existing-candidate replacement rules are unchanged.

Most ordinary PDFs should finish the interactive save quickly, but image-only PDFs, legacy Office conversion, a cold service, or a slow connection can still take longer. There is no fixed completion-time guarantee. Background profile completion time remains separate from the initial upload confirmation, and automatic enrichment follows the user and organization settings.