Recruitment Document Integration

Summary

Recruitment uses a typed HTTP client/gateway to store candidate documents and generated offer letters while persisting only document references.

Audience

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

Overview

Recruitment does not own document bytes. A resume filename without bytes may produce a reference-only record. Offer creation/revision couples local success to letter generation. Cross-service rollback, orphan cleanup, retention, access control, malware scanning, and reconciliation are not implemented in Recruitment.

Requires confirmation

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

Source References

• microservices/src/recruitment-service/Application/Common/Gateways.cs
• microservices/src/recruitment-service/Infrastructure/DocumentServiceClient.cs
• microservices/src/recruitment-service/Infrastructure/Gateways.cs
• microservices/src/recruitment-service/Application/Commands/CandidateCommands.cs
• microservices/src/recruitment-service/Application/Commands/OfferCommands.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
• Document Integration

Revision Information

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