Katkat

Company

Box interview questions

9 practice questions in the style of Box's interviews, covering Coding & Algorithms, System Design.

Questions9

1 easy6 medium2 hard

Your progress0/9

Box interview questions by the numbers

Last updated

Katkat has 9 Box interview questions. The largest topics are Coding & Algorithms (67%) and System Design (33%). By difficulty: 11% easy, 67% medium and 22% hard. The most common round is Onsite (100%).

Topics

Difficulty

  • Easy11% · 1
  • Medium67% · 6
  • Hard22% · 2

Interview rounds

  • Onsite100% · 9

Roles

  • Software Engineer100% · 9

Showing 1–9 of 9 results

  • Compute Top-K word frequencies under a path evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    BoxSoftware EngineerCoding & AlgorithmsOnsite
  • Design out-of-order windowed stream processor evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    BoxSoftware EngineerCoding & AlgorithmsOnsite
  • Diagnose failures via SSH and large logs evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    BoxSoftware EngineerSystem DesignOnsite
  • Explain and diagram your past system architecture evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    BoxSoftware EngineerSystem DesignOnsite
  • This question evaluates a candidate's understanding of bitwise operations and low-level integer manipulation, along with the ability to reason about the time and space complexity of bit-level operations.

    BoxSoftware EngineerCoding & AlgorithmsOnsite
  • Identify and fix deadlock in locked code evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    BoxSoftware EngineerSystem DesignOnsite
  • This question evaluates understanding of rate-limiting algorithms, time-based state management, and concurrent programming concepts, including synchronization and test design for boundary and timing behaviors.

    BoxSoftware EngineerCoding & AlgorithmsOnsite
  • Implement a leaky-bucket rate limiter evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    BoxSoftware EngineerCoding & AlgorithmsOnsite
  • This interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Solve classic troubleshooting & algorithm tasks states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    BoxSoftware EngineerCoding & AlgorithmsOnsite

Box interview experiences

All 9 →
  • Box Account Executive final presentation processBox · Account Executive · HR Screen · May 2026

    I interviewed for the Account Executive role at Box and went through a fairly standard process over a few rounds. The difficulty felt moderate, although the experience varied between feeling supported and wanting more clarity. The process included a recruiter screen about my background and fit for the role. There was also a virtual manager or hiring manager interview. In some accounts, that conve…

  • Rejected

    The process started out promising and turned into a long endurance test. I went through several rounds with a professional, easy-to-talk-to interview team. Around the middle of the process, I was told that I had cleared everything. The hiring timeline kept stretching after that. I then entered a "cooling-off" period of about four weeks with no communication. Just when I thought the process was ov…

  • Box Software Engineer interview with a two-hour technical screen and LLD roundBox · Software Engineer · Technical Screen · May 2026
    Rejected

    My Box Software Engineer interview felt like a classic LeetCode-style process, with more emphasis on data structures than algorithms. The first technical screen lasted about two hours. The interviewer joined at the beginning and again at the end just to discuss the results. The next coding and DSA round took about an hour, with the interviewer on the call the entire time. After that, there was a…

  • Box Frontend Engineer interview: unclear final coding feedbackBox · Frontend Engineer · Technical Screen · Apr 2026

    The interviews were technically focused, but the final coding conversations soured the process for me. After the earlier rounds went smoothly, I reached a final coding interview where the interviewer couldn’t explain the questions or feedback clearly. It was hard to stay focused on implementing the solution because I kept feeling like the target was moving while I worked. The feedback afterward m…

  • The process had a disappointing start. The first round was a conversation with a manager, but the interviewer was so quiet that it didn't feel like a dialogue. I didn't get much chance to explain my experience before the call moved on. From my perspective, it wasn't a serious evaluation of fit or skills. I felt as though I wasn't allowed to contribute, and I didn't move forward afterward. What I…

More companies