Depop Interview Questions
& Process

So I interviewed with Depop for a backend engineering gig and made it to the pair-programming stage. The task was to link buyers with sellers using their inventory. It was a pretty standard problem, but the interview wasn't as collaborative as I expected. The interviewers were pretty quiet, and we didn't really talk much about design decisions. I got feedback later saying I didn't break down the problem well, specifically because I didn't focus on the algorithm before doing some basic modeling. They didn't mention this preference during the interview, though. It would be better if they communicated that upfront instead of after, so it feels more like actual pair programming and less like a silent test with secret rules.

It was a few stages. First, I had a quick call with recruitment/HR, they asked a ton of questions fast. Then, I chatted with the hiring manager on video, which was more chill and about my background and why I wanted the job. After that, I got a detailed brief for a data analysis and presentation task. For the next interview, I did an hour-long video call where I presented my slides and answered questions from the hiring manager and another team member. They were nice and focused on my presentation. The last step was a 30-minute video call with the marketing director. It was supposed to be a casual chat about culture fit, but it felt like a rapid-fire Q&A session, similar to the first call, and didn't leave a great impression. Communication was okay until after the final interview, then it took a few weeks to hear back. Overall, it was a pretty good experience with friendly interviewers, and they even sent out anonymous surveys for feedback after each stage.

The interview process was pretty smooth. I had an initial call with an external recruiter about their Product design role, followed by a second 45-minute call with two designers at Depop, where I discussed my experience and presented 2 design case studies, followed by questions. I thought the interview went well, but unfortunately, I was told it was a no, even though they appreciated my strong visual and interaction design skills and execution. The feedback was that I was short on demonstrating strategic-level thinking.

The recruiting team talks a lot about collaboration and thinking out loud. But the actual interview is the complete opposite. My System Design session was a silent interrogation. The interviewer barely spoke and refused to engage in any real discussion. They just sat there taking notes, waiting for me to match a rigid script. The feedback proved exactly what is wrong with this culture. They admitted that I solved the complex architectural challenges perfectly. However, they rejected me because my specific choices on small operational details didn't match the interviewer's personal preference. This is what happens when you let mid-level engineers interview Senior talent without proper training. They mistake their own subjective preferences for technical facts. They don't know how to evaluate a nuanced trade-off, so they just reject anyone who doesn't give the exact 'safe' answer on their checklist. If you are a Senior Engineer who expects an intelligent conversation, look elsewhere. You will not be judged on your ability to solve problems. You will be judged on how well you can guess the hidden checklist of a silent interviewer.