Box Interview Questions

All 10 Box questions collected here were asked in an onsite round, and 9 of them came from Software Engineer interviews, so there is no separate phone-screen format to prepare for. The coding half leans systems rather than puzzles. Candidates report implementing a leaky-bucket rate limiter, computing Top-K word frequencies across every file under a path, and being handed working code that deadlocks so they can find the lock ordering that causes it. One question is closer to on-call work than to an algorithm: diagnose a failure over SSH with nothing but large log files, which really tests how you narrow a search space out loud. The design slot includes an out-of-order windowed stream processor, where the interesting part is late-arriving events and how long you hold a window open before emitting. Only two of the ten are runnable in a console, so most of the preparation here is reasoning rather than typing, and eight come with a written solution. Difficulty sits mid-range: 6 medium against 3 hard and one easy. 90% of the page reads without an account.