Recruiting: jobs not visible on the career site

# Fix of the Day #7: Recruiting: jobs not visible on the career site

Part of my Oracle Fusion HCM Fix of the Day series: real issues from implementations and a Redwood rollout I led without a Systems Integrator, and how I fixed each one.

This is Fix #7. Start from Fix #1 to follow the series in order.

A recruiter publishes a job. The requisition says it is posted. But when a candidate opens the career site, the job is not there. This one causes a lot of back and forth between recruiters and the HCM team, because everything in the requisition looks correct. In my case the setup was fine. The search index behind the career site was not.

The symptom

Published requisitions were not showing on the career site. Recruiters could see them in the requisition list. The status looked right. The posting looked right. Candidates searching the career site simply could not find them.

There was no error message anywhere. That is what makes this kind of issue confusing. Nothing fails. The job just does not appear.

Why it happens

The career site does not read requisitions directly from the transaction tables every time a candidate searches. It relies on a search index. In Oracle Recruiting Cloud, that search is powered by Oracle Search Cloud Service, often called OSCS.

When a requisition is published, it needs to be picked up by that index before candidates can find it. If the index is out of step with the data, the career site shows an old picture. Jobs that are live in the application can still be missing from search results.

So there are two separate things to check. First, is the requisition really eligible to show on the career site? Second, has the search index caught up with it? In my case the first was fine. The fix needed an OSCS index rebuild.

How I fixed it

1. I took a few specific requisitions that were missing and used them as test cases for the whole investigation.
2. I checked each requisition's status and confirmed it was open and published, not just approved or saved.
3. I checked the posting details: that it was posted to the right career site, internal or external, and that the posting start and end dates covered today.
4. I searched the career site for those jobs using the job title and the requisition number, and confirmed they were still missing.
5. With the requisition setup confirmed, I treated it as a search index problem rather than a data problem.
6. I ran the OSCS index rebuild for recruiting through the scheduled processes.
7. Once the process completed, I searched the career site again. The missing jobs now appeared.
8. I asked the recruiters to confirm a few more of their recent postings were visible.

How to avoid it next time

• Check the requisition first. Status, career site and posting dates explain many missing jobs before you touch the index.
• If the setup is correct and jobs are still missing, suspect the search index early instead of reworking requisitions.
• Re-check career site search after quarterly updates, bulk requisition loads and career site configuration changes.
• Agree with recruiters on a simple first check: search by requisition number on the career site before raising a ticket.
• Keep a short runbook entry for the index rebuild, so anyone on the support team can run it and verify the result.

Key takeaway

If a published requisition is not visible on the career site and the posting setup is correct, the search index is the likely gap. Rebuilding the OSCS index brought the jobs back for me.

Next in the series: loading learning completions with HDL, and why gaps in the payroll calendar blocked backdated records.

Meeramaheswari Annadurai, Oracle HCM & Enterprise AI. More at meera2k10.github.io/enterprise-ai

```