Recruitment business — under NDA
A recruitment website, and the platform running behind it.
- Sector
- Recruitment
- Engagement
- Duration — to confirm
- Scope
- Website and platform, end to end
- Stack
- Node.js · JavaScript · Postgres · AWS
01 — The problem
The public site and the process behind it were separate systems held together by a person copying between them.
Every application arrived twice: once as a form, once as somebody re-entering it. The cost was not the typing. It was that the two records disagreed, and reconciling them was nobody’s job.
Narrative drafted from the brief — replace with the engagement detail
02 — What discovery found
The site was the smaller half of the problem; the workflow behind it was the real one.
Off-the-shelf ATS products all assumed a process this business did not run.
Most of the manual work existed to compensate for one missing status.
03 — What we built
One Node.js system on AWS, front to back: the site people apply through and the platform the team works in.
Public site
Roles, applications and the pages that have to rank — served from the same Postgres records the team works from.
Pipeline
The stages the business actually uses, rather than the stages a generic ATS ships with.
Handover
Documented as it was built, in their accounts and their repository from the first week.
04 — What changed
Qualitative — add figures when you have them
One record per applicant
The site and the pipeline read the same data, so there is nothing to reconcile.
The process is the software
The stages match how the business works, which is why nobody keeps a spreadsheet beside it.
They can change it
Their team owns the code and has shipped to it since. That was the measure of the engagement.
Got something shaped like this? Let's talk.
Discovery is free — you get a written proposal either way