Architecting a multi-portal recruitment platform
Technical leadership for connected admin, recruiter and candidate products backed by secure APIs and automated workflows.
- My role
- Software Engineer & Technical Lead
- Period
- 2025–Present
PROJECT OVERVIEW
Juvakel is a recruitment ecosystem with distinct experiences for administrators, recruiters and candidates, supported by shared services and operational tooling.
The problem
Recruitment workflows cross multiple roles and sensitive data boundaries. Separate portals still need consistent identity, permissions, job state, notifications and analytics without duplicating business rules.
My responsibility
I lead technical direction, architecture and delivery across web, mobile, APIs and deployment workflows while collaborating with product stakeholders.
REAL-WORLD CONSTRAINTS
SOLUTION & CONTRIBUTION
Shared backend services enforce authentication, authorisation and workflow rules, while each portal is shaped around its users. Automation and deployment practices reduce operational friction as the platform evolves.
- 01Architected admin, recruiter and candidate portal boundaries.
- 02Developed secure APIs and role-based access controls.
- 03Implemented candidate screening and job-management workflows.
- 04Built notification and analytics capabilities.
- 05Introduced delivery automation and DevOps practices.
SANITISED ARCHITECTURE
Certain implementation details and screens are intentionally anonymised to protect organisational and user data.
Engineering challenge
The central challenge is keeping permission checks and workflow rules consistent across different user experiences. Moving those rules behind shared APIs reduces duplication and makes role boundaries testable.
Observable outcomes
- A shared foundation for three role-specific products
- Centralised security and workflow rules
- Automated operational and notification paths
- Deployment practices designed for product growth
Technology used
Next case study
Fundani School OS