Dropped Requests
Reported by candidates from Amazon's online assessment. Pattern, common pitfall, and the honest play if you blank under the timer.
Amazon's "Dropped Requests" problem hit the OA circuit in January 2024, and candidates are blanking on it cold. You've got a queue or stream of requests, some get dropped, and you need to figure out the pattern or count the fallout. The trick isn't the data structure, it's understanding what "dropped" means in context. If you've never seen this one before, StealthCoder will read the exact problem statement on your screen and hand you the pattern in seconds. Most candidates lose points here because they misinterpret the drop condition on their first pass.
Pattern and pitfall
Without the full problem text, the pattern likely involves either simulation (processing requests in order and marking which ones fail a condition) or counting (how many requests don't meet some threshold or constraint). Amazon loves queue-based problems, so expect something like: requests arrive, each has a property (timestamp, priority, size), and if a certain condition isn't met (buffer full, timeout, rate limit), it's dropped. The gotcha is off-by-one errors or misunderstanding when the drop happens relative to processing. Use a straightforward simulation with a data structure like an array or queue, track state carefully, and don't over-engineer. StealthCoder acts as your safety net if you freeze on the exact problem definition or the edge cases around when a request transitions from valid to dropped.
If you see this problem in your OA tomorrow, the play is to recognize the pattern in 30 seconds. StealthCoder buys you that recognition.
You can drill Dropped Requests cold, or you can hedge it. StealthCoder runs invisibly during screen share and surfaces a working solution in under 2 seconds. The proctor sees the IDE. They don't see what's behind it. Built by an Amazon engineer who passed his OA cold and still thinks the filter is broken.
Get StealthCoderRelated leaked OAs
You've seen the question.
Make sure you actually pass Amazon's OA.
Amazon reuses patterns across OAs. Built by an Amazon engineer who passed his OA cold and still thinks the filter is broken. Works on HackerRank, CodeSignal, CoderPad, and Karat.
Dropped Requests FAQ
What does 'dropped' actually mean here?+
Without the full problem, it's likely a request that fails to meet a constraint (buffer capacity, rate limit, deadline, or priority threshold). Read the problem statement three times. The definition of 'dropped' is buried in one sentence and candidates miss it the first time.
Is this a queue or array problem?+
Most likely both. You'll simulate processing requests in order using a queue or list, track state, and output either the count or indices of dropped requests. Don't assume the data structure until you've read the full problem.
What's the common pitfall?+
Misunderstanding the drop condition or the order of operations. Does a request get dropped before or after it's processed? Does the drop depend on current buffer state or a pre-computed value. Test your logic against the examples carefully.
How do I code this fast?+
Write a clean loop that iterates through requests, maintains a simple state variable (buffer count, timestamp, whatever), and appends to a 'dropped' list when the condition is true. Skip premature optimization. Correctness first.
Is this still asked at Amazon in 2024?+
Yes, queue and request-handling problems remain common. Expect variations. The pattern (simulation with clear state tracking) is core to Amazon's OA. Master the fundamentals and you'll see this theme again.