Oracle Recruiting Cloud: How to Apply and Track Status

Oracle Recruiting Cloud is the recruiting part of Oracle's cloud HR software, and if a careers site sends you to an address ending in oraclecloud.com, that is the system you are applying through. The application itself is short: you enter an email address or phone number, upload a resume or fill in the form, answer the employer's questions, and submit. The step that decides whether anyone sees it comes last. Oracle sends a 6 digit verification code, and its own documentation says an application has to be confirmed to be part of the selection process. Unconfirmed applications are hidden from the recruiter's list by default. This guide walks through the flow, the code, how Oracle differs from Taleo, and where your status lives afterwards.

What Oracle Recruiting Cloud is

Oracle files the product under Oracle Fusion Cloud Talent Management, in two guides called Implementing Recruiting and Using Recruiting. Job seekers and employers mostly call it Oracle Recruiting Cloud, or ORC.

You can recognize it from the address bar. JPMorganChase's careers page at jpmorganchase.com/careers links its job searches to jpmc.fa.oraclecloud.com/hcmUI/CandidateExperience/en/sites/CX_1001, which is the pattern to look for: the employer's name or a code at the front, oraclecloud.com in the middle, and CandidateExperience in the path. Oracle calls the candidate side of the product the career site.

It covers a lot of jobs. On 17 October 2026 our index held more than 41,000 open jobs on Oracle Recruiting Cloud, including more than 2,700 at JPMorganChase and more than 180 at Goldman Sachs. Those counts move every day.

As with every applicant tracking system, the employer configures almost everything you see: which questions appear, whether a resume can be imported, what the phases of the process are called and which emails go out. Our guide to what an ATS is covers how that works across systems.

Oracle Recruiting Cloud versus Taleo

Oracle sells two recruiting products, and they behave differently for a candidate. Taleo is the older one. Oracle announced on 9 February 2012 that it would buy Taleo "for $46.00 per share or approximately $1.9 billion, net of Taleo's cash and debt", according to the announcement Taleo filed with the SEC. Oracle still publishes Taleo Enterprise Edition documentation; its Implementing Career Section guide carries a 2025 copyright.

The University of Pittsburgh is a Taleo example: its job site links to career sections at cfopitt.taleo.net/careersection/....

About "taleo login". There is no single Taleo account. Each employer's Taleo career section has its own sign in, and its settings belong to that employer. The career section guide lists them: whether new users may register, whether to show the "Forgot your user name?" and "Forgot your password?" links (which Oracle calls "highly recommended"), and even a phone number to "use as hotline for users who encounter login problems". So if a Taleo password fails, use the reset links on that employer's career section, not another employer's, and look there for a help contact. Our step by step guide on how to apply for jobs on Taleo walks through the account, profile and forms.

Taleo's status page is also optional. The same guide says the My Submissions page gives candidates the job description and job status for their applications, but that "submission status (in the context of career section work flows) and messaging capability are features available at extra cost to Taleo customers", and an employer can switch the display of submission statuses off. What it can show by default is whether the job is still open. Oracle's default labels map an open requisition to "Accepting Job Submissions", a filled one to "Filled", one on hold to "On Hold" and a canceled one to "Closed".

The application flow

Oracle documents the pieces separately. Put together, an application on Oracle Recruiting Cloud usually runs like this.

1. Start from the employer's own careers page. Search there, then follow its link to the Oracle career site, as JPMorganChase's page does.
2. Pass the bot check if one appears. Oracle lets employers enable hCaptcha, a challenge candidates "must pass before they can join talent communities, apply for jobs, and manage profiles."
3. Enter your email address or phone number. This is your identity on that employer's site. If you already have a profile there, Oracle sends the verification code right away and then shows your saved profile data. If you are new, the code usually comes at the end, as covered in the next section.
4. Import your resume or fill in the form. With Express Apply switched on, you can upload a resume or import from Indeed or LinkedIn, "depending on what's enabled", or follow a link to fill in the classic form by hand. After an import, Oracle shows you "precisely what fields need to be completed", and you only see the blocks with missing information. Read what was imported anyway. A parsed date or job title can come through wrong, and our post on ATS friendly resume format covers what trips parsers up.
5. Answer the employer's questions. Expect prescreening questions and any other blocks the employer added.
6. Sign, if asked. Employers can turn on a job application e-signature. The Implementing Recruiting guide describes its statement as instructions "displayed to candidates when they provide their electronic signature as part of the candidate's application process."
7. Submit, then confirm with the code.

