Context
Just Eat Takeaway was running driver onboarding through Fountain, an external ATS that had become too expensive at consumer scale and too rigid for the recruitment workflows operations actually needed. The brief: replace Fountain with a Salesforce-native applicant tracking system. Scale target was 250,000 applicants per year, multi-country deployment, on-call IT for incidents, and a new applicant-facing portal.
The Salesforce org carried tech debt: a 2,000-line Visualforce page (DriverPath) full of cascading formula fields driving the applicant-stage logic, with validation rules in two places that contradicted each other. The refactor had to land without breaking the live driver pipeline.
Our role
Embedded delivery on the recruitment platform team. Custom LWC development for the applicant portal, refactor of the legacy DriverPath, and architectural evaluation of whether Salesforce Experience Cloud or a partner platform was the right host for an applicant portal serving consumer-volume traffic.
What we delivered
- Applicant Portal LWCs:
- Funnel viewer showing application status, with completed and pending tasks per stage
- Onboarding-event scheduler letting applicants pick their onboarding date directly, with capacity limits per event, no double-booking, and cancel/reschedule support
- Job Application overview component on the Lead record
- DriverPath refactor. Audited the 2,000-line page and its formula-field-driven stage logic. Moved business rules from formula fields into validation rules (where they belonged), simplified cascading conditionals, and made the next-step messaging readable for the operations team that had to debug it.
- Email-to-Case configuration linking inbound applicant emails to the right Lead record without changes to page layouts.
- Architecture evaluation: partner platform vs Experience Cloud for the applicant portal at scale. Documented per-login economics, integration depth, and operational implications. Gave the platform team a clear decision path for the 250,000-applicant target without locking them into Salesforce per-user licencing for low-frequency users.
- GIT/SFDX source-tracking workflow introduced alongside the existing Copado pipeline, with sandbox-to-org conventions documented for the team.
- Trigger logic for sequential task completion on Job Application so applicants couldn’t skip ahead in the funnel.
The DriverPath refactor took a Visualforce page that was effectively unreadable and turned it into something the operations team could understand and modify themselves.
Outcome
The Salesforce-native ATS replaced Fountain as the applicant-facing experience. The DriverPath refactor eliminated the formula-vs-validation contradictions and gave operations debug visibility into stage transitions. Scale-side, the partner-platform evaluation gave the team a clear architectural path forward at 250,000 applicants per year.
