READ. UNDERSTAND. PRACTICE.
Interview experiences
Explore algorithm tutorials, coding and system design questions, interview experiences, and computer science study guides.
3,669 resources · Page 100 of 153
Interview experiences · Oracle Health
Oracle Health Account Executive interview: mock call and behavioral steps
After speaking with the recruiter, the process felt relaxed and early stage. I expected sales-heavy questions, but the conversation was broader: who I was, my experience, what I wanted, and the basics of the account executive role. It felt like a real conversation rather than a grilling. About a week later, I moved into two interviews. The flow included a mock call and a behavioral component, and…
Interview experiences · Oracle Health
Oracle Health Software Engineer interview: five-hour loop and existing Java codebase
A recruiter contacted me about two weeks after I applied. The recruiter call was basic, and a technical screener was scheduled for the following week. That first technical conversation was friendly and straightforward, almost a check on basics such as if-else control flow. The final loop was much harder to arrange: five separate one-hour interviews spread across a week, and I took PTO to make it…
Interview experiences · Oracle Health
Oracle Health Software Engineer interview: four interviews and a two-week offer
The process felt well organized. Some of it was technically challenging, but I never felt completely lost. After a recruiter conversation, I moved through a sequence that added up to four interviews. The discussions were professional and engaging, progressing from core coding to broader engineering questions. I worked through a live LeetCode-style algorithms and data structures question. The rest…
Interview experiences · Oracle Health
Oracle Health Software Engineer interview: LRU cache under pressure
My interview loop was tougher than I expected, although the overall tone was engaging. Across several technical rounds, I implemented an LRU cache and solved a course-prerequisite-ordering problem. The pace kept me on my toes and made it hard to relax into the problems. The last round became more intense with an optimization-style challenge: maximizing the container area between vertical lines. I…
Interview experiences · Oracle Health
Oracle Health Software Engineer interview: trade reconciliation and low-level design
My loop began with a detailed low-level design round where I designed a trade reconciliation service. The interviewer was knowledgeable and helpful, but the bar for clarity and completeness felt strict. I left realizing that my preparation had gaps. Later rounds were more focused. One was described as basic DSA. Another drilled into my projects, asking me to defend design decisions rather than ju…
Interview experiences · Oracle
Oracle Senior+ Backend Engineer Interview Experience — Five Rounds From Elimination Screen to Behavioral
Elimination Round Given an array and an integer k, find the top k most frequently occurring elements. If two elements have the same frequency, the larger element comes first. Questions about Java collections, PriorityQueue, HashMap, and related knowledge points. Deep dive into projects mentioned in the resume. Round 1 Given a string, split it into exactly three non-empty palindromic substrings. N…
Interview experiences · Oracle
Oracle Senior+ Platform Engineer Interview Experience — First Technical Round
Round 1: Technical Interview Maximum of Minimums of Every Window Given an array A of size n and an integer x, implement the following steps: Consider every contiguous subarray of length x, or sliding window. Find the minimum value in each window. Return the maximum of all those minimum values. For example, A = [1, 3, -1, 5, 3, 6] and x = 3: The final return value is 3. The main point of the quest…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — Five Rounds from Top-K URLs to Log Collection
Screening Given a massive volume of URL access logs and limited memory, find the global Top K URLs and the Top K most frequently accessed URLs over the past 24 hours. The main focus was system-design thinking, trade-offs, and pseudocode implementation. Round 2 Given an event stream in the format (userId, eventType, timestamp), find the Top 100 users with the most events during the past hour. This…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — Four Onsite Rounds, Rejected Over a Forgotten Import
Phone screen: break a log into message, timestamp, and level, then query it based on time. Easy-medium difficulty. Round 1 was a bar raiser — pure behavioral questions, around ten of them, all pretty common. Round 2, I don't really remember the specifics of the interviewer, but it was also easy-medium. Round 3 (this is the round I got rejected in): given an array of numbers and a number k, each o…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — IC4 Rejection, IC3 Downgrade, and Relocation
Because the interview happened several months ago, I do not remember the exact timeline very clearly. Phone Screen Implement a service that supports: generate(token_id, time): create a token whose TTL expires at time. renew(token_id, time): refresh the token's TTL so that it expires at time. count(time): return the number of tokens that have not expired at time. BQ1: Tell me about a time when sim…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — OCI Onsite Where the Director Skipped System Design and a Surprise LLD Round, Rejected Without Feedback
JD: a public posting on Oracle's careers site. I mass-applied. Got a recruiter call the very next day, a phone screen a week later, and the onsite another week after that. I interviewed over two days, Wednesday and Thursday. Got told today that I failed, and they won't give any feedback. After talking with them, it felt like there are a lot of openings and they're actively hiring. Phone screen: c…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — Passing a Difficult Remote Interview Process
An Oracle IC3 applicant describes four remote interviews scheduled across a Thursday morning. Two sessions were coding interviews, alongside behavioral and design discussions. During the first coding session, the interviewer could not access the shared coding platform, so the applicant shared their screen. The author reports unclear retry requirements, additional constraints introduced after impl…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — Recruiter Ghosted Me Twice During Scheduling
I got referred to a role on the OCI observability org. About a week and a half later I got an HR call invite. The recruiter was extremely unprofessional — he ghosted me twice total, and I'll complain about it in chronological order below. The first time the recruiter went dark was around scheduling the phone screen in late October. The system-generated interview availability window was a bit shor…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — Same Question Rewritten Three Times in One Phone Screen
Documenting a bad phone interview experience. I don't know if this is typical for OCI, but here's my advice: if you can tell early on you're going to have a hard time communicating with the interviewer, just reschedule. The interviewer was some old guy, and his accent was incredibly, incredibly heavy. That said, there's nothing to be done about that in general — my own team has several people wit…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — Six-Stage Onsite Loop from Brain Teasers to Bar Raiser
Stage 1 Coding Question Max profit using a single buy and sell (best time to buy and sell stock, limited to one transaction). Technical Question Bottom view of a binary tree — explain the implementation approach and the reasoning behind it. Technical Question Find the minimum number of processes allocated. System Design Given a series of webpage URLs (including schemaName, host, port), design a v…
Interview experiences · Oracle
Oracle Software Engineer Interview Experience — Trie Question, Five-Round Virtual Onsite, and an Unprofessional HR Twist
Phone screen (1 round): the interviewer ran the call (I remember his title was something like "senior engineer," though the way it was phrased sounded more like "elderly engineer"). He gave a trie + backtracking question. The prompt: the user types in a string prefix, and you return the 5 most similar existing words. You need to implement two APIs: a. add a word; b. search for a word. If fewer th…
Interview experiences · Oracle
Oracle Software Engineer interview: intern technical sequence
For a Software Developer Intern role, I went through an online assessment, three technical interviews, and an HR interview. The process felt positive and straightforward, and the panelists were friendly. They concentrated on problem solving, understanding my own projects, and core computer-science basics instead of trying to catch me with trick questions. The questions still required real fundame…
Interview experiences · Oracle
Oracle Software Engineer interview: LRU cache and course ordering
The technical rounds were more demanding than I expected. The questions did not seem unfair, but the interviewer energy and live problem-solving pace kept me switching gears. I implemented an LRU cache and then worked on a course-prerequisite ordering problem, which made me think about ordering constraints as well as code. The final round was the most stressful. I had to maximize the area trapped…
Interview experiences · Oracle
Oracle Software Engineer interview: panel rounds and a quick offer
The process felt smooth and organized, and it did not start with technical questions. I first had a screening-style call where the team explained what to expect and set the context. After that, I moved to team interviews that focused more directly on what I could do. I completed two panel rounds, one technical and one behavioral, with questions aligned to the team's interests. The technical panel…
Interview experiences · Orange
Orange Software Engineer interview: long coding and salary discussions
The process made me feel that time and professionalism were not handled well. One interview was extremely long, combining live coding with a prolonged discussion afterward and running late into the evening, while people were still working around me. I passed the technical parts, but the overall atmosphere never became comfortable. At another time, the process felt equally shaky because I was prom…
Interview experiences · Oscar Health
Oscar Health Business Analyst interview: quick recruiter response while the process continued
After I applied, the recruiter responded quickly, which gave the process a positive start. The culture seemed to match what I was hoping for, and communication felt efficient compared with other processes I had experienced. When I wrote about it, I was still in the middle of the process and had not received an offer. I was waiting for the next steps and hoping to hear back soon because I had like…
Interview experiences · Oscar Health
Oscar Health Software Engineer interview: algorithms, system design, and manager round
A recruiter contacted me on LinkedIn, and the process became three rounds. I started with a technical phone screen. The next round covered both an algorithms-style screen and system design, and the final stage was a manager screen. I would not say every detail went perfectly smoothly, but the structure held together: technical evaluation first, then a leadership conversation at the end. I was not…
Interview experiences · Oscar Health
Oscar Health Software Engineer interview experience
Recruiter outreach was quick. After a short recruiter call with basic Q&A, I went to a technical screen that was essentially a hard, tightly constrained LeetCode-style coding task. I was warned that the question would be challenging, and it was. I did not have a comparable pattern fresh in mind, and getting to a complete answer inside the time limit was difficult. The interviewer seemed to know t…
Interview experiences · Oscar Health
Oscar Health Software Engineer interview: silence after coding
The recruiter call was routine, followed by a LeetCode interview. If that went well, I was told the next steps would be a two-hour LeetCode session and a system-design interview. I thought I had done well enough and left feeling that the rounds had gone well. Then the company went silent. I followed up after about a week and still never heard back. That was the frustrating part. Everything before…