Skip to main content

Recruitment Service Responsibilities

Summary​

The service owns Recruitment state, lifecycle execution, tenant-scoped reads, audit/timeline evidence, report aggregates, compatibility translation, and integration-event production.

Audience​

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

Overview​

Owned responsibilities​

  • Requisitions, openings, candidates/applications, interviews/feedback, offers, and onboarding aggregates.
  • Domain and application validation for supported commands.
  • Tenant-scoped persistence, audit, timeline, and outbox records.
  • Native/public queries and operational reporting.
  • Compatibility translation for the existing portal contract.

Delegated responsibilities​

  • Document content and offer-letter storage belong to Document Service.
  • Requisition approval tasks may belong to Workflow Service.
  • Employee master creation belongs to Employee Service.
  • Authentication originates outside Recruitment; authorization remains incomplete.
  • Notification delivery, Platform entitlement enforcement, and Payroll projections are not Recruitment implementations.

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/Domain/Recruitment
  • microservices/src/recruitment-service/Application/Commands
  • microservices/src/recruitment-service/Application/Queries/RecruitmentQueries.cs

See Also​

Keywords​

  • Recruitment technical architecture
  • Recruitment Service
  • Responsibilities

Revision Information​

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