Recruitment Module Overview

Summary

The module owns hiring records and lifecycle evidence while delegating documents, requisition workflow, and final Employee creation to other bounded contexts.

Audience

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

Overview

The module owns hiring records and lifecycle evidence while delegating documents, requisition workflow, and final Employee creation to other bounded contexts.

Scope

Recruitment owns requisitions, openings, candidates and applications, interviews and feedback, offers and revisions, onboarding state, audit/timeline evidence, reports, and lifecycle events.

It does not own Employee master data, identity/login creation, document content, Workflow tasks, Notification delivery, Payroll, or platform entitlements.

Capability classification

Capability	Maturity
Core hiring lifecycle	Partial
Portal and compatibility contract	Transitional
Workflow requisition approval	Transitional
Employee handoff	Partial
Document integration	Transitional
Native authorization policy	Foundation
Notification consumption	Not implemented
Payroll interaction	Not implemented

Requires confirmation

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

Source References

• microservices/src/recruitment-service/Domain/Common/Enums.cs
• microservices/src/recruitment-service/Application/Commands
• UI/salary-ui/apps/client-hrms-portal/src/App.tsx

Related Articles

• Recruitment module
• Recruitment business documentation
• Recruitment limitations

See Also

• Recruitment module overview
• Recruitment business rules

Keywords

• Recruitment
• Hiring lifecycle
• Overview

Revision Information

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