Box Software Engineer interview questions

4 Software Engineers have shared notes from their Box interviews, with the questions they were asked in each round. That is 57% of the 7 Box interview notes on Screna AI.

4 Software Engineer interview notes

Box·Software Engineer·Technical Phone Screen

Jun 2026
Two-hour coding round at Box for a software engineering role, focused entirely on building a leaky bucket rate limiter from scratch. The interviewer gave a class template to start from, but writing tests was on me, which I didn't fully expect.
  • Implement a leaky bucket rate limiter from scratch, starting with a basic single-threaded version.
  • Extend your leaky bucket implementation to be thread-safe and support concurrent access.

“They gave a class skeleton which helped a bit, but I still had to figure out the core logic myself.”

View Post

Box·Software Engineer·Onsite - System Design / Architecture

May 2026
Box system design round focused entirely on elevator design, which sounds like a classic warm-up but went pretty deep pretty fast once they started pushing on multi-car scheduling and concurrency.
  • Design an object-oriented elevator system. Walk through the core entities, request types, scheduling logic, state transitions, and how you'd handle concurrency and edge cases.
  • How would you differentiate between an external hall call (someone pressing up or down on a floor) and an internal floor selection (a passenger choosing a destination inside the car), and what does that mean for your request model?
  • Walk through the state transitions for a single elevator car, including how you'd handle a maintenance or out-of-service state.
  • How would you extend the system to support express elevators or VIP priority requests without rewriting the core scheduling logic?
  • How do you handle concurrent requests arriving simultaneously, say multiple hall calls across different floors at the same time?

“I started with the obvious classes (Elevator, Floor, Building) and felt good for about two minutes.”

View Post

Box·Software Engineer·Onsite - System Design / Architecture

Apr 2026
Box SWE interview that went deep on rate limiting, both the implementation side and the distributed systems angles. More follow-ups than I expected for what seemed like a straightforward coding problem.
  • Design and implement a Leaky Bucket rate limiter with an allow(request) API that returns whether a request is admitted.
  • How would you make this rate limiter thread-safe? Walk through different locking strategies including mutexes, fine-grained locks, and atomic operations.
  • How would you scale this rate limiter across multiple app servers sharing the same budget for a given user or API key?
  • What are the trade-offs between a leaky bucket and other rate limiting approaches like token bucket, fixed window, and sliding window?
  • How do you prevent the lock from becoming a bottleneck under very high request throughput?

“Started with the bucket metaphor and worked through capacity plus leak rate.”

View Post

Box·Software Engineer·Technical Phone Screen

Apr 2026
Box technical phone screen for a software engineering role. One meaty design question that took up the whole session, which I didn't expect. Walked away thinking I probably over-engineered parts of it.
  • Design and implement an in-memory key-value store that supports transactions, including nested transactions, with SET, GET, UNSET, BEGIN, COMMIT, and ROLLBACK operations.

“The nested transactions part is where I got tripped up.”

View Post