Candidate Experience. Bulk job imports and dedicated recruiting email

Managing your job architecture and recruiting communications just got easier to do at scale. Bulk-import jobs from a CSV, and give the Candidate engine its own dedicated email setup, separate from your core platform.

Bulk job imports

Upload up to 10,000 job records in a single CSV. The system detects existing jobs by their External ID - updating what's already there and creating what's new - links jobs to existing locations or creates them from your file, and supports pipe-delimited reporting hierarchies (for example L1:Product|L2:Design). The import experience matches your existing Candidate Import workflow, so it's familiar from the first upload.

Every import gets a detailed history: a live status while it's processing, who uploaded it, success and failure counts for the batch, and a downloadable error file with the precise reason behind any failed row - so you can fix and re-import right away.

A dedicated email setup for recruiting

Candidate emails can now run on their own configuration, fully separate from your core platform's email settings: an independent SMTP server if you want one, a dedicated "from" address (like careers@yourcompany.com), and a delivery mode - default, custom email, or SMTP - that you set for candidates without touching your employee engagement settings. The two stay strictly isolated, so a recruiting-side configuration change can never affect email delivery on your core platform.

Also new for Candidates

Hiring-manager surveys. Candidate surveys can now go to the candidate's Hiring Manager instead of the candidate directly - checked daily, in your account's timezone, against the candidate's Date of Joining, and sent to the mapped hiring manager the moment it arrives, so they can share feedback on the candidate's onboarding and early experience.

Date of Joining. A Date of Joining field is now part of every candidate's record, available through the API and in the UI - the same field the hiring-manager survey above uses to know when to send, and a foundation for tracking onboarding timelines more broadly. Included for any account with Candidate Experience enabled, no separate request needed.

Lifecycle stage mapping. Candidates can now be mapped to a lifecycle stage using more than one condition at once, instead of just a single parameter - with custom conditional logic resolving the right stage dynamically, for mapping requirements too complex for a single rule to handle.