B2B SAAS · EDUCATION · 2024—
URM Nexus
Connecting applicants to their next chapter.
01 / Context
The problem
International student recruitment brings together eligibility rules, institution choices, and application documents. Those steps need to work as one coherent process.
02 / Response
The product response
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 recruitment workflow.
03 / Contribution
My role
Technical Co-Founder & Full-Stack Developer, November 2024–present. Architecture, implementation, code reviews, and sprint planning with four junior developers, as documented in the August 2026 CV.
04 / Architecture
How the pieces connect
- 01Next.js App Router surfaces
- 02Server actions and route handlers
- 03Supabase auth, Postgres and storage
- 04Stripe billing
05 / Execution
The engineering challenge
Bringing eligibility decisions, document handling and matching into a consistent workflow while migrating an existing WordPress platform onto a typed application stack.
06 / Result
Outcomes & perspective
The CV documents the platform and development responsibilities. No independently verified adoption, revenue, or performance metrics are available.
07 / Reflection
A lesson from the work
A migration is also a product-design problem: the application process must stay understandable as its underlying system changes.
08 / Evidence
Evidence & scope
Sources: August 2026 professional CV, and the private repository’s README and package manifest inspected September 2026. Architecture is a high-level summary; private implementation details are not published.