Recruitment Onboarding Model
Summary
Onboarding owns the accepted-offer handoff state and references to the Employee result; application behavior performs provisioning before completion.
Audience
Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.
Overview
The aggregate supports Pending, In Progress, Completed, and Cancelled and makes Completed terminal through command handling. It records Employee references, login-pending evidence, completion time, role, and manager metadata.
Application behavior requires an accepted offer, reuses an active onboarding, synchronously provisions Employee, then marks completion, moves Candidate to Joined, raises events, and commits. Employee call success followed by local commit failure is not covered by a distributed transaction; deterministic provisioning supports retry but formal reconciliation is not implemented.
Requires confirmation
Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.
Source References
microservices/src/recruitment-service/Domain/Recruitment/Onboarding.csmicroservices/src/recruitment-service/Application/Commands/OnboardingCommands.csmicroservices/src/recruitment-service/Infrastructure/Gateways.cs
Related Articles
- Recruitment technical documentation
- Recruitment business documentation
- Recruitment known limitations
See Also
Keywords
- Recruitment technical architecture
- Recruitment Service
- Onboarding Model
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly