For Raya HR & RIS

One clear journey.
Two systems,
no confusion.

This is the operating model behind the careers experience we are building: our custom frontend makes Raya’s opportunities easier to discover, while Oracle Fusion Recruitment keeps ownership of vacancies, applications, CVs and HR workflows.

What Raya HR keeps doing normally

HR teams continue to create, update, publish and close requisitions in Oracle. The public careers experience reflects those approved roles after the live integration is enabled. No second vacancy database is introduced here.

01 / RAYA HR

Manage the source.

Create and maintain vacancies, status, job details and recruitment workflow inside Oracle Fusion Recruitment as usual.

02 / OUR FRONTEND

Make it easier to find.

Present the approved public job information in a bilingual, searchable and brand-led Raya experience across companies and sectors.

03 / CANDIDATE

Apply in Oracle.

Let candidates open the role, continue securely into Oracle, submit their application and CV, then follow the Oracle journey.

What is connected, and what is not

The public experience
stays simple.

Connected in this projectPublic job discovery, bilingual content presentation, role details, search, filtering, canonical Oracle handoff, source alignment and responsive experience design.
Owned by OracleCandidate sign-in, employee identity, application submission, CV storage, applicant status, recruiter workflows, requisition management and HR dashboards.
Not introduced by usNo Oracle customization, no duplicate candidate database, no local CV uploads, no fake application records and no parallel HR administration console.
Needs RIS confirmationSandbox access, supported read-only route or API, field mapping, CORS/network requirements, canonical apply URL and any approved security boundary.