Skip to main content

Recruitment Business Overview

Summary​

Recruitment covers requisitions, openings, applications, candidate progression, interviews, offers, and the handoff that creates an Employee record.

Audience​

Recruitment operations, hiring stakeholders, product, engineering, QA, support, and architecture teams. Candidate-facing behavior is identified explicitly.

Overview​

Recruitment covers requisitions, openings, applications, candidate progression, interviews, offers, and the handoff that creates an Employee record.

Capability map​

The native service owns tenant-scoped hiring records. A public careers flow discovers open positions and creates applications. Compatibility routes preserve the existing portal contract while gateway ownership remains Transitional.

Confirmed outcomes​

  • Approved requisitions create an open job opening.
  • Applications create a candidate and link that candidate to an opening.
  • Interview feedback can move the candidate to Selected, Rejected, or Interviewed.
  • Offer acceptance permits onboarding; onboarding completion provisions an Employee record.
  • Audit and timeline evidence is written for confirmed commands.

Not implemented​

Notification consumption, Recruitment-to-Payroll projection, native permission policies, and login creation during onboarding are not implemented.

Requires confirmation​

Formal ownership, production policy, authorization parity, and approved operating procedures require confirmation.

Source References​

  • microservices/src/recruitment-service/Domain/Common/Enums.cs
  • microservices/src/recruitment-service/Domain/Recruitment
  • microservices/src/recruitment-service/Application/Commands

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Business Overview

Revision Information​

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