Recruitment Operations Documentation

Summary

Recruitment Service owns the hiring domain, persistence, compatibility/public APIs, audit/timeline records, and transactional outbox. Runtime dependencies include its database, gateway/authentication context, Workflow when enabled, Employee Service during completion, Document Service for content, and messaging for outbound publication.

Documentation map

• Operational overview, configuration, and startup
• Health and observability and smoke testing
• Workflow, Employee, Document, and Notification
• Outbox, public tokens, and consistency
• Compatibility/cutover, support, and checklist

Safety boundary

These pages do not provide secrets, values, internal addresses, broker topology, database edits, replay commands, or destructive recovery steps. Production ownership, runbooks, service objectives, alerts, retry governance, and approvals require confirmation.

Source References

• microservices/src/recruitment-service/Program.cs
• microservices/src/recruitment-service/Api/RecruitmentEndpoints.cs
• microservices/src/recruitment-service/Api/RecruitmentCompatEndpoints.cs
• microservices/src/recruitment-service/Messaging/OutboxRelayHostedService.cs
• microservices/scripts/smoke-recruitment.ps1

Audience

Recruitment stakeholders, product, engineering, QA, support, operations, architecture, security, and implementation partners as applicable to this page.

Overview

Use the source-backed sections above as the authoritative scope. Unsupported behavior remains Requires confirmation or Not implemented.

Related Articles

• Recruitment module
• Recruitment technical documentation

See Also

• Recruitment API
• Recruitment known limitations

Keywords

• Recruitment
• Hiring lifecycle
• Draft documentation

Revision Information

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