URM Nexus
Connecting applicants to their next chapter.
- Role
- Architecture and team lead
- Timeline
- 2024 to 2026
- Type
- Education and hiring platform
- Stack
- Next.js, React, TypeScript, Supabase, Stripe
The problem
International recruitment brings together eligibility rules, institution choices and application documents. Those steps need to work as one process, for applicants and for partner institutions.
What we built
A multi-surface platform: public discovery and eligibility journeys, a partner workspace, internal admin operations, account lifecycle and billing. AI-assisted eligibility screening and applicant-institution matching sit inside the same workflow, with a GDPR-compliant data pipeline for compliance and reporting.
My role
As technical co-founder of URM ENROLL, I set the architecture for Nexus and lead the small team that builds it, through code review and sprint planning.
How it fits together
- Next.js App Router surfaces
- Server actions and route handlers
- Supabase auth, Postgres and storage
- Stripe billing
The hard part
Bringing eligibility decisions, document handling and matching into one consistent workflow on a typed stack, while keeping personal data handling GDPR-compliant, and doing it through a team rather than alone.
Where it stands
Built by the team on the architecture I set and the reviews I run. No adoption, revenue or performance figures are published here.
What I took from it
Leading a team moves the work from writing the code to making the next decision obvious: clear boundaries, clear reviews, and a codebase a new developer can find their way through.
Sources and scope
Sources: my CV, and the repository's README and package manifest, inspected September 2026. Architecture is a high-level summary; private implementation details are not published.
