Dropbox Product Engineer Interview Guide

tl;dr

With more than 700 million registered users across the world, Dropbox is one of the most popular file-hosting services around. In addition to their well-known cloud storage offerings, Dropbox also administers several other SaaS products. Their premium “Dropbox Business” plans allow distributed teams to access shared folders and collaborate via an intuitive “Dropbox Spaces” interface. Other Dropbox products include HelloSign, which handles digital authorization for contracts and agreements, and DocSend, which provides users with useful control features and analytics for the files they share with others.

Dropbox’s user base is scattered across more than 18 countries, with a significant volume of data that Dropbox manages. Over 90% of this data is maintained on Dropbox’s distributed storage infrastructure. The company also deploys regional accelerators in North America, Europe, Asia, and Australia to lower latency and boost reliability to the metropolitan areas where most of its users reside.

Compensation

Compensation at Dropbox is scaled to, among other things, the metro area where an employee lives and its regional cost of living. The average total compensation across software engineering levels at Dropbox are:

• IC1 (Software Engineer, entry-level): $174k
• IC2: $246k
• IC3: $346k
• IC4: $457k
• IC5 (Staff Software Engineer): $638k

What does a Dropbox Product Engineer do?

Product engineers at Dropbox are responsible for building, upgrading, and maintaining their suite of file-sharing and collaboration tools. Full-stack engineers are recommended to have experience with:

• Python, JavaScript, HTML/CSS
• Tools, such as, React, Angular, and Node.js
• Database systems, such as MySQL, PostgreSQL, and MongoDB.

Many dedicated backend roles emphasize Go, NoSQL databases, and distributed systems.

Dropbox product engineers work on cross-functional teams with product managers, designers, and other stakeholders. Furthermore, seniority and leveling at Dropbox are strongly influenced by how willing and effective you are at training your fellow employees. As such, your ability to collaborate with others and provide mentorship is essential.

Archetypes to consider

As engineers rise through the ranks at Dropbox, they tend to gravitate toward one of several “Archetypes”:

• Tech Leads guide the approach and execution of their team, in partnership with one or more engineering managers.
• Architects take ownership of the direction, quality, and approach within a critical area. They combine in-depth knowledge of technical constraints, user needs, and organization-level leadership.
• Solvers pounce on arbitrarily complex problems and find a path forward. Some focus on a specific area for long periods. Others bounce from hotspot to hotspot, as needed.

Because reliability and 24-hour uptime are so essential to Dropbox’s services, many product teams have on-call rotation assignments. Everyone on the team is responsible for answering calls and solving product issues when their rotation period rolls around, so you should be prepared to set aside the occasional late night or early morning for emergency troubleshooting and fixing software bugs.

Demonstrate impact

Dropbox wants to see that you’re an engineer who’ll make a profound business impact, and each step of their interview process—from the initial very first recruiter’s call—is tailored to expose that. Your business impact can manifest as product expertise, domain expertise, and innovation; the raw technical acumen of a skilled engineer. It can also be visible as technical leadership, project leadership, and mentorship, acting as a role model for best practices and setting a strong foundation for others to build on. Talk about your impact in the same framework that Dropbox uses:

• Consistency—Your work delivers results, over and over again.
• Velocity—You can produce good outcomes quickly.
• Accountability—You take ownership of the results you're accountable for, within your scope of work.

Each additional SWE level beyond IC1 comes with a greater scope of impact: if an entry-level Dropbox engineer is responsible for the outcome of a task, the rung above that is responsible for a project; above that is responsibility for the team assigned to that project. Demonstrating that you can handle a greater scope of work in your interview is the greatest determinant of which level you’ll be offered when you start.

Before you apply

• Read the Dropbox Engineering Career Framework. It’s open source, and clearly lays out the responsibilities and promotional paths for Dropbox software engineers (SWEs) at all levels.
• Familiarize yourself with the Dropbox Values and how to talk about your business impact. “Impact” is the primary metric that Dropbox uses to select who to hire and promote.
• Practice for behavioral interviews. Being able to articulate your experience and culture fit are strong, key factors for getting an offer at Dropbox.
• Coding questions are weighted heavily for junior applicants, while the system design interview is weighted heavily for seniors. Take some time to prepare for these areas.

