Box Software Engineer candidates report a recruiter screen, hands-on React or JavaScript coding, algorithm and system design rounds, and hiring manager conversations. Reported total timelines run about 3 to 5 weeks.
$182K
Avg. Base Comp
$245K
Avg. Total Comp
Not reported
Typical Rounds
3-5 weeks
Process Length
Candidates describe a Box Software Engineer loop that is organized and well communicated, but not uniform. Frontend-leaning reports center on hands-on JavaScript and React work: an Emitter class built in JavaScript, a dropdown component, and a to-do list app in React. Other candidates report data structure problems such as top K frequent words, bit manipulation and priority queues, plus a system design prompt to design an elevator system.
One candidate described a same-day frontend and backend pair. The frontend hour involved fixing a dropdown in an existing repository and questions on React refs. The backend hour asked for API documentation for shopping cart operations, and that task felt too large for the time available. Another candidate said the elevator design round required gathering requirements, proposing an architecture and ideally writing working code against the clock. Practice scoping quickly and saying out loud what you are leaving out.
The final stage appears to carry real weight. Two candidates describe hiring manager conversations after strong technical rounds that still ended in rejection, one citing backend experience and another citing lack of experience. Be ready to explain your past projects clearly, discuss your tech stack choices, and show breadth beyond your strongest area.
Feedback quality varies. Some candidates received detailed written feedback for each round, while others got an automated rejection or no specific notes, so ask about next steps and dates. Reported end-to-end timelines range from about 3 to 5 weeks.
Synthesized from 18 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Box process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Box
What is the probability that no two passengers will get off at the same floor
| Question | |
|---|---|
| Max Width | |
| Three Indexes Adding Zero | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Prime to N | |
| Top 3 Users | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Raining in Seattle | |
| Minimum Change | |
| Find the Missing Number | |
| Customer Orders | |
| Bagging vs Boosting | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Scrambled Tickets | |
| Weighted Keys | |
| The Brackets Problem | |
| Flight Records | |
| Rectangle Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR call covering background, experience and the role. One candidate said the recruiter clearly outlined what to expect at each stage. Ask for concrete next steps and dates before you leave the call.
Reports vary here. One candidate describes a one-hour live coding screen with three independent problems, including bit manipulation, top K frequent words and finding issues in synchronized code. Another describes an algorithms round with priority queues. The format may depend on team and level.
Frontend-leaning candidates report building a dropdown component, an Emitter class and a to-do list app in React or JavaScript. One candidate also discussed how the Internet works. Expect time pressure, and be ready to explain your choices as you work.
Candidates report an elevator system design and a backend task documenting an API and data models for shopping cart operations. Both mention that time was tight, so move from requirements to architecture quickly and state your tradeoffs.
The last stage typically includes hiring manager conversations and, for some candidates, a behavioral interview. Outcomes were mixed even after strong technical feedback, so prepare to discuss your projects, tech stack and backend or frontend breadth in plain terms.
