Design around reviewer context
The reviewer surface uses tabs and browser-like multitasking to keep several application tasks within one workspace.
1,000+ applicants · 50+ interviewers
A recruitment platform built with a 50+ person team to manage application review, interviews, and administration for 1,000+ applicants.
Context
The challenge
The platform had to keep application review, interviews, and administration workable for more than 1,000 applicants and more than 50 interviewers. That meant the data path and the reviewer interface both had to support a high-volume recruitment workflow.
Krishang's role
System
Architecture
The applications portal collects and organizes the candidate workflow for more than 1,000 applicants.
A React and Tailwind workspace recreates browser-style tabs and multitasking for more than 50 interviewers.
A Next.js 16 App Router dashboard uses Server Actions and Prisma for administrative workflows.
CockroachDB stores application data while Redis supports the optimized query path.
PostHog telemetry records product usage so the team can monitor workflows.
Choices
Engineering decisions
The reviewer surface uses tabs and browser-like multitasking to keep several application tasks within one workspace.
Schema work and Redis caching targeted the query path used across the recruitment workflow.
The admin dashboard uses App Router, Server Actions, and Prisma rather than introducing a separate administration application.
Result
Recorded outcomes
Working stack
Evidence boundary
The scope and measurements here are limited to the project record in Krishang's résumé; no public OCS repository is linked.