Skip to main content

Recruitment Lifecycle

Summary

The confirmed lifecycle begins with either a requisition or direct opening and ends when onboarding completes or a branch is rejected, declined, withdrawn, cancelled, or closed.

Audience

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

Overview

The confirmed lifecycle begins with either a requisition or direct opening and ends when onboarding completes or a branch is rejected, declined, withdrawn, cancelled, or closed.

Confirmed end-to-end flow

Direct opening creation bypasses requisition approval. Candidate stage changes also have a general command that does not enforce a complete transition graph, so the diagram describes orchestrated behavior rather than a universal state-machine guarantee.

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
  • microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs

See Also

Keywords

  • Recruitment
  • Hiring lifecycle
  • Lifecycle

Revision Information

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