Skip to main content

Recruitment Document UI

Purpose​

Documents embedded resume upload/view/download and offer-letter generation/download behavior. There is no standalone Recruitment document screen.

Resume actions appear in Careers, Candidates, and Interviews; offer-letter actions appear in Offers.

Intended users and preconditions​

Candidates upload resumes publicly; protected Recruitment users view/download resumes and generate/download offer letters. A selected opening/candidate/offer and available Document Service are required for the relevant action.

Main components​

File input, resume reference display, view/download controls, offer PDF action, and page-level errors.

Fields, columns, and sections​

Source-defined file metadata and document references are used. Document contents are not stored in this documentation.

Filters and actions​

Upload resume with an application or candidate, view supported resume content, download resume, and generate/download offer letter.

Validation​

Frontend file handling and service validation apply. Allowed type/size governance beyond source evidence requires confirmation.

UI states​

  • Loading: Document actions use their parent page loading/saving states.
  • Empty: Candidate surfaces explicitly show no-resume states.
  • Success: Browser blob URLs are created for view/download and then revoked.
  • Error: Document failures render page errors; the source also logs a generic resume failure without document content.

Permission behavior​

Public resume upload is unprotected. Protected view/download uses coarse Recruitment route visibility; document-level authorization requires confirmation.

API dependencies​

Uses public/compatibility candidate payloads, native resume download, and Document generation/download APIs.

Document Service owns stored bytes while Recruitment holds references in the native design. Delete, retention, consent, lifecycle synchronization, and reconciliation UI are not implemented.

Screenshot placeholder​

Capture only sanitized, non-production data after product and privacy review. No screenshot is embedded in this Draft page.

Document flow​

Source References​

  • UI/salary-ui/apps/client-hrms-portal/src/pages/CareersPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentCandidatesPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentInterviewsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentOffersPage.tsx
  • microservices/src/recruitment-service/Infrastructure/DocumentServiceClient.cs

Summary​

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

Audience​

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview​

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information​

  • Status: Draft
  • Last reviewed: 2026-07-16
  • Review cycle: Quarterly