Box Software Engineer Interview Guide

Box's interview process is precisely structured—it runs like clockwork and they stick to the script. It started with an HR meeting covering my background, experience, case studies, and general qualifications. Then came two technical interviews on the same day, each an hour long with a half-hour break between them.

The first interview focused on frontend. I had to improve and fix a dropdown component in an existing repository, work through state management and styling questions, understand React refs, and explain the differences between React and Angular. The second interview shifted to backend. They wanted me to document an API for third-party apps, including request/response structure and data models for cart operations: getting items, adding, removing, updating quantities, and checkout. They also asked me to design the markup for a shopping cart checkout page.

Here's the challenge: there was too much material for the time given. My backend answers took longer than expected, and I didn't have time to cover error handling, edge cases, or security considerations. The interviewer was visibly rushing through topics and jumping around as time ran out. It would have been nearly impossible to fit all those requirements—detailed endpoints, responses, response codes, business logic—into 45 minutes while also writing everything out clearly.

Despite the time crunch, the team did provide clear feedback afterward, which helped me understand their decision not to move forward. The process felt fair in its transparency, even if the scope-to-time ratio was unrealistic.