# Software Engineer II
**Role:** Software Engineer · **Level:** L5
**Company:** [Box](https://scaleengineer.com/companies/box)
**Difficulty:** Medium to Hard
**Salary:** US$130000 - US$175000
**Experience:** 4 - 8
**Timeline:** ~14 days
The interview process for a Software Engineer II (L5) at Box is designed to assess a candidate's technical proficiency, problem-solving abilities, system design skills, and cultural fit. The process typically involves multiple rounds, including technical interviews, a system design interview, and a behavioral/managerial interview.
Canonical: https://scaleengineer.com/interviews/box/l5-software-engineer
---
## Overall evaluation

- Technical Skills
- Behavioral and Cultural Fit

## Questions asked

- Given an array of integers, find the contiguous subarray with the largest sum.
- Design a URL shortening service like bit.ly.
- Describe a time you disagreed with a teammate and how you resolved it.
- How would you design a system to handle real-time notifications for a social media platform?
- What are the trade-offs between using a relational database and a NoSQL database?
- Explain the concept of eventual consistency.
- Tell me about a project you are particularly proud of and why.
- How do you approach testing your code?
- What are the principles of RESTful API design?
- Describe a situation where you had to deal with ambiguity or incomplete information.

## Preparation tips

### lists

- Review fundamental data structures and algorithms.
- Practice coding problems on platforms like LeetCode, HackerRank, or Coderbyte.
- Study system design concepts, including scalability, availability, and distributed systems.
- Prepare to discuss your past projects in detail, focusing on your contributions and the impact.
- Research Box's products, culture, and recent news.
- Understand the STAR method (Situation, Task, Action, Result) for behavioral questions.
- Prepare thoughtful questions to ask the interviewer.

### studyPlan

- {"title":"Data Structures and Algorithms","longDescription":"Weeks 1-2: Focus on core data structures (arrays, linked lists, trees, graphs, hash maps) and algorithms (sorting, searching, dynamic programming, graph traversal). Practice implementing these in your preferred language and analyze their time and space complexity.","shortDescription":"Weeks 1-2: Data Structures & Algorithms fundamentals. Practice coding."}
- {"title":"System Design","longDescription":"Weeks 3-4: Dive into system design principles. Cover topics like API design, database choices (SQL vs. NoSQL), caching strategies, load balancing, message queues, and microservices architecture. Study common system design interview questions and practice designing systems.","shortDescription":"Weeks 3-4: System Design principles. Practice designing systems."}
- {"title":"Behavioral Preparation","longDescription":"Week 5: Prepare for behavioral questions. Reflect on your past experiences and identify examples that demonstrate key competencies like problem-solving, teamwork, leadership, and adaptability. Use the STAR method to structure your answers.","shortDescription":"Week 5: Behavioral questions preparation. Use STAR method."}
- {"title":"Company Research and Final Review","longDescription":"Week 6: Research Box thoroughly. Understand their business, products, values, and recent developments. Prepare specific questions about the role, the team, and the company culture. Review your resume and be ready to discuss any aspect of it.","shortDescription":"Week 6: Research Box. Prepare questions. Review resume."}

## Location differences

- {"location":"Remote/Hybrid","differences":{"tips":["Familiarize yourself with the specific cloud provider most relevant to the role (e.g., AWS for many Box roles).","Be prepared to discuss your experience with containerization (Docker, Kubernetes).","Highlight any experience with infrastructure as code (Terraform, CloudFormation).","Showcase your ability to collaborate effectively in a remote or hybrid environment."],"interviewFocus":["Emphasis on practical application of distributed systems knowledge.","Understanding of cloud-native architectures (AWS, Azure, GCP).","Experience with CI/CD pipelines and DevOps practices.","Strong communication skills for explaining technical concepts to a diverse audience."],"commonQuestions":["Discuss a challenging technical problem you solved at your previous company.","How do you approach debugging a complex distributed system?","Describe a time you had to mentor a junior engineer.","What are your thoughts on the current state of cloud computing?","How do you stay updated with new technologies and best practices?"]}}
- {"location":"On-site (e.g., Redwood City, CA)","differences":{"tips":["Deep dive into system design principles and common patterns.","Practice designing systems for high availability and fault tolerance.","Be ready to discuss your experience with specific databases and caching strategies.","Prepare examples that showcase your impact and leadership."],"interviewFocus":["Strong emphasis on system design and scalability.","Ability to articulate trade-offs in architectural decisions.","Experience with large-scale data processing or storage.","Demonstrated leadership potential and ability to drive technical initiatives."],"commonQuestions":["Describe a time you had to influence a team to adopt a new technology.","How do you handle disagreements within a team regarding technical direction?","Walk me through a project where you had significant ownership and impact.","What are the key considerations when designing a scalable API?","How do you ensure the quality and reliability of your code?"]}}

## Round 1: Data Structures and Algorithms
**Type:** Technical Phone Screen / Coding Interview · **Difficulty:** Medium · **Duration:** 45 min
Assess fundamental coding skills and problem-solving abilities.
This round focuses on your fundamental coding skills. You will be asked to solve one or two algorithmic problems, typically involving data structures like arrays, linked lists, trees, or hash maps. The interviewer will assess your ability to write clean, efficient, and correct code, as well as your approach to problem-solving and your communication skills.
**Interviewers look for:** Ability to translate a problem into code.; Efficiency of the solution.; Clarity and correctness of the code.; Ability to articulate the solution and its trade-offs.
**Evaluation criteria:** Coding proficiency; Problem-solving approach; Understanding of data structures and algorithms; Communication of thought process
**Common rejection reasons:** Inability to write clean, working code.; Poor understanding of fundamental algorithms and data structures.; Difficulty in explaining thought process.; Not meeting the expected time/space complexity requirements.
## Questions

- Given a binary tree, invert the tree.
- Find the kth largest element in an unsorted array.
- Implement a function to check if a string is a palindrome.

## Preparation tips

- Practice coding problems regularly.
- Focus on understanding the time and space complexity of your solutions.
- Be prepared to explain your thought process step-by-step.
- Write code that is readable and well-commented.

## Round 2: System Design
**Type:** System Design Interview · **Difficulty:** Hard · **Duration:** 60 min
Assess ability to design scalable and reliable software systems.
This round evaluates your ability to design scalable, reliable, and maintainable software systems. You'll be presented with a high-level problem (e.g., design Twitter's feed, design a URL shortener) and expected to discuss various aspects of the system, including data models, APIs, scalability considerations, and potential trade-offs. This is a crucial round for L5+ roles.
**Interviewers look for:** Ability to design complex systems from scratch.; Understanding of distributed systems, databases, caching, and messaging.; Ability to identify and mitigate potential bottlenecks and failure points.; Clear communication of design choices and rationale.
**Evaluation criteria:** System design principles; Scalability and performance; Reliability and fault tolerance; Trade-off analysis; Clarity of design and communication
**Common rejection reasons:** Lack of understanding of distributed systems concepts.; Inability to design scalable and reliable systems.; Poor consideration of trade-offs.; Not addressing potential failure points.
## Questions

