Recruitment Requisition Model

Summary

JobRequisition owns Submitted, Approved, and Rejected state, decision evidence, an optional Workflow instance link, and the created opening reference.

Audience

Backend and frontend engineers, architects, QA, support, security reviewers, and operators responsible for Recruitment.

Overview

The aggregate validates title, monetary range ordering, workflow attachment while Submitted, approval/rejection terminal constraints, and rejection reason. The application layer supplies tenant/requester context, starts optional Workflow approval, creates the JobOpening on approval, and writes audit/timeline evidence.

Workflow callbacks are application behavior, not aggregate behavior. Duplicate terminal callbacks are handled before aggregate mutation. There is no requisition revision, cancellation, reopen, or deletion behavior in the native command set.

Requires confirmation

Production ownership, authorization policy, operational thresholds, and future design decisions require confirmation.

Source References

• microservices/src/recruitment-service/Domain/Recruitment/JobRequisition.cs
• microservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs
• microservices/src/recruitment-service/Application/WorkflowIntegration.cs

Related Articles

• Recruitment technical documentation
• Recruitment business documentation
• Recruitment known limitations

See Also

• Recruitment module
• Recruitment API foundation

Keywords

• Recruitment technical architecture
• Recruitment Service
• Requisition Model

Revision Information

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