Recruitment workspace
Rekriva
Bring candidates, reviews and hiring decisions into one clear workspace. Explore it with fictional demo data.
View full imageClarity in a busy hiring process
Hiring teams need to compare candidates, see the next action and retain the context behind a decision. Rekriva brings openings, candidate stages and attributed reviews together in a recruitment workspace. The real application image shows fictional TeamRocket candidates in an isolated demonstration session. It is the current interface, not a reconstruction of the first release, and does not imply a customer relationship or expose real applicant information.
Idea to public showcase in 55 minutes
The original recorded recruitment idea was on 11 November 2026 at 19:02:58.303 UTC. The first verified-live report was at 19:58:17.961 UTC the same day, after public browser journeys, deployed-file checks and persistence across a service restart. The elapsed 55 minutes and 19.658 seconds rounds to 55 minutes. These endpoints come from the original session capture, not the later scope-confirmation timestamp. The private repository corroborates implementation in commit 3e11fad and the subsequent release receipt in 7a9666d. The endpoint is the first recorded verified-live report, not a measurement of the first server response or uninterrupted coding time.
A working release, not just a local scaffold
The first public release record includes eight browser journeys, PostgreSQL persistence, company and department boundaries, review attribution and a saved review surviving a service restart. It also records trusted HTTPS and exact deployed-asset checks. The showcase separated hiring decisions from simulated message delivery. Those checks support a bounded working demonstration, not production readiness for processing real applicant data. Private source and raw conversation history remain private; the public product is available to inspect.
Keep the milestone separate from the roadmap
The first release used synthetic data, with real intake, uploads, recruitment email and staff sign-in unavailable. Development continued after publication, including interface refinement and relational architecture work. Those later capabilities must not be retroactively included in the 55-minute milestone. The Principles of Earned Autonomy workflow connected human direction, decision records and verification, but this delivery example is not a controlled experiment proving that the method caused its speed, nor a promise that a complete production ATS can be delivered in the same time.
