Skip to main content

Recruitment Known Limitations

Summary​

Confirmed gaps and maturity constraints for Recruitment Epic 10.1.

Audience​

Recruitment operations, hiring stakeholders, product, engineering, QA, support, and architecture teams. Candidate-facing behavior is identified explicitly.

Overview​

Confirmed gaps and maturity constraints for Recruitment Epic 10.1.

Reference Content​

The following catalog consolidates the confirmed source evidence and its maturity.

Access and governance​

  • Native Recruitment permission policies are not implemented.
  • UI role visibility is not proof of API authority.
  • Candidate/recruiter/job ownership and hiring-manager scope require confirmation.
  • Compensation and document-access governance require confirmation.

Lifecycle​

  • Candidate, interview, opening, and offer general status commands do not form strict transition engines.
  • Offer approval is not Workflow-managed and separation of duties is not enforced.
  • Candidate acceptance moves the candidate to Selected; Joined occurs only after onboarding completion.
  • No candidate merge, global deduplication, withdrawal, deletion, archival, talent-pool, or vacancy-consumption engine is confirmed.

Integrations​

  • Notification consumption is not implemented despite emitted events.
  • Payroll integration is not implemented.
  • Employee login creation and reporting-manager mapping are unresolved.
  • Gateway and compatibility coexistence is Transitional.
  • Platform opening-limit and offer-letter entitlement enforcement is not confirmed.
  • Document/Employee development fallbacks are not production behavior.

Reporting and assurance​

  • Reports are operational aggregates without governed definitions or historical snapshots.
  • Formal Recruitment automated test-project coverage requires confirmation.
  • Retention, privacy, consent, token expiry/revocation, and audit access governance require confirmation.

Requires confirmation​

Formal ownership, production policy, authorization parity, and approved operating procedures require confirmation.

Source References​

  • microservices/src/recruitment-service/Domain/Common/Enums.cs
  • microservices/src/recruitment-service/Domain/Recruitment
  • microservices/src/recruitment-service/Application/Commands
  • microservices/src/recruitment-service/Api/Policies.cs
  • microservices/src/notification-service/Application/EventNotificationResolver.cs

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Known Limitations

Revision Information​

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