Real, anonymous reports from people who interviewed for Software Engineer at Box, newest first and distilled into what to expect across the loop.
I went through what started as a promising process and turned into a long endurance test. First I had multiple rounds with a professional, easy-to-talk-to interview team, and at around the middle point I was told I had cleared everything. Even so, the hiring timeline kept stretching, and after that I hit a “cooling-off” period of about four weeks with no communication. Just when I thought it was over, I was told there had been a “policy change,” and I had to complete three more rounds that effectively revisited similar conversations.
My Box Software Engineer interview felt like a classic LeetCode-style journey, but with an emphasis more on data structures than algorithms. The first technical screen ran about two hours, and the interviewer joined at the start and again at the end just to discuss results. The next coding/DSA round lasted about an hour with the interviewer on the call the whole time, followed by a separate LLD interview and then a behavioral interview with the hiring manager.
The interview process at Box typically involves multiple rounds, often spanning several weeks, with a mix of technical and behavioral assessments. Candidates noted that while the structure was generally clear, the timeline could feel prolonged and sometimes lacked timely communication.
Candidates experienced a variety of technical interviews, including coding challenges focused on data structures, algorithms, and system design, with an emphasis on problem-solving and reasoning over syntax. Some rounds involved practical tasks like building components in React or fixing existing code.
Behavioral interviews at Box often assess cultural fit and alignment with company values, with candidates expected to discuss their experiences and how they relate to the role. The tone of these interviews varied, with some candidates feeling rushed or misunderstood.
Feedback from interviewers was inconsistent, with some candidates receiving minimal or generic responses post-interview, leaving them unclear about their performance. While some appreciated detailed feedback, others felt the lack of clarity in outcomes was frustrating.
The overall environment during interviews was described as professional and supportive, though some candidates reported experiences with disengaged interviewers or unclear questioning that affected their performance. Positive interactions were noted, but inconsistencies were common.
Final rounds often included a mix of technical and behavioral evaluations, with candidates expressing that a single poorly managed interview could overshadow earlier positive experiences. Many reported receiving automated rejection emails without clear explanations.