Bulk-importing data

When you're loading more than a handful of applicants or jobs, use Data Import instead of the per-record dialogs. Bulk imports are PDF-based (and URL-based for jobs) — there is no spreadsheet workflow.

The Data Import section has four pages, surfaced as left-hand sub-tabs once you click Data Import in the sidebar.

---

Applicant Import

Data Import → Applicant Import. One drop zone:

• Drop a folder of resume PDFs onto the zone, or click to browse.
• One applicant is created per PDF.
• Skills extraction starts immediately and runs in the background — you don't have to wait for it on this page.

Use Applicant Import after an in-person event, when migrating from another tool, or any time you have many resumes already in hand.

---

Job Import

Data Import → Job Import. Two paths, side by side:

• Paste posting URL. Paste a link to a public job posting and click Add. Careers fetches the page, parses the JD, and queues skills extraction.
• Drop JD PDFs. Drop a folder of JD PDFs (or a single PDF) onto the right-hand zone. One job is created per PDF.

You can mix both paths in a single session — paste a few URLs, then drop a folder.

All jobs created through this page land in Uploaded Jobs and become editable. (The Public Jobs feed is curated by Mapademics and isn't populated through bulk-import — see Jobs — Public vs Uploaded.)

---

Import History

Data Import → Import History. A flat audit log of every past import.

Filter the list by type with Filter by type at the top. There's no detail row click-through here — to investigate a specific extraction, look at Background Tasks (below).

---

Background Tasks

Data Import → Background Tasks. The live monitor for skills extraction.

A single import (one applicant, one job, or many of either) usually creates one background task per record. Two sub-tabs:

• Resumes — extraction tasks for applicant resumes.
• Job Descriptions — extraction tasks for jobs.

The number on each tab is the task count.

For each task you'll see:

• Job Name — the internal task identifier (Task <id>).
• Status — Completed (green), Failed (red), or in-progress.
• Progress — a bar showing how much of the task is done. The label is items completed / total items.
• Items — totals broken out: how many records the task processed and how many succeeded.
• Created — when the task started.

This is the right place to look when an import seems "done" on the Import History page but the new applicant's skills haven't shown up yet — extraction may still be running.

---

When a task is Failed

A Failed task means extraction did not complete for that record. The applicant or job still exists, but the Resume & Skills or Required Skills view will be empty for the failing record.

What to do:

1. Re-upload the file. Most failures are recoverable. Open the applicant's profile and upload the same resume as a new version (or, for a job, click Extract Skills on the Required Skills panel). A fresh task starts.
2. Check the file itself. Scanned-image PDFs without OCR'd text, password-protected PDFs, and very low-resolution images are the most common causes. Re-export from the source if you can.
3. If the same file fails twice in a row, contact Support with the task ID.

---

Next steps

• Adding applicants
• Uploaded Jobs
• Support