Application access and lifecycle

A Talent applicant account is separate from an Infra One platform user. Both sessions can exist in the same browser, but each product checks its own identity and signing out of one does not sign out the other. The active Talent applicant session owns a draft and submission; application fields do not switch that identity.

Entry and authentication

The public application entry point belongs to one published job. Before authentication, Talent portal keeps that job context. Successful email verification continues at the application wizard; a general Talent portal sign-in instead opens Home.

Talent checks that the job is published when the application wizard opens or refreshes. The current final-submit action does not repeat that check for a wizard already open in the browser. A later job closure therefore prevents new entry but is not an atomic cutoff for that in-flight wizard.

The applicant signs in with a six-digit email code. The code is valid for 10 minutes and locks after three incorrect attempts. Requesting a new code replaces the previous code and resets the attempt count.

Draft lifecycle

Talent portal stores at most one in-progress application for an applicant and job. Each wizard step can update the draft. The draft:

• belongs to the verified applicant and selected job;
• can be continued by reopening the job’s application page while the job remains Published;
• does not appear in Home or Applications.

The application requires a CV, first name, last name, and country of residence at final submission. A cover letter, city, phone number, LinkedIn URL, start date, and expected compensation remain optional. When supplied, the LinkedIn value must be one complete URL beginning with http:// or https://.

Submission lifecycle

Selecting Confirm & apply validates the complete draft and creates a submission. The new Hiring pipeline status is New, presented to the applicant as Submitted. Applications are ordered newest first in Talent portal.

Talent associates one application record with each applicant and job. Once submitted, that record is no longer treated as a wizard draft. Repeated submission is not a supported recovery path; open the existing application under Applications instead.

The stored submission and its Submitted UI state are authoritative. A receipt email is sent only when the hiring organization’s application-received template and delivery path permit it. CV and cover-letter parsing is best-effort background enrichment and does not gate the submission or applicant-visible detail.

Ownership after submission

Only the applicant who submitted an application can open it in Talent portal. The detail shows its applicant-facing Status, Job details, Application details, and Documents. An identifier alone does not grant access.

Talent portal currently has no applicant withdrawal control. The hiring organization can update the shared pipeline when an applicant asks to withdraw.

Application-detail status

Hiring status	Applicant-facing status
New	Submitted
Screening	In review
Interview	In process
Offer sent	Offer sent
Accepted	Hired
Rejected	Rejected
Withdrawn	Withdrawn
Talent pool	Kept on file

Any other active pipeline status falls back to In process on the application detail. Cards on Home and Applications translate New to Submitted, but otherwise use the Hiring pipeline label. Private rapid-review decisions in Hiring are not applicant statuses.