Recruitment Onboarding and Employee Provisioning Events

Summary

Onboarding completion synchronously provisions Employee, then raises CandidateOnboarded and CandidateJoined before the local save.

Audience

Developers, QA and support engineers, integration reviewers, implementation partners, solution architects, and security reviewers.

Overview

Employee provisioning is HTTP-driven, not event-driven. A deterministic employee code supports retry lookup. Completion persists Employee references and emits two mapped contracts only after provisioning returns successfully.

Onboarding creation/start/status/cancellation have no dedicated events. Login provisioning and manager mapping are absent. Employee success followed by local failure has no reconciliation workflow or distributed transaction.

Requires confirmation

Consumer ownership, tenant-envelope policy, correlation/causation policy, retry limits, replay, ordering, contract governance, reconciliation, monitoring, and production support 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
• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• microservices/src/contracts/Events/CandidateOnboardedEvent.cs
• microservices/src/contracts/Events/RecruitmentLifecycleEvents.cs

Related Articles

• Recruitment events documentation
• Event catalog

See Also

• Recruitment technical documentation
• Recruitment API documentation

Keywords

• Recruitment events
• Onboarding and Employee Provisioning

Revision Information

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