Depop Software Engineer interview questions & guide 2026

While interview questions can vary based on the specific team and seniority level, the following categories capture the recurring patterns reported by candidates. Use these to understand the scope of the assessment rather than as a definitive list.

Technical & Domain Expertise

These questions assess your foundational knowledge, your ability to handle specific language requirements (such as Python or Scala), and your understanding of core software engineering principles.

• How do you optimize API calls that block for a long time?
• What are the primary strategies for reducing unnecessary database hits?

Preparation at Depop requires a balanced approach. You should be ready to demonstrate deep technical competence while clearly articulating your collaborative style.

Technical Competency – You must be comfortable with both the language you use daily and the willingness to work with others, such as Scala. Interviewers look for clean, testable, and efficient code; always explain your thought process during live coding sessions.

Problem-Solving Approach – When faced with system design or architectural questions, focus on trade-offs. Interviewers want to see how you weigh factors like latency, consistency, and future-proofing rather than just arriving at a "correct" answer.

Communication & Collaboration – Technical skills are only part of the equation. You will be evaluated on your ability to explain complex technical concepts to non-technical stakeholders and your openness to feedback during pair programming exercises.

Cultural Alignment – Depop values authenticity and a passion for their mission. Be prepared to discuss your own career goals and how they align with the company's trajectory, while also demonstrating that you are a supportive team player.

The interview process at Depop is designed to be comprehensive, typically spanning four stages. While it is structured to be thorough, it is also intended to be a two-way street where you get to know the team and the culture as much as they get to know you. You can expect a mix of initial screenings, technical assessments (often involving live coding or pair programming), and discussions focused on architecture or culture.

The process is generally marked by a high level of engagement with team members, allowing you to get a clear picture of your potential colleagues. While the pace can vary, candidates are encouraged to maintain clear communication with their recruiter throughout the stages to stay informed on the timeline.

The visual timeline above illustrates the standard progression from initial contact to final team interviews. Use this to pace your preparation, ensuring you have enough time to brush up on both your core coding skills and your ability to articulate your past projects during the behavioral rounds.

Technical Coding & Pair Programming

This is the core of the technical assessment. You will be expected to write production-quality code under observation, usually with a focus on efficiency and testing.

Be ready to go over:

• Test-Driven Development (TDD) – Writing tests alongside your code is often expected.
• Code Refactoring – Expect to be asked to improve an initial implementation for efficiency or readability.
• Language Nuances – Be ready to discuss the specific behaviors of your primary language (e.g., Python or Scala).

Example scenarios:

• Implementing new endpoints for a REST framework.
• Solving algorithmic challenges while maintaining clean, readable code.

System Design & Architecture

This area evaluates your ability to think about the long-term health of the platform.

Be ready to go over:

• Scalability – How to handle increased traffic and load.
• Microservices – The challenges and benefits of transitioning from a monolith.
• API Design – Best practices for building robust and usable internal/external APIs.

Example scenarios:

• Designing a strategy for splitting a legacy monolith into modular microservices.
• Discussing strategies for database optimization in high-concurrency environments.

As a Software Engineer at Depop, your daily work involves translating product requirements into robust, scalable features. You will spend a significant portion of your time collaborating with product managers and other engineers to define the technical implementation of new functionalities. This includes writing clean, maintainable code, performing thorough code reviews, and ensuring that the services you own are performant and reliable.

Beyond individual coding tasks, you will be expected to contribute to the broader engineering culture. This includes participating in design discussions, advocating for technical improvements, and helping to mentor team members. You will frequently interface with the infrastructure or platform teams to ensure that your code integrates seamlessly into the larger Depop ecosystem.

A strong candidate for this role balances deep technical expertise with the flexibility to adapt to changing project needs.

• Must-have skills: Proficient in at least one modern backend language (e.g., Python), experience with REST APIs, a strong grasp of testing methodologies, and excellent communication skills.
• Nice-to-have skills: Experience with Scala or functional programming, familiarity with microservices architecture, and prior experience in e-commerce or high-traffic consumer platforms.
• Soft skills: A collaborative mindset, ability to navigate ambiguity, and a clear, proactive communication style.

Q: How long does the entire process take? The process typically takes several weeks. While it can feel extended, it is structured to ensure you meet multiple team members, which helps you make an informed decision about your fit.

Q: Is the technical test difficult? Most candidates find the technical sessions accessible if they have a strong grasp of fundamentals. Focus on writing clean, testable code rather than just trying to find the most "clever" solution.

Q: What is the culture like at Depop? The culture is generally described as friendly and collaborative. You will be working with people who are passionate about the product, and you should expect an environment that values open dialogue.

Q: Will I need to learn Scala? If the team is transitioning to Scala, you will be expected to learn it. Be honest about your interest in learning new languages, as this is often a key indicator of a candidate's long-term potential at the company.

• Prioritize Communication: During pair programming, talk through your thought process out loud. Interviewers care as much about how you solve problems as they do about the final code.
• Be Curious: Ask insightful questions about the team's roadmap, the challenges they are facing, and the company's vision. This shows you are engaged and thinking like a future team member.
• Own Your Experience: Be prepared to talk about your past work in detail. Use the STAR method (Situation, Task, Action, Result) to keep your answers structured and impactful.
• Stay Flexible: If you are asked to refactor your code during a test, don't panic. Treat it as a collaboration rather than a critique; show that you are receptive to feedback and quick to adapt.

The Software Engineer position at Depop offers a unique opportunity to shape the technology behind a global fashion marketplace. By focusing on your technical fundamentals, demonstrating a collaborative approach to problem-solving, and showing a genuine passion for the company's mission, you can significantly enhance your candidacy.

Preparation is the most effective tool you have to succeed in this process. You can explore additional interview insights, practice questions, and preparation resources on Dataford to ensure you are fully ready for every stage of the journey. We encourage you to approach your interviews with confidence—your technical skills and unique perspective are exactly what Depop is looking for.

The provided compensation data reflects typical market ranges for this role. Candidates should interpret these figures as a baseline, keeping in mind that total compensation often includes base salary, equity, and benefits, which may vary based on your specific level of experience and the team you join.