An employer-unfriendly and bureaucracy-filled company that does not invest in engineering
An employer-unfriendly and bureaucracy-filled company that does not invest in engineering
A big company that allows you flexibility in your work schedule.
Other than the upper management, Oracle does not take care of its employees. The culture does not recognize or reward employee performance. Management is not encouraged to build strong, empowered teams. There are many layers of bureaucracy, all designed to compartmentalize information and decision-making. There is absolutely no information sharing with engineers. Even Senior Director-level personnel are pretty powerless when it comes to budget or decision-making. Having now worked there for nearly 4 years, I've lost any internal motivation to excel at Oracle. No one really cares.
Also, Oracle management is interested in selling the product that is there today. They are not interested in investing in the future on engineering products. They are not interested in engaging with external bodies or cooperating with the community at large, even if it is beneficial to Oracle's goals. Management is incapable of looking ahead. I doubt they are rewarded for such thinking.
Treat your employees as adults and trust them to make decisions for the good of the company. An unempowered workforce is inefficient and unmotivated.
Be open instead of having a "Father Knows Best" attitude. For heavens sake, share the profits the company makes with those that help make it.
Was this helpful?
Oracle Interview Questions
Oracle Interview Experiences
Principal Software Engineer
Recruiter call followed by a 45-minute phone screen on CoderPad. The screen included more team-specific questions, and then covered REST concepts, basic questions about microservices, and past work experiences.
Principal Software Engineer
I applied for the job online. The recruiter scheduled a telephonic interview, which lasted for nearly an hour. By the following week, they called for an in-person interview. There were a total of four 1:1 interviews, each lasting 45 minutes.
Principal Software Engineer
It was an internal promotion. The interview was informal. Eligibility was based on the results of a performance review. The rating had to be at least a 4, preferably a 5, on the overall rating scale (out of 5).
Principal Software Engineer
San Jose, California, United StatesJuly 1, 2024Recruiter call followed by a 45-minute phone screen on CoderPad. The screen included more team-specific questions, and then covered REST concepts, basic questions about microservices, and past work experiences.
Principal Software Engineer
San Jose, California, United StatesJuly 1, 2016I applied for the job online. The recruiter scheduled a telephonic interview, which lasted for nearly an hour. By the following week, they called for an in-person interview. There were a total of four 1:1 interviews, each lasting 45 minutes.
Principal Software Engineer
San Jose, California, United StatesOctober 1, 2014It was an internal promotion. The interview was informal. Eligibility was based on the results of a performance review. The rating had to be at least a 4, preferably a 5, on the overall rating scale (out of 5).
