Skip to main content

Recruitment Onboarding Handoff

Summary

Only an Accepted offer can move to onboarding. Completing onboarding synchronously provisions or finds an Employee record before Recruitment records completion.

Audience

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

Overview

Only an Accepted offer can move to onboarding. Completing onboarding synchronously provisions or finds an Employee record before Recruitment records completion.

Employee handoff

An existing non-cancelled onboarding is reused for the same offer. Employee creation is designed to be retry-safe through a deterministic employee code and lookup on conflict. Completion emits onboarding/joined evidence only after Employee provisioning succeeds. Login/user creation is Not implemented, so login remains pending. Manager identifier mapping is unresolved.

Requires confirmation

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

Source References

  • microservices/src/recruitment-service/Domain/Recruitment/Onboarding.cs
  • microservices/src/recruitment-service/Application/Commands/OnboardingCommands.cs
  • microservices/src/recruitment-service/Infrastructure/EmployeeServiceClient.cs
  • microservices/src/recruitment-service/Infrastructure/Gateways.cs

See Also

Keywords

  • Recruitment
  • Hiring lifecycle
  • Onboarding Handoff

Revision Information

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