Interview process

The process to interview at Dropbox is particularly standardized, including the scripts and prompts that their interviewers are trained to follow. This is partly due to their commitments to equity and inclusion; presenting each candidate with similar challenges and the same treatment ensures that each candidate is measured to the same benchmark.

Applicants to Dropbox complete these interview stages before they are hired:

• A recruiter screen, to check for general fit and that you meet the minimum requirements for the role
• A technical screen conducted over CodeSignal, made of domain-specific questions
• A final interview loop of 4–6 rounds, which can be held on-site or remotely

Final hiring decisions are made by a hiring committee, with the candidate’s name and gender redacted from their application and interview results.

Recruiter screen

At many tech companies, the initial recruiter call is a routine check that a candidate is (at least) minimally qualified and interested in the role. Dropbox takes a proactive approach to screening candidates from the start. About 20% of applicants are invited to the next step in the process. However, the questions you’ll get are fairly standard for this stage of the process.

Be prepared to talk about your background, previous accomplishments, what motivates you, and your interest in the role. You should weave your answers around the central thread of how you’re able to produce impact. An ideal candidate takes initiative, strives to improve themselves, and takes feedback well.

Sample questions include:

• Why do you want to work at Dropbox?
• What are some of your notable projects?
• What do you do in your current role?
• Why are you looking for a new job?
• What are you looking for in your next role?
• What drives you? What are you passionate about?
• What are your salary and equity expectations?

Technical screen

The technical screen is administered through CodeSignal and lasts about 75–90 minutes. Expect the challenge to be a long coding problem, broken into several smaller subtasks. Dropbox tries to pick challenges that resemble a typical problem you might encounter on the job.

You’ll need to perform all of your code entry, testing, debugging, and so forth through the CodeSignal interface, instead of a separate IDE, so you may be faced with a different workflow than you’re used to. The tech screen is not, by default, usually overseen by a proctor, but Dropbox will provide one if you ask for it—a sign of their commitment to accessibility.

Sample coding problems include:

• Implement a simple, in-memory file sharing system with basic CRUD features.
• Given a specific application, implement an LRU cache for it.
• Program an in-memory database, with four layers of successive requirements.

Final interview loop

The last step of your interview loop is completing a set of 4–6 interview rounds that cover several domains; the more senior the role you’re applying for, the more rounds you’re likely to undergo. This loop includes a set of 2 or 3 technical rounds focused on:

• Coding and debugging
• An “all-around” section focused primarily on behavioral and culture-fit questions
• Speaking with the hiring manager.
• Senior and staff-level roles also include a system design interview round.

All of these interview rounds are scheduled as a “virtual onsite” video call over the course of a few hours.

Coding and debugging rounds

These programming challenges tend to be quite similar in structure to the initial technical screen, except that these will be overseen by a proctor. (They will still be conducted through CodeSignal, whether you take the final interview remotely or not.) Again, the usual structure is a big problem divided into several smaller steps. After implementing the basic functionality, the next steps usually involve an increase in scale or (less commonly) in time- and space-complexity.

A debugging problem, on the other hand, might present you with a flawed codebase and a set of goals it needs to fulfill; for example, “make this buggy UI display X data and achieve Y results”. How you troubleshoot these issues reveals your problem-solving prowess,  your ability to use reference material, and maintain code so that it’s useful for others to work on.

If you’re applying to a junior or mid-level role, it’s extremely important for you to perform well on these rounds—they’re weighted heavily, and this is the best chance for you to showcase your talent.

Dropbox tends to reserve system design interviews for more senior role applications, and while you’ll have plenty of chances to discuss your past experience as an engineer, you may not yet have enough career achievements in your portfolio to sell your technical strengths on them alone.

Sample coding problems include:

• Find and return all duplicate files in a folder, and then rewrite the function to use fewer operations.
• Write a program to allocate and release IDs, and make it more space-efficient, and then make it run faster.
• You’re given a function that fetches the HTML of a webpage, and another that retrieves links from HTML text. Now write a web crawler program that finds the links from all the pages it crawls. Can you make it so that it’s multithreaded?

