Skip to main content

Interview Scheduling UI

Purpose

Schedules interviews and manages their current state in the protected workspace.

Talent → Interviews; protected interview route.

Intended users and preconditions

Recruiter/HR workspace users; interviewer-specific protected workspace scope is not implemented. Workspace must return openings and candidates. A job opening, candidate, interviewer name, and schedule are required.

Main components

Metrics, scheduling form, candidate search, filters, calendar-like record cards, details panel, status controls, and resume actions.

Fields, columns, and sections

The form includes opening, candidate, round, type, interviewer contact, schedule, mode, meeting/location information, and notes.

Filters and actions

Schedule, search/filter, open details, update status, access resume, and proceed to feedback.

Validation

Source checks require opening, candidate, interviewer name, and date/time. Backend state rules remain authoritative.

UI states

  • Loading: An explicit loading state is shown.
  • Empty: An explicit no-interviews state is shown.
  • Success: Successful scheduling/status changes reload workspace data.
  • Error: Load, schedule, status, and resume failures render page errors.

Permission behavior

Only coarse Recruitment route visibility is checked; interviewer ownership and assignment-based authorization require confirmation.

API dependencies

Uses compatibility workspace, interview-create, interview-status, and native resume-download endpoints.

Statuses are Scheduled, Completed, Cancelled, and Feedback Submitted. No external calendar provider integration is evidenced.

Screenshot placeholder

Capture only sanitized, non-production data after product and privacy review. No screenshot is embedded in this Draft page.

Interview flow

Source References

  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/RecruitmentInterviewsPage.tsx
  • UI/salary-ui/apps/client-hrms-portal/src/pages/hr/HrSuitePage.tsx
  • microservices/src/recruitment-service/Application/Commands/InterviewCommands.cs

Summary

This Draft page summarizes source-backed Recruitment behavior and explicitly marks incomplete governance or implementation.

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.

See Also

Keywords

  • Recruitment
  • Hiring lifecycle
  • Draft documentation

Revision Information

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