Thank you for considering a career with Oracle! We have reimagined what the cloud can do for businesses, and are looking for creators who want to influence the future.
You are the builder here and, as such, we want to help you show off the best of your abilities throughout the technical interview process. Know that we’ll be testing your coding skills and problem-solving abilities, as well as considering how well you’ll fit into our company culture. We want to see how you think, how you solve a problem, and how you embody our values.
How to prepare
Whether you’re a new coder or an experienced engineer, it’s always a good idea to do some prep work before a technical interview. We don’t expect you to spend days preparing, so we rounded up our best advice from Oracle engineers and made a list of (optional) resources that will help you get up to speed if you need a refresher.
Step 1: Refresh on core computer science concepts
Interviewers will present problems and coding challenges from an array of topics, so it’s best to re-familiarize yourself with coding principles such as:
Your own bookshelf, local library, or eReader likely has a number of books that can refresh your knowledge with a quick scan. Cracking the Coding Interview is certainly one of the most detailed guides available, but here are a few other recommendations from our engineers:
You may also wish to watch lectures on coding concepts and distributed systems topics. Our engineers recommend:
Step 2: Practice problems
Throughout the process, you’ll be presented with a problem to solve and asked to present a solution using code and, time permitting, create a test case. You can solve coding problems in whichever language you feel most comfortable, unless otherwise noted. Many of the books above include exercises, as well as these sites: https://hackerrank.com, http://www.spoj.com, https://uva.onlinejudge.org.
Here are a couple examples from our engineers:
When you're practicing, try writing out solutions long-hand on paper. This better mimics the conditions of an interview in most cases, rather than using an IDE with code-completion. Things you struggle to remember are good things to review. Also, consider how you would communicate your work as you go; remember, we want to understand how you solve problems and not just see the code.
Step 3: Ace the interview
The big day has come! Now here are some additional tips to ace the live interview process.
Finally, remember that these resources are optional and to be used as you wish. However, if this list feels intimidating in scope, or something you’re not reasonably fresh on, feel free to request more time to brush up before continuing your interview process.