Really no pros of working at Oracle, apart from having a big company on your CV.
Remote work.
Not sure where to start, but there are many things that are so wrong, especially for a big company such as Oracle. Management is not empathetic at all with the engineers; they will try to squeeze as much work as they can for free. If you end up working for OCI in the UK, you'll just be part of a support team doing on-call shifts and doing basic bug-fixing work.
On-call is a full 84-hour week, which you are expected to work with no extra compensation. If there is an incident, those hours might increase further. Deployment processes are extremely slow.
If you're eager to learn, this is the wrong place for you. Instead, if you want to have a stagnant career, you'll love this place.
Boring place to work, no real learning opportunities, as all new features and design docs come from engineers in the US.
Care about the people that work for you instead of trying to exploit them as much as you can. Listen to the people that work for you; listen to their suggestions, regardless of experience level.
I was out in one round. I didn't prepare very well for it, but that was my mistake. The interviewer was excellent. It was my first interview, in my whole life, so yeah, I think it was supposed to go badly. Always prepare for the interview; you nev
The interview started with introductions, followed by 30 minutes of behavioral questions and 30 minutes of technical questions. The technical portion required looking at JavaScript code and then telling what each section would print out.
I faced three basic data structure and algorithm questions. I came up with some answers, but they wanted a more refined solution. The first phone interview went great, but the technical screen-sharing portion that followed was with someone who was i
I was out in one round. I didn't prepare very well for it, but that was my mistake. The interviewer was excellent. It was my first interview, in my whole life, so yeah, I think it was supposed to go badly. Always prepare for the interview; you nev
The interview started with introductions, followed by 30 minutes of behavioral questions and 30 minutes of technical questions. The technical portion required looking at JavaScript code and then telling what each section would print out.
I faced three basic data structure and algorithm questions. I came up with some answers, but they wanted a more refined solution. The first phone interview went great, but the technical screen-sharing portion that followed was with someone who was i