Stable But Micromanaged, Zero Input
Stable But Micromanaged, Zero Input
Stable company, large enough to get lost in, with benefits.
Engineering quality is not valued.
Personal development is not valued.
Engineers have little or no input into decision-making.
Managers micromanage.
New groups are routinely formed by picking engineers from unrelated groups without consultation or input from the engineers.
Applicants to vacant positions are of very poor quality.
Good engineers do not want to work here!
Was this helpful?
Oracle Interview Questions
Oracle Interview Experiences
Software Engineer V
For software engineers, expect about 4 interviews: * 2 technical * 1 manager * 1 HR Sometimes, an interview by a matrix manager or the manager's manager may occur. Recruiting is mostly done via headhunting, often through LinkedIn.
QA Engineer
The interview process involved two rounds of phone interviews, followed by an in-person interview with the team. Considering Oracle is a great company to work for, I accepted the offer. The interview process was intense. I was asked many questions ab
Software Engineer
On-campus career fair, then on-site meetings with each team. The interviews were not technical; they involved talking about yourself and learning about the team's work.
Software Engineer V
Redwood City, California, United StatesMay 1, 2011For software engineers, expect about 4 interviews: * 2 technical * 1 manager * 1 HR Sometimes, an interview by a matrix manager or the manager's manager may occur. Recruiting is mostly done via headhunting, often through LinkedIn.
QA Engineer
Redwood Shores, California, United StatesFebruary 16, 2015The interview process involved two rounds of phone interviews, followed by an in-person interview with the team. Considering Oracle is a great company to work for, I accepted the offer. The interview process was intense. I was asked many questions ab
Software Engineer
Redwood Shores, California, United StatesOctober 23, 2016On-campus career fair, then on-site meetings with each team. The interviews were not technical; they involved talking about yourself and learning about the team's work.
