Skip to main content

Recruitment Technical Known Limitations

Summary​

Confirmed technical gaps across architecture, access, integrations, operations, performance, testing, and governance.

Audience​

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

Overview​

Security and tenancy​

  • Native authorization policies and endpoint enforcement are not implemented.
  • UI/gateway/native/compatibility authorization parity is unresolved.
  • Ownership, compensation/document access, public-token lifecycle, and callback authentication need governance.

Consistency and integrations​

  • Workflow ownership covers requisitions only and is Transitional.
  • Employee login provisioning and manager identifier mapping are not implemented.
  • Employee/Document calls do not share a distributed transaction with Recruitment.
  • Notification consumption is not implemented; event publication alone is insufficient.
  • Platform entitlement enforcement and Payroll interaction are not implemented.

Runtime and assurance​

  • Health is shallow; readiness/liveness separation and dependency probes are absent.
  • No Recruitment metrics, caching, concurrency tokens, or governed performance limits.
  • Reports use current-state aggregation without an analytics projection.
  • No formal Recruitment test project, backfill, parity comparator, cutover helper, or runbook.
  • Privacy, retention, redaction, reconciliation, archival, and token governance require confirmation.

Requires confirmation​

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

Source References​

  • microservices/src/recruitment-service/Program.cs
  • microservices/src/recruitment-service/Api/Policies.cs
  • microservices/src/recruitment-service/Application/Commands
  • microservices/src/recruitment-service/Infrastructure
  • microservices/src/notification-service/Application/EventNotificationResolver.cs
  • microservices/scripts

See Also​

Keywords​

  • Recruitment technical architecture
  • Recruitment Service
  • Known Limitations

Revision Information​

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