
Creating a job in Oracle Recruiting Cloud is straightforward once you understand the workflow. The process typically starts with a job requisition that needs approval before it becomes a published job. Here’s how I usually do it:
First, log into Oracle Cloud with the appropriate role (HR Specialist or Recruiter). Navigate to the Recruiting work area and select Create Job Requisition. You’ll be prompted to fill in key fields: job title, department, location, employment type (full-time, contract, etc.), and the salary range. Oracle allows you to pull from pre‑existing job profiles or create a new one. I always recommend using a structured job description that includes responsibilities, qualifications, and success metrics—this improves candidate matching later.
Next, set up the approval workflow. Oracle uses a configurable hierarchy, so you might need to select a hiring manager and a budget approver. If your organization uses FTE (full‑time equivalent) budget tracking, ensure the headcount is available. Once submitted, the requisition goes through an approval chain. You can monitor its status in the Requisitions dashboard.
After approval, you can publish the job to multiple channels. Oracle integrates with job boards like LinkedIn, Indeed, and your company’s career site. You can also set up screening questions and knockout criteria to filter candidates early. For example, I always add a compulsory question about work authorization to save time.
Finally, activate the job and share the direct link with your team. Oracle will automatically track applicants, source of hire, and time‑to‑fill metrics. One tip: use the bulk upload feature if you’re creating multiple similar roles—it saves hours.
Here’s a quick reference table for the key steps:
| Step | Action | Typical Duration |
|---|---|---|
| 1 | Fill job requisition details | 15–30 minutes |
| 2 | Attach job profile and approval chain | 5–10 minutes |
| 3 | Submit for approval | 1–3 business days |
| 4 | Publish to job boards | Instant after approval |
| 5 | Set up screening questions | 10–15 minutes |
The entire process, from creation to posting, usually takes under a week, with most of the waiting time spent on approvals.

I handle job creation mostly by copying an existing requisition that’s similar. Oracle has a Clone Requisition option that carries over the job profile, salary range, and even the approval chain. Then I just tweak the title and location. It’s a huge time‑saver, especially when I’m hiring for multiple positions in the same department. The only thing I double‑check is the budget code—sometimes the cloned one points to an old project. Also, I always refresh the posting schedule so the job doesn’t accidentally go live on a weekend.

From my perspective, the most critical part is the approval routing. Oracle allows you to define conditional approval rules—for example, if the salary exceeds $120,000, it needs VP sign‑off. I set this up in the Configuration Workbench under Recruiting. Another thing: EEO/OFCCP compliance fields must be filled out correctly. Oracle has a dedicated section for equal opportunity data, and if you skip it, the system blocks publication. I always run a pre‑validation check before submitting to avoid back‑and‑forth.

When I need to create a job, I first check if the job description is already in the Oracle library. Our HR team maintains a set of standardized templates. I select the one that matches the role, then adjust the skills and competencies to fit my team’s needs. The custom attributes are handy—I can add fields like “required certifications” or “travel percentage.” One thing I’ve learned: always set the internal posting period to at least 5 days before going external. It gives current employees first crack and reduces turnover.

I’m often the one configuring the backend for job creation. The key is to ensure the data model is mapped correctly. For example, if you want to use a custom salary range table, it needs to be imported into Oracle’s Compensation module first. The job profile hierarchy is also important—each job title should link to a grade and a pay band. I also set up automated notifications so that when a requisition is created, the hiring manager gets an email with a link to the draft. That way, they can review it before it goes to approval. Test the flow in the sandbox environment before going live.


