A staffing business lives in its applicant tracking system. We wanted one that matched how we actually hire, including the onboarding paperwork that generic tools leave to spreadsheets, so we built it.
What it does
- A public careers site with job pages and a short application.
- A recruiter workspace: pipeline, candidate records, interviews, offers and email.
- A candidate portal where applicants track their application and upload documents.
- Onboarding documents with HR-only files, so recruiters don’t see what they don’t need after a hire.
- An onboarding autopilot (see the separate case study).
Security we designed in
- Role-based access with a permission catalog, and two-step sign-in required for admin and HR roles in production.
- Uploaded files are scanned for malware before anyone can open them.
- Security changes, such as a password reset or a new two-step device, notify the account owner, and refused attempts are audited.
- Contact details are hidden from roles that don’t need them.
How we test it
Every change runs the automated test suite against both PostgreSQL 16 and an in-process database. Browser suites then sign in as every role and click through every page on a desktop and a phone-sized screen, with accessibility checks on each one.
What we’d tell a client
Building your own system is rarely the right call. It was for us because recruiting is our core operation and the compliance details are where off-the-shelf tools stop. If that’s true for you too, we can help; if it isn’t, we’ll tell you which product to buy.
- 223automated tests, run on PostgreSQL 16 and in-process
- 35permissions in the role catalogue
- 37versioned database migrations
Figures on this page are counted from our own code and test suite each time the site is built.