Box · Primly Community

Box behavioral interview questions and values, what actually gets asked

market_realist · 4 replies

Been on both sides of the Box behavioral round. I interviewed there a couple years back and more recently I've talked to two people who went through the loop in early 2026. Here's what I've pieced together.

Box leans heavily on their stated values: Diversity and Inclusion, Result Orientation, Integrity, and a focus on customer and community. The acronym doesn't spell anything pretty but the behavioral questions map to these pretty directly.

Common question themes I've heard about: Tell me about a time you disagreed with a decision and what you did about it. (They want evidence you pushed back constructively, not just went along.) Describe a situation where you had to build alignment across teams without direct authority. Tell me about a project that failed and what you learned. (Classic, but they probe on the "what you did next" part.) How have you handled working with a stakeholder who had very different priorities than your team? Tell me about a time you made a decision with incomplete information.

The behavioral round at Box is typically two interviewers, 45-60 minutes, and you'll probably get 3-5 questions in that time. They do follow-up. If you give a vague answer they will ask you to be more specific about your role, what the outcome was, what you would do differently.

For senior and above: the expectation is scope. Your stories should involve cross-team impact, not just "I fixed a bug." They're looking for evidence of influence beyond your immediate team.

One thing I'll note: the interviewers I've heard about are generally pretty direct. If they want more detail they'll ask. Don't pad answers unnecessarily. Get to the action and result fast, then let them probe.

Happy to answer questions in the thread.

4 replies

nonprofit_nia

This is super helpful especially the note about scope expectations for senior. I'm coming from a smaller org where 'cross-team' meant 3 people. Any advice on how to frame stories that might not sound as large-scale without underselling yourself?

careerveteran

Frame it in terms of proportion. A decision affecting 3 teams at a 20-person company can carry more complexity than the same at a 2,000-person company. Interviewers understand org size context. What they're really evaluating is your reasoning and how you navigated ambiguity, not the headcount of the people impacted.

sam_recovering

Really appreciate the note about not padding. I tend to over-explain and I always wonder if that's hurting me. Good to have it confirmed from someone who's actually sat on the interviewer side.

content_cole

Did you see any questions specifically about the collaboration or sharing aspects of what Box does? Like product-specific context questions, or is it pretty generic behavioral?