You can stop partway. Oracle's draft application rules say an application is saved automatically, every 10 seconds, once you have given your email address or phone number and agreed to the legal disclaimer. Oracle sends a notification after 60 minutes of inactivity and another 3 days after the last save, each with a link back to the draft. Two details matter: recruiters and hiring managers cannot see drafts, and a draft you leave alone for 30 days is removed automatically. A draft is not an application until you submit it.

Email verification

This is the part most worth understanding. Oracle's page on how candidate job applications are confirmed opens with the rule: "Candidate job applications must be confirmed to be part of the candidate selection process." It continues:

• "In most cases, when external candidates complete a job application they're sent an email or SMS with a 6 digit verification code asking them to confirm their job application. This is the default method."
• A recruiter can resend the code with a Send Confirmation Request action, or confirm the application for you with a Confirm Job Application action.
• "By default, unconfirmed job applications for a job requisition aren't displayed."

The Using Recruiting guide adds that unconfirmed candidates do not appear in recruiters' search results either. So an application where you closed the tab before entering the code is one the hiring team does not see by default, unless someone filters for it.

When the code arrives depends on whether the employer already knows you. Oracle's page on candidate autoconfirmation sets out the cases. With no profile and no saved draft, "the verification code is sent at the end of the apply flow". With a draft, it comes before you enter the flow. With an existing profile, "the verification code is sent as soon as the candidate provides the email or phone." An employer can also turn on autoconfirmation, in which case a brand new candidate gets no code at all and the address is confirmed automatically. So not every Oracle site will ask you.

Returning candidates can meet one more check. Oracle's email authentication settings let an employer ask you to confirm your date of birth or last name before a code is sent "to further verify ownership." You get 4 attempts. After that, everything on the Confirm Your Identity window is disabled except a link to create a new profile, or you can wait 30 minutes and try again. If you create a new profile with an address someone else's profile was using, the previous candidate using that address is marked as unverified.

Codes also come back later. If the employer turns on Keep Me Signed In, you can return without a code for a while, but Oracle requires "a required sign-in 180 days after the initial verification."

What to do with all of that:

• Enter the code before you leave the page. Treat submitting and confirming as one step.
• Use one email address for every application to the same employer. Your profile, your drafts and your returning-candidate checks all hang on it.
• If no code arrives, check spam and junk, then contact the employer. The recruiter is the one with the resend and confirm actions, so ask the employer rather than Oracle.

Tracking status

Your status lives on the employer's career site, on what Oracle calls candidate self service. You "must confirm their identity to access the candidate self service", which usually means another code. Once in, Oracle documents that you can:

• view your applications in three lists, Active, Inactive and Draft, with up to 5 shown in each and a Show More button for the rest; any active application that needs your attention is listed first,
• confirm an application you did not confirm earlier,
• withdraw, at any phase before the Offer phase,
• schedule, reschedule or cancel interviews, if you were invited and the employer allows it,
• edit or delete your profile, and set job alerts.

Employers name the entrance differently. St. Olaf College's candidate FAQ tells external applicants to log into its careers site, click their profile and open the My Application section.

The status words are mostly the employer's. Oracle documents that an employer can rename the default phases and states, and the new names appear wherever the current phase and state of an application are shown. One set of labels is fixed in the documentation: for evergreen "pipeline" postings, Oracle's page on pipeline requisitions says the self-service page shows Under Consideration while you have an active application, Not Retained once every application is rejected or withdrawn, and Offer Accepted once an application on a linked job reaches the HR phase. Our post on what under consideration means goes through how the same words read in Workday, Greenhouse, Taleo and SmartRecruiters.

Two more things change how you read the list. An application that moved to Inactive after a withdrawal can sometimes be reopened: if the employer turns on reapplying after a withdrawal, your profile prefills a new application, but you answer the prescreening questions again and start "at the beginning of the candidate selection process". And a draft in the Draft list was never submitted, whatever you remember doing.

Where ApplyEze fits

Oracle Recruiting Cloud is one of the 12 platforms ApplyEze completes applications on end to end, alongside Greenhouse, Lever, Ashby, Workday, Workable, SmartRecruiters, JazzHR, BambooHR, Rippling, Pinpoint and Recruitee. On Oracle and Workday it applies only when an application inbox is connected, because both rely on email verification during the application. It runs on your own machine in a visible browser, and a dry-run mode fills the form without clicking Submit. If you also apply to Workday employers, our guide to creating a Workday account covers the account step Oracle mostly skips.