- Design a system to count unique visitors to a website in real-time.
- Design a distributed key-value store.
- Design the backend for a ride-sharing service like Uber.

## Preparation tips

- Study common system design patterns and architectures.
- Understand concepts like load balancing, caching, database sharding, and message queues.
- Practice designing systems for scale and availability.
- Be prepared to discuss trade-offs between different design choices.

## Round 3: Behavioral and Managerial Fit
**Type:** Behavioral / Managerial Interview · **Difficulty:** Medium · **Duration:** 45 min
Assess behavioral competencies, cultural fit, and motivation.
This round focuses on your behavioral aspects and how you fit within the team and company culture. You'll be asked questions about your past experiences, how you handle specific situations (e.g., conflict, failure, success), your motivations, and your career aspirations. The interviewer aims to understand your working style, collaboration skills, and overall fit.
**Interviewers look for:** Evidence of collaboration and teamwork.; Ability to handle conflict and challenges constructively.; Ownership and accountability for work.; Alignment with Box's values (e.g., customer focus, innovation, collaboration).; Enthusiasm for the role and company.
**Evaluation criteria:** Behavioral competencies (teamwork, leadership, problem-solving); Communication skills; Cultural fit; Motivation and career goals; Past experiences and impact
**Common rejection reasons:** Poor communication skills.; Lack of self-awareness.; Inability to provide specific examples.; Not aligning with company values or team dynamics.; Negative attitude or lack of enthusiasm.
## Questions

- Tell me about a time you failed. What did you learn from it?
- Describe a situation where you had to work with a difficult colleague.
- Why are you interested in working at Box?
- How do you prioritize your work when you have multiple competing deadlines?

## Preparation tips

- Prepare examples using the STAR method.
- Reflect on your strengths and weaknesses.
- Understand Box's company values and culture.
- Be ready to discuss your career goals and why you're interested in this role.
- Show enthusiasm and genuine interest.