Hiring app for a growing company with roles, candidates, stages, interviews, offer approvals, and a dashboard
recruiting-pipeline · 3600 s per turn · source
The ask
We're a software company growing fast, and I need to run hiring in one place instead of our old applicant tracker: roles, candidates, and each candidate's path from applied through phone screen, interview, and offer to hired. Our open and past roles and the candidate export are attached; people show up more than once in that export, and I want each person once with every role they applied for. Interviews get scheduled in the app, and no interviewer should ever be booked twice at the same time. Every offer needs my approval before it goes out, and nobody can offer above the salary range on the role. I want team logins with different access: hiring managers see only candidates for their own roles, our CEO can look at everything without changing anything, and I want a dashboard with our pipeline and how long it takes us to hire. Give me an admin login and one for Ken Okafor, who hires for Engineering.
Seed files the agent must import: roles.csv</code>, <code>candidates.csv. The agent must leave a RESULT.json with a reachable URL, an admin login, and the named restricted login.
Acceptance checklist
26 binary items. The first 14 are the enterprise baseline shared by every build task (delivery, invitations, roles, server-side authorization, scoped live dashboard, exact lists and exports, audit metadata, validation, persistence); the rest are application-specific. Core items, which together define "first usable": 1, 3, 5, 6, 8, 14, 16, 22, 24.
| Tag | Items |
|---|---|
| Exact | 8 |
| Rule | 5 |
| Automation | 2 |
| Dashboard | 2 |
| Delivery | 2 |
| Permission | 2 |
| Sharing | 2 |
| API | 1 |
| Audit | 1 |
| Persistence | 1 |
The full checklist with per-item "how to check" instructions and expected figures is in checklist.md. Testers see it; the agent never does.
Change requests
Each change is a new one-shot turn on the carried-forward workspace. Only the owner's text below is sent; the tester items are withheld. After each change the full checklist is rerun, so regressions count.
Change 1 · 3 new checklist items
I want a pipeline report: for each role, how many candidates are at each stage. And put our offer acceptance rate on the dashboard.
Change 2 · 3 new checklist items
When a role is filled, everyone still in process for it should be rejected automatically with the reason "Position filled", but if they've applied for another role, that application stays as it is.
Change 3 · 3 new checklist items
Add a Reference check stage between Interview and Offer. And interviewers need their own login: they see only the candidates they're interviewing, add their scorecard, and never see any salary numbers.
No published score. Build runs need a human acceptance pass on a live URL, and no arm has completed one for the full set. Automated probes generate a tester sheet; they do not substitute for it. Results will be published as a separately labeled release when an arm completes.