Throw the Ball
Reported by candidates from Flexport's online assessment. Pattern, common pitfall, and the honest play if you blank under the timer.
Flexport's May 2024 OA included a problem called 'Throw the Ball,' and you're staring at it right now wondering what the trick is. No problem text survives in the wild, which means candidates either nailed it quickly or got stuck guessing the rules. This is exactly where StealthCoder acts as your safety net: if you blank on the mechanics mid-assessment, you have a live overlay reading the problem and feeding you the pattern while the proctor sees nothing.
Pattern and pitfall
Without the exact problem statement, the most common 'ball-throwing' OA pattern involves simulation, greedy logic, or graph traversal. Candidates typically get tripped up on edge cases: what happens when the ball reaches a boundary, who catches next, does order matter. The trick is usually that you need to simulate the throws step-by-step or recognize a cycle, not derive a formula. Many stumble by over-engineering when a straightforward loop or BFS works. StealthCoder helps here by letting you re-read the problem with fresh eyes if your first approach stalls, cutting down panic and wasted code time.
Memorize the pattern. If you can't, run StealthCoder. The proctor sees the IDE. They don't see what's behind it.
You can drill Throw the Ball 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. Made by an engineer who treats the OA as theater. If yours is tonight, you don't have time to grind. You have time to hedge.
Get StealthCoderRelated leaked OAs
You've seen the question.
Make sure you actually pass Flexport's OA.
Flexport reuses patterns across OAs. Made by an engineer who treats the OA as theater. If yours is tonight, you don't have time to grind. You have time to hedge. Works on HackerRank, CodeSignal, CoderPad, and Karat.
Throw the Ball FAQ
Is 'Throw the Ball' a simulation or math problem?+
Almost certainly simulation. You're tracking state across throws, likely updating positions or catching order. Math shortcuts rarely work here. Build the simulation first, optimize if needed.
What's the most common mistake on Flexport ball-throwing problems?+
Assuming the pattern is obvious without testing edge cases. Boundaries, cycles, and invalid throws trip people up. Write test cases as you code.
How much time should I spend before coding?+
3-5 minutes to clarify the rules, draw a small example, and identify the loop or end condition. Jumping straight to code without understanding the mechanics wastes 15-20 minutes.
Is this problem still asked at Flexport?+
It was reported in May 2024, so very likely. Flexport OAs rotate slowly. If you see it, you're prepared.
What if I don't recognize the pattern mid-OA?+
Slow down and simulate by hand with a small input. That always works. Write the brute-force solution, then optimize. Don't get stuck on theory.