Jenny Mcrich Recruitment
Keep the hiring decision in context.
A recruitment workspace for Jenny Mcrich: candidate records, hiring stages, interviews, and job matching in one interface.
- Year
- 2026
- Role
- Design + implementation
- Client
- Jenny Mcrich Recruitment
- Surfaces
- Recruitment workspace
- Stack
- Next.js, React, TypeScript, Tailwind CSS, Recharts, dnd-kit
Recruiters need to see a candidate’s experience, the role’s requirements, and the next action without rebuilding the story across separate tools. JennyATS brings the dashboard, candidate workspace, job records, and hiring pipeline into one application.
I designed and implemented a recruitment workspace with named stages, candidate detail pages, interview scheduling, and matching logic. The current demo data layer records stage changes and checks scheduling conflicts, so the interaction can be explored with consistent sample records.
These captures come from the implemented app using its fictional in-memory demo data. Supabase is a planned production data-layer replacement, not a live backend demonstrated here. The case study shows the interface and demo behavior without claiming hiring outcomes or production adoption.
Recruitment workspace
Recruiter dashboard
01 / 03
Start with the next action
Use the overview to bring interviews, stalled applications, and pipeline context into the recruiter’s working day.
Make stages explicit
Carry candidates through Applied, Screening, Interview, Offer, and Hired, with Rejected handled as a separate outcome.
Keep context together
Connect candidate records, job requirements, scheduling, and history so a move through the pipeline is an informed action.
Build an honest demo boundary
Use the app’s fictional records and implemented in-memory behavior. Keep the future database integration distinct from what the demo currently proves.
Next
