Oracle is known for its database software, and it also offers cloud infrastructure, business applications for finance, human resources and supply chains, and the Java language. As a fresher, prepare to explain database fundamentals through business examples: an index on an employee table, a transfer between two accounts, a payroll table with repeated data. Bring college projects that used a database or Java. What to show here: solid database and Java fundamentals, explained in plain words. Each question below has what the interviewer is checking, an answer frame and a sample spoken answer to adapt.
How Oracle hires, in its own words, and its questions for every job →
“In my library management project I stored each book's author as text in the books table. When we added a screen to list all books by an author, spelling differences meant the same author appeared several times. By then three screens depended on that table. I created an authors table, wrote a small script that filled it from the distinct names and fixed the spellings by hand, then replaced the text column with an id. I updated the screens one by one. It took a weekend. Now I draw the tables and their relationships before writing any screen. The result was your result.”
Weak answers patch the screens to hide the problem, or say they have never had a design mistake.
“In my internship, a report page took almost a minute to load. My first guess was the network, but I measured each step and found that the database query took most of the time. The query looked simple, but I printed the plan and saw it read the whole orders table for every customer row. There was no index on the customer id in the orders table. I added the index and the query returned in well under a second. I also rewrote a loop that ran one query per row into a single join. I learned to measure first. The result was your result.”
Weak answers change random things until it feels faster and cannot say what the cause was.
“Without an index, the database has to read the whole table to find one employee, and that cost grows with the number of employees. An index is a separate sorted structure, usually a tree, that maps each id to the location of its row, so the database finds the row in a few steps. The cost is that every insert, delete and update of that column must also change the index, so writes become slower and the table takes more space. If a table is small, or is written far more often than it is read, an index on that column may not be worth it.”
Weak answers say indexes always make things faster and cannot explain the cost on writes.
“A transaction is a group of changes that the database treats as one unit: either all of them happen or none of them do. In the transfer, the first update takes money from one account and the second adds it to the other. If the power fails after the first update but before the commit, the money would simply vanish. So on restart the database reads its log, sees the transaction never committed, and undoes the first update. Once a transaction is committed, the database has already written enough to its log that the change survives a crash.”
Weak answers describe a transaction as just a set of queries and do not know what happens on a crash.
“Repeating the department name on every row wastes space, but the bigger problem is that the same name can be typed in different ways, and a rename means updating thousands of rows, some of which may be missed. Then a report by department gives wrong totals. I would create a departments table with an id and a name, and store only the id in the payroll row. The same for managers. There is one exception. Payroll is history, so if we must know which department an employee was in during a given month, I would keep the department id on the row for that month.”
Weak answers recite the normal forms and cannot say what goes wrong in the payroll example.
“In Java I do not free memory myself. The garbage collector runs from time to time, finds every object that can still be reached from running code, and frees the rest. So an object nobody refers to is freed at some point. Memory can still run out when objects are no longer needed but something still refers to them. In my college project I stored every request in a static list for logging and never removed anything, so the program used more memory every hour. A cache without a size limit does the same. The collector cannot know the program has forgotten about them.”
Weak answers say Java has no memory problems, or confuse garbage collection with closing files.
“First I would check whether I am still inside a transaction that has not been committed. If so, I roll it back and nothing is lost. If it was committed, I would tell my team right away, before anyone builds test results on the bad data. Then I would look for the quickest way to restore the table, such as the last backup of the test database or a copy of the table someone loaded recently. After that, I would suggest we set the tool to require a where clause or to ask before a large update. Hiding it would waste my teammates' time.”
Weak answers quietly try to fix the data by hand and tell nobody.
“The database course was the one where things clicked for me in college. I liked that a query planner decides how to find data, and that a transaction promises something even when the power fails. Java was the language of most of my projects. Oracle builds the database many businesses run on, plus cloud infrastructure and applications for finance and human resources, so the fundamentals I enjoy are the daily work here. I want to learn how these ideas hold up at a scale far beyond my college projects, from people who have built them.”
Weak answers give reasons about size or brand and cannot say what the products do.
No figures on this page: pay depends on the level, the city and the offer in front of you. When the offer comes, the free salary negotiation script helps with that part.
ClapAssist is an AI interview assistant for Mac and Windows. It listens to the interview on your computer and shows you what to say, in short lines you can read while you talk. Your live interview audio and screen are never stored. Your resume and notes are saved to your account so the app fills them in on any computer. It is hidden from screen share on every plan, including Free; only you can see it.