When are Oracle performance reviews? (2026)
Oracle runs on a fiscal year ending in May, and its evaluation rhythm follows that rather than the calendar. Cycle dates vary by org, so anchor your record to fiscal-year goals and the customers behind them.
Once a year
No specific review month is published for this company, because none could be sourced from the company's own material. What follows is the cycle shape, which is what is actually knowable. Your own manager is the authority on this year's dates.
How the cycle works
Oracle's fiscal year ends on the last day of May, a matter of public record in its financial reporting, and that single fact rearranges the working year. The final fiscal quarter is the heaviest stretch in the company, the new year's targets land in early summer, and anything you want counted needs to be counted against the fiscal year rather than the calendar one.
This is a large, long-established enterprise company with a very wide product surface: databases, middleware, applications, and cloud infrastructure, sold largely to organizations that will still be running it a decade from now. Evaluation reflects that time horizon. Work that keeps an existing large customer successfully running is valued alongside work that ships something new, which is not true everywhere.
Cycle specifics differ substantially between engineering, consulting, sales and support organizations. Confirm your own with your manager rather than assuming a neighboring group's schedule applies.
What actually gets weighed
Named-account outcomes carry unusual weight. In an enterprise business, a single customer can represent a large commitment, and being the person a major account depended on is a specific, defensible claim. Name the account where you are permitted to.
Backward compatibility and upgrade safety count as engineering quality here rather than as constraints on it. Customers run these systems for many years, so a migration path that did not break anyone is a real accomplishment, and breaking one is expensive in a way that shows up long after the release.
Fiscal-quarter delivery matters, particularly work that unblocked something before a quarter closed. The organization remembers the last few weeks of a fiscal quarter with unusual clarity.
Cross-product coordination is the fourth axis, because the product surface is wide and customers buy combinations of it.
What to have ready
- Your goals as written at the start of the fiscal year, and the outcome of each, in the original wording.
- Accounts or deployments where your work was a specific dependency.
- Migrations and upgrades you shipped, with what did not break.
- Anything that landed in the closing weeks of a fiscal quarter, since that is disproportionately remembered.
- Assemble it in the spring rather than after the summer reset, while the fiscal year is still the frame everyone is thinking in.