Recruitment Candidate and Application Events

Summary

Candidate application raises one mapped event; candidate creation without application and later stage changes do not.

Audience

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

Overview

CandidateAppliedDomainEvent is invoked after candidate/application creation and maps to CandidateAppliedEvent. Duplicate application detection happens before creation. The mapped contract has no confirmed consumer.

Candidate stage changes, selection, rejection, notes, document-reference changes, and administrative creation have no dedicated domain/integration event. Sensitive candidate information carried by the contract is not reproduced here.

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/Candidate.cs
• microservices/src/recruitment-service/Application/Commands/CandidateCommands.cs
• microservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.cs
• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• microservices/src/contracts/Events/CandidateAppliedEvent.cs

Related Articles

• Recruitment events documentation
• Event catalog

See Also

• Recruitment technical documentation
• Recruitment API documentation

Keywords

• Recruitment events
• Candidate and Application Events

Revision Information

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