Recruitment operations platform

Overview

Agency recruiters juggle several open roles at once, and each role lives in a different place: a spreadsheet of candidates, an inbox of replies, a calendar of interviews. This concept pulls those threads into one workspace built around the pipeline, so the question "where does this role stand?" has one answer.

The problem it explores

Recruiting teams often track candidates across spreadsheets, inboxes and disconnected tools, with no single view of the pipeline.

Design decisions

1. The pipeline is the home screen

   Open roles, stage counts and upcoming interviews sit on the first screen, because recruiters start their day by asking what needs attention, not by searching.

2. AI suggests, people decide

   Candidate matching shows why a candidate fits (skills, experience) so a recruiter can confirm or dismiss it in seconds. The model ranks; it never moves a candidate on its own.

3. Roles shape what you see

   Recruiters, coordinators and account managers get different default views of the same data, using role-based access from the first release.

What the concept includes

• Hiring pipeline funnel from sourced to hired
• AI candidate match with skills breakdown
• Interview scheduling and upcoming-interviews list
• Job openings with candidate counts per role
• Activity feed and insights panel

Under the hood

A Next.js front end talks to a Django REST API backed by PostgreSQL. Search and matching run as background jobs so the interface stays responsive, and the whole stack ships in Docker for repeatable environments.