Recruitment Notifications

Summary

Recruitment raises lifecycle events that could drive notifications, but no Recruitment event consumption is confirmed in Notification Service.

Audience

Recruitment operations, hiring stakeholders, product, engineering, QA, support, and architecture teams. Candidate-facing behavior is identified explicitly.

Overview

Recruitment raises lifecycle events that could drive notifications, but no Recruitment event consumption is confirmed in Notification Service.

Confirmed event opportunities

Application receipt, interview scheduling, offer creation/approval/acceptance/rejection/decline/withdrawal, onboarding completion, joining, and joining reminders have event contracts or domain events.

Maturity

• Transactional outbox publication is implemented.
• Event publication does not prove consumption or candidate delivery.
• Notification Service contains no confirmed Recruitment resolver/consumer.
• Templates, recipients, channels, consent, retry policy, and delivery tracking are Not implemented for Recruitment in the inspected source.

Do not promise that candidates, interviewers, recruiters, or managers receive a message.

Requires confirmation

Formal ownership, production policy, authorization parity, and approved operating procedures require confirmation.

Source References

• microservices/src/recruitment-service/Domain/Recruitment/RecruitmentDomainEvents.cs
• microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
• microservices/src/notification-service/Application/EventNotificationResolver.cs

Related Articles

• Recruitment module
• Recruitment business documentation
• Recruitment limitations

See Also

• Recruitment module overview
• Recruitment business rules

Keywords

• Recruitment
• Hiring lifecycle
• Notifications

Revision Information

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