System design

Dropbox usually only assigns a system design round for roles at senior-level or above, but if you get one, it’s one of the most important considerations for you to get an offer. The more depth of thinking and level of experience you demonstrate here, the more likely you can be tracked to a higher SWE level.

You’ll be given an open-ended prompt related to a Dropbox-relevant product or problem, and ~30 minutes to describe how you’d build a technical solution for it.

A good system design answer starts by thinking through the problem, considering how it fits into Dropbox’s overall goals, and foreseeing the pros and cons of a particular approach. In general, as you lay out your design, you should briefly address the trade-offs you’re making as you go, but stay focused on presenting the overall picture. You can (and should) address the details in more depth afterward, or when the interviewer asks follow-up questions.

Sample task questions might include:

• Design a notification broadcasting system.
• Design a recommender system feature for Dropbox that suggests files to users when they open the app on their phone.
• Design Dropbox.

“All-Around”

The “All-Around” segment is designed to delve into your past experiences and evaluate the skills and mindset you’ll bring to Dropbox. It’s comparable to a behavioral or culture fit interview, where the focus is more on “soft skills”, rather than your raw technical acumen. Still, you should expect to talk about your past projects a lot; for example, why you made the choices you did, how well they worked, and what you learned from it. Preparing a story bank is especially valuable for the “all-around” interview segment at Dropbox.

This round, even more than the rest, is fundamentally about your ability to deliver business impact. Your impact is a compilation of the projects you’ve worked on and the problems they solved. Further to that is your ability to collaborate with your coworkers, and to organize more effective teams and structures in the companies you’ve worked at. Plan ahead for this round by taking account of your previous work and brainstorming ways to connect it to the values articulated in the Dropbox Career Framework.

Dropbox associates each SWE level with a particular scope, and evaluates how an engineer executes within and beyond that scope. If you’re applying to an entry-level position, you probably don’t have a lot of impressive projects to cite in the all-around loop, but an enthusiastic student or hobbyist should still be able to demonstrate what Dropbox expects from an IC1. Demonstrating that you want to learn, improve, and take feedback always works in your favor.

The higher up the ladder you go, the greater the scope you’ll need to handle. This usually means more complex technical problems, organizational structures, and product needs.

Experienced candidates should be able to:

• Explain their decision-making process and defend their choices.
• Ready to foster mentorship and collaboration at Dropbox.

Sample questions include:

• Talk about a notable project you worked on. What was the reach of your impact on this project?`
• What was a time you brought up constructive criticism? How did it go?

Hiring manager round

The last round of Dropbox’s virtual onsite is a meeting with the hiring manager for the role. Compared to the rounds before it, the stakes are somewhat lower; this is primarily an opportunity for the both of you to get to know each other. The hiring manager will ask you about your wants, needs, and expectations as an engineer.

Assuming the rest of the interview has gone well so far, this is unlikely to be a make-or-break moment. If you come across as a desirable candidate otherwise, but this round reveals a mismatch between you and the team you’re applying to, you may well be offered a spot on a different team.

Additional resources

• Read the Dropbox Engineering Career Framework as an essential part of your preparation.
• Take our course on behavioral interviewing. Preparing a story bank is especially valuable for the “all-around” interview segment at Dropbox.
• Read the Dropbox tech blog to see valuable examples of problems you’ll tackle at Dropbox, which can inform your system design approach.
• Practice solving common coding questions.

FAQs

How should I prepare for a Dropbox Product Engineer interview?

• Read the Dropbox Engineering Career Framework and internalize its key concepts, such as impact.
• Practice behavioral interviewing and coding so that you’re prepared for the most important rounds of the interview.

How much do Dropbox Product Engineers earn?

The average total compensation across software engineering levels at Dropbox are:

• IC1 (Software Engineer, entry-level):$174k
• IC2: $246k
• IC3: $346k
• IC4: $457k
• IC5 (Staff Software Engineer): $638k

How long does the Dropbox Product Engineer interview process take?

Dropbox moves fast when it comes to hiring decisions. Most candidates report completing the entire interview process in 3–4 weeks.