Skip to main content

Recruitment Events

Summary​

Recruitment defines 12 domain-event types and maps 11 to shared version-1 contracts. OfferWithdrawn is the sole unmapped event.

Audience​

Recruitment developers, integration engineers, QA, support, and architects.

Reference Content​

CandidateOnboarded and CandidateJoined are raised after synchronous Employee provisioning succeeds. Onboarding create/start/status/cancel have no dedicated events. JoiningReminder is conditional on accepted-offer joining information.

The context maps events before save, stages contracts in its outbox, and clears aggregate event queues. A registered hosted relay later publishes pending/failed entries.

No inbound subscription is registered. A ProcessedIntegrationEvent model exists as Foundation, not proof of a consumer.

No requested-scope consumer was found for any Recruitment contract, including CandidateOnboarded, CandidateJoined and OfferAccepted.

Requires confirmation​

Unless explicitly confirmed above, live delivery, consumer deployment, replay, reconciliation, retention, contract governance, monitoring and production ownership require confirmation.

Source References​

  • microservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.cs
  • microservices/src/recruitment-service/Domain/Recruitment/Offer.cs
  • microservices/src/recruitment-service/Domain/Recruitment/Onboarding.cs
  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
  • microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs

See Also​

Keywords​

  • Onboarding events
  • Offboarding events
  • Integration contracts

Revision Information​

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