Candidate Experience
What actually happens to a candidate's data, from clicking Apply to hearing back.
Candidate experience is usually discussed in terms of interface polish — how many fields a form has, how fast a page loads. Those things matter, but this page focuses on something candidates ask about less often yet arguably care about more once they know to ask: what actually happens to their CV and personal information after they hit submit, and what fairness commitments the platform can back up mechanically rather than just promise.
On this page
01The apply flow itself
Applying takes a name, email, optional phone and current title, an optional cover letter, and a CV upload — deliberately minimal, because every additional required field measurably reduces completion rates, and there's no legitimate reason to ask for more at the application stage than a recruiter needs to make an initial screening decision. There's no forced account creation; a candidate applies and is done, without being funnelled into a password-setup flow they didn't ask for.
02What happens to a CV after upload
The uploaded file is parsed to extract raw text, then run through a pattern-based stripping process that removes names, email addresses, phone numbers, physical addresses, postal codes, social-media and professional-network URLs, and language suggestive of age, gender, nationality, or marital status — eleven distinct pattern categories in total. Only this anonymised text is sent to the AI extraction step described on the CMS page; the AI performing the semantic reading never sees who the candidate is.
This stripping is pattern-based, not perfect — an unusual name format or an indirect reference to a protected characteristic embedded in prose (rather than a labelled field) can occasionally slip through, and we say this plainly rather than overclaiming a guarantee the mechanism can't fully back. It substantially reduces exposure; it does not eliminate every possible signal, and no automated system can honestly promise that it does.
03Data retention and deletion
A candidate's application data, including their CV file, is retained for 24 months from the date of application, after which it is automatically deleted rather than retained indefinitely by default — a nightly process identifies and removes expired records without requiring a candidate or recruiter to request it manually. This window balances a hiring team's legitimate interest in reconsidering past applicants for a newly-opened role against a candidate's interest in not having their personal data held forever by a system they applied to once, two years ago, for a job that's long since been filled.
04A new option: full profile control on the country job site
Because the ATS itself doesn't offer candidates a login of their own — recruiters need administrative access, candidates generally don't — an application now also creates (or reuses, if one already exists) a real account on the destination country's own Expertini job site, where the candidate can log in, see their application status, update their CV, and browse other roles. This account creation is disclosed in the consent checkbox at the point of application, and a temporary password is emailed immediately so the account is usable right away.
Platform architecture & operations
A1How this is architected in the platform
Candidate Experience is not a bundle of point products — it is a slice through one platform. The platform is deliberately server-rendered: every view is prepared by the application server and shipped as complete HTML, with no client-side framework, no third-party CDN scripts, and no build pipeline between the data and the page. What renders is what the server computed — the property that makes the interface auditable.
All persistence runs on a single search-native document store; every query carries the organisation's identifier as a mandatory filter at the lowest query layer. Tenant isolation is therefore structural — a property of how every request is composed — rather than a policy that relies on application code remembering to check.
Every capability referenced on this page resolves to a registered tool or connector: the tools directory and the integrations catalogue are renderings of the same registries the application enforces at runtime, so what this page describes and what the product gates can never drift apart.
A2Operational and audit posture
Screening is deterministic and published — the same inputs produce the same outputs, hard requirements block rather than average away, and the methodology is public on the research page. Actions that touch external systems are explicit and journalled per event; usage reporting aggregates the same journals the actions write, not a parallel telemetry system.
Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.
Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.
Frequently asked questions
Does the AI screening a CV know the candidate's name, age, or gender?⌄
How long is my application data kept?⌄
Do I need to create a password to apply?⌄
Can I apply if I'm not currently based in the job's country?⌄
At a glance
- Sub-2-minute mobile-friendly apply flow
- 11-pattern PII stripping before any AI analysis
- Automatic 24-month data expiry, no request needed
- No forced account creation on the ATS
- Automatic profile account on your local Expertini site
- Plain-language consent, not buried legalese
See candidate experience on your own hiring.
Bring a real job description to a 30-minute demo — free trial included.
Book a demo