Oracle Senior Software Engineer Technical Phone Interview Throttling Design
Interview Experience
I recently had a phone screen with Oracle for a Senior Software Engineer role and was asked the following question: "In a first-person shooter (FPS) game, players trigger actions like shooting, reload
Full Details
I recently had a phone screen with Oracle for a Senior Software Engineer role and was asked the following question: "In a first-person shooter (FPS) game, players trigger actions like shooting, reloading, or throwing grenades by pressing keys. During intense gameplay, players may press the same key repeatedly in a short period of time, which can lead to excessive event triggers." I was asked to design a throttling mechanism that ensures the same event type can only be triggered once within a given delay period. If the same event occurs again before the delay expires, it should be ignored. Each event type should be handled independently.
Example: delay = 5 events: [("shoot", 1), ("shoot", 2), ("reload", 3), ("shoot", 6)]
output: [true, false, true, true] This is the solution I came up with. Curious to know if there's a more optimal approach.
public class EventThrottler { private final Map
return true; } long lastTime = lastTriggered.get(eventType); if (currentTime - lastTime >= delayMillis) { lastTriggered.put(eventType, currentTime);
return true; }
return false; } }
One optimization I could think of is to use a ConcurrentHashMap instead of a regular HashMap for a multithreaded environment.
About This Question
This is a candidate experience report from a oracle interview for a swe role (senior level) during the phone screen round reported in 2026.
It covers the following topics: Hash Table, System Design, Strings .
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.