Oracle OCI IC3 Software Engineer Interview Experience Networking Team
Question Details
Recently I got chance to interview with OCI Networking Team.
**
Round 1 Screening**
Coding Reverse a linked list (Write end-to-end code). Find the intersection point of two linked lists. Networking &
Full Details
Recently I got chance to interview with OCI Networking Team.
**
Round 1 Screening**
Coding Reverse a linked list (Write end-to-end code). Find the intersection point of two linked lists. Networking & Debugging: Basic networking and debugging questions. Scenario Based : Packet drop debugging. Given a three-router topology (R1→R2→R3), if a packet is not received at destination R3, how would you debug this scenario and identify where the packet is being dropped?
Loop Round 1
Coding A warehouse manager needs to create a shipment to fill a truck. All products are in identical-sized boxes, but each product has a different number of units per box. Given the number of boxes the truck can hold, determine the maximum number of units of any mix of products that can be shipped.
Example 1 boxes = [1, 2, 3] (boxes available for each product) unitsPerBox = [3, 2, 1] (units per box for each product) truckSize = 3 (maximum number of boxes the truck can hold)
Output: 7 Linked List: Given a linked list where each node contains either 0 or 1,
return the equivalent decimal value.
Loop Round 2: Systems Design & Networking LLD/
HLD Design a Logging File System. Design an LRU Cache and explain the choice of data structures used. Networking: Explain how Ping works in detail. Basic networking and scenario-based questions. Project: Detailed discussion regarding previous project work.
Loop Round 3: Architecture & System Design Project Discussion:
Explanation of previous project architecture.
System Design Questions focused on latency and scalability.
Coding Find the intersection point of two linked lists without using any extra space.
**
Round 4 Managerial** Project & Networking: Discussion on current projects and basic networking concepts.
System Design Design a Cache System. Documentation: Provide an Estimation of Effort (EoE) and a rough Specification Document for the designed system. Waiting for result .
About This Question
This is a reported interview question from a oracle interview for a swe role (junior level) reported in 2026.
It covers the following topics: Linked List, System Design .
Difficulty rating: Easy
Topics
More Oracle Interview Questions
About Oracle Interview Reports
This question was reported by a candidate who interviewed at Oracle. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Oracle are the higher-signal extractions to take from this report.
For broader preparation context, the Oracle interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Oracle reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Oracle Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Oracle reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.