Skip to main content

Recruitment Document Integration Events

Summary​

Candidate documents and offer letters use synchronous Document Service operations; Recruitment has no Document event subscription.

Audience​

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

Overview​

Recruitment owns references while Document Service owns content. Candidate upload and offer creation/revision can call Document Service before local Recruitment save. Failure and local-commit boundaries are therefore separate.

The inspected Document generation path can produce a generic document contract, and Notification recognizes that generic type. Recruitment's blob-storage calls are not shown to use that generation path, and Recruitment does not consume the contract. No Recruitment delete/lifecycle document event or reference reconciliation implementation was found.

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/Application/Commands/CandidateCommands.cs
  • microservices/src/recruitment-service/Application/Commands/OfferCommands.cs
  • microservices/src/recruitment-service/Infrastructure/DocumentServiceClient.cs
  • microservices/src/recruitment-service/Infrastructure/Gateways.cs
  • microservices/src/document-service/Application/Generation/DocumentGenerationService.cs

See Also​

Keywords​

  • Recruitment events
  • Document Integration Events

Revision Information​

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