Skip to main content

Recruitment Terminology

TermSource-backed meaning
RequisitionApproval request for hiring demand; native workflow may be local or Workflow-managed.
Job opening / positionRecruitable role created or managed after approval or through compatibility commands.
CandidatePerson represented in the hiring pipeline.
ApplicationCandidate-to-opening association with duplicate controls.
StageCandidate pipeline state from Applied through terminal Joined/Rejected.
InterviewScheduled assessment with lifecycle state and feedback records.
FeedbackInterview evaluation containing recommendation/result and sensitive notes.
CTC approvalCandidate-level compensation approval state in compatibility behavior.
OfferHiring proposal with lifecycle, approval/revision records, public response, and document reference.
OnboardingPost-acceptance handoff that can synchronously create an Employee.
Compatibility surfaceMonolith-shaped API/UI contract mapped over Recruitment persistence.
Public tokenOpaque route lookup used for feedback or offer response; governance requires confirmation.
OutboxLocally persisted outbound event message awaiting or recording publication.

Source References​

  • microservices/src/recruitment-service/Domain/Common/Enums.cs
  • microservices/src/recruitment-service/Domain/Recruitment
  • microservices/src/recruitment-service/Application/Compatibility/CompatLabels.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