I applied through other source. I interviewed at Box (Redwood City, CA) in Jun 2016
Interview
I was contacted initially by a recruiter on LinkedIn. After an initial conversation with the recruiter, I then had a standard phone interview that involved a discussion with a senior engineer and a simple coding question. I used collabedit to code.
After the phone interview, I was invited onsite. Box had an interesting onsite interview process. Rather than conducting a series of whiteboard coding questions using algorithms and data structures, their format was a bit different. I'm not sure if this is standard for all engineering candidates or if this was unique to the team and position I was applying for.
My interviews consisted of:
* A system design question
* A technical communication session (describe a significant project you worked on and discuss tradeoffs, outcomes, design decisions, etc)
* A 90 minute coding exercise on my laptop
* A simulated code review where I audited and reviewed some code written by a junior engineer
* Lunch with the hiring manager
The sessions are intended to simulate what an engineer might do on a day to day basis at Box.
In my particular case, I had a little bit of trouble with the coding exercise and the system design question. The interviewers liked what they saw in my experience and with what they saw in the other sessions, so I was asked to come back for a second onsite a week later. The second onsite consisted of:
* A whiteboard question
* A conversation with the VP in charge of the group I was interviewing for
* A second lunch with the hiring manager
None of the questions involved any of the classic interview questions that I had seen before. The coding exercise wasn't too bad, but I missed a key requirement which ended up making my code verbose and a little too complicated. I ended up re-implementing the code at home after the interview and without the pressure of being in an interview setting, and it was a much easier exercise. My advice for this section is to definitely pay attention to the requirements given to you and not to rush. I was also given a phone number and email address to use if I had questions, so I would also advise to ask questions if there are ever any doubts around what you're building.
Throughout the process, the interviewers were very nice and happy to answer any questions I had about what it was like to work at Box. The conversation with the VP in particular was very good. I felt like I got very sincere and honest answers on all the questions that I had.
The recruiters were also very responsive and very quick to schedule
In the end, I was not extended an offer, but it was a great experience from start to finish. The whole process took about 3 weeks from start to finish.
7
Other Senior Software Engineer Interview Reviews for Box
Straightforward. They're looking for your approach towards a problem and how efficient your solution is, they don't care about any coding syntax hiccups.
There were multiple questions (not all LC)
- Unix Commands
- Identify Synchronization Issue in the given code
- Find K Most Frequent words across all files in a given dir path
- Flip Kth Bit
I applied through an employee referral. I interviewed at Box in Feb 2026
Interview
Short screening with HR. Followed by dropdown implementation fix for frontend. Then to implement todo list via React. Last full-stack to implement Cart logic with pseudocode. Interviews around one hour long. And interviewers are pretty chill and ready to help you in the process.
Interview questions [1]
Question 1
Write a cart logic specification document intended for a backend development team to use as an implementation guide.
At first I applied via job board, then recruiter screening, one week leater System design interview and Coding interview. I get declined at this step with quiet big feedback. All take around 3 weeks. And meeting in summarize was 4 hours.