Skip to main content

Recruitment Document Reference Storage

Summary

Recruitment persists candidate and offer document references while external Document Service owns content.

Audience

Developers, QA and support engineers, data reviewers, implementation partners, solution architects, and security reviewers.

Overview

CandidateDocumentReference is a Candidate child with a cascade foreign key. It stores document category, file/reference metadata, external document identifier, integrity metadata, actor evidence, and time. Its configured index supports tenant/candidate/document-category access; the snapshot also includes a CandidateId relationship index.

Offer stores a current letter reference and owns OfferLetter history records. OfferLetter has a cascade Offer foreign key and two supporting index shapes in the snapshot.

No document bytes are stored in Recruitment. Delete, orphan reconciliation, retention, and content-governance persistence are not implemented.

Requires confirmation

Production migration governance, rollback ownership, reconciliation, retention, privacy, performance, query optimization, concurrency, and operational ownership require confirmation.

Source References

  • microservices/src/recruitment-service/Infrastructure/RecruitmentDbContext.cs
  • microservices/src/recruitment-service/Domain/Recruitment/Candidate.cs
  • microservices/src/recruitment-service/Domain/Recruitment/Offer.cs
  • microservices/src/recruitment-service/Infrastructure/DocumentServiceClient.cs

See Also

Keywords

  • Recruitment database
  • Document Reference Storage

Revision Information

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