Skip to main content

Recruitment Workflows

Summary​

Workflow Service integration is limited to feature-controlled job-requisition approval; interview, candidate, offer, and onboarding actions are not Workflow-managed in source.

Audience​

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

Overview​

Workflow Service integration is limited to feature-controlled job-requisition approval; interview, candidate, offer, and onboarding actions are not Workflow-managed in source.

Workflow-managed requisition​

  • Creation can request an external approval workflow.
  • A started instance is linked to the Submitted requisition.
  • Direct approve/reject is blocked while that workflow owns the pending decision.
  • A terminal callback applies approval or rejection.
  • Duplicate callbacks against a terminal requisition are acknowledged without creating another opening.
  • Optional live-state comparison can reject a mismatched callback.

Failure handling differs by environment and remains Transitional. Workflow keys, routing values, and internal addresses are intentionally excluded.

Requires confirmation​

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

Source References​

  • microservices/src/recruitment-service/Application/WorkflowIntegration.cs
  • microservices/src/recruitment-service/Application/Commands/RequisitionCommands.cs
  • microservices/src/recruitment-service/Infrastructure/WorkflowServiceClient.cs

See Also​

Keywords​

  • Recruitment
  • Hiring lifecycle
  • Workflows

Revision Information​

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