
Box Frontend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 14 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Box.
Frontend Developer
The interview process had three main parts: a frontend task to build a To-Do list in React (1 hour) plus a coding task to make an Emitter class in JavaScript and talk about how the internet works (1 hour). Then there was a JS Architecture Interview, which was another frontend task for me to create a dropdown in React (1 hour). Lastly, a Culture Interview, which was a 30-minute chat about my experience and if it fit with Box’s values. The Hiring Manager Interview was a 45-minute talk on my experience and soft skills. It feels long but they tell you about each step beforehand and you can pick your own times. Some interviews are back-to-back which might seem tough, but the interviewers are nice and helpful, some even new to Box. You get feedback after each interview about what they tested and how to improve, which is good. But, the final stage was the worst. It really depends on the Hiring Manager and team. I had two interviews with different managers, both went okay talking about my experience and tech. I got rejected both times. First time because I lacked backend experience. Second time, no feedback, just an automatic rejection email. It seemed like they don't consider your previous interview scores, maybe they just don't like you. P.S. Former employees said negotiating salary raises is hard there, so be happy with the offer for a few years.
No confirmed questions were included in this interview report.
Senior Frontend Developer
The interview process takes quite a long time, includes live coding, problem-solving skills, theoretical knowledge, and culture matching. Before each part, you get well-informed about the next steps and have some time for preparation.
- How would you approach a Leetcode Hard problem involving algorithms?
- Can you complete this React live-coding exercise?
- Discuss JavaScript architecture patterns.
Frontend Engineer
So there were 6 stages in total. 3 were coding tests on HackerRank and the other 3 were about cultural fit and problem solving. The interviewers were not friendly at all. They did not even say hello back. The tests were not timed properly. The interviewers looked like they just wanted to end the call. The whole process was disorganized. For example, I was supposed to answer JavaScript questions but they asked React questions instead. After all the time I spent, I got a generic rejection email. I asked for feedback but never got a reply. It was a really bad experience and I felt like I wasted my time.
- Write a JavaScript class for event handling.
- Contribute to a part of the company's control panel.
- Develop a to-do application using React.
Box Frontend Engineer Interview Questions
Quoted word for word from Box interview reports.
“Write a JavaScript class for event handling.”
Read reports →“Can you build an EventEmitter from scratch?”
Read reports →“Implement a simple component.”
Read reports →“Could you explain what happens when you type a website address into your browser?”
Read reports →“Can you write an event handler in JavaScript?”
Read report →“Can you code using the reduce function and objects?”
Read report →“Can you build a Checklist component?”
Read report →“How would you design the component layout for a React application?”
Read report →“Can you complete this React live-coding exercise?”
Read report →Formats, difficulty and experience
Across all 14 Box interview reports.