Recruitment Offer Model

Summary

Offer owns status, a compensation value object, public token, document references, revision history, approval decisions, and candidate-response evidence.

Audience

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

Overview

Aggregate methods support revision, internal approval/rejection, acceptance, decline, rejection, withdrawal, and lifecycle event creation. Application services load Candidate/Opening state, invoke Document Service, enforce command-specific guards, update Candidate stage, and create Onboarding.

Offer rules are distributed across aggregate and command methods rather than one complete transition table. Revision resets Draft and regenerates a letter. No Workflow integration, approval threshold, separation-of-duties rule, token expiry, or distributed recovery is implemented for offers. Sensitive compensation formulas and values are intentionally omitted.

Requires confirmation

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

Source References

• microservices/src/recruitment-service/Domain/Recruitment/Offer.cs
• microservices/src/recruitment-service/Application/Commands/OfferCommands.cs
• microservices/src/recruitment-service/Domain/Common/ValueObjects.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
• Offer Model

Revision Information

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