Deliverr Backend Engineer Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 10 interview experiences · FREE TO READ
Candidate interview experiences
First-hand accounts from people who interviewed at Deliverr.
Deliverr
Senior Backend Developer
Senior Average Positive experience Accept offer 7 rounds
Interview process
Take home Recruiter call Technical screen Onsite Offer
Interview formats
Coding Technical Behavioral System Design
First I got an online assessment on a third-party platform, which was a cool change because it was more of a hands-on task instead of just LeetCode practice. For a senior backend engineer, it was pretty doable. It covered some coding, database stuff, and troubleshooting. Then I had a chat with HR, followed by 5 interviews during the virtual on-site: one behavioral, one deep dive into a past project, one design interview, and two coding interviews. The coding questions were about medium LeetCode difficulty. The whole process felt similar to other big tech companies, though maybe not as intense as some. I heard back the day after the interviews about an offer. My recruiter was great, kept in touch, and answered everything. Even after the offer, they arranged calls to clear up my remaining questions. I had another offer but was really impressed with the whole Deliverr experience from beginning to end, including the final offer.
Confirmed questions1 question
- I was surprised by how much database modeling was a focus.
Deliverr
Senior Backend Developer
Senior Average Negative experience No offer 6 rounds
Interview process
Technical screen Onsite
Interview formats
Coding Technical
There was a programming exercise for about 1.5 hours which was pretty boring. After that, they set up 5 separate interviews, each lasting an hour. These could be done all in one day or spread across two days. You'd meet different employees in each session, and every interview involved small exercises or questions.
Confirmed questions1 question
- What makes you want to work at Deliverr?
Deliverr
Backend Engineer
Entry Average Positive experience Accept offer 5 rounds
Interview process
Recruiter call Technical screen Onsite Offer
Interview formats
Coding Technical Behavioral
Because it was during COVID-19, the first step was a phone call, then a technical interview. After that, I had a virtual onsite with 3 technical interviews and one behavioral interview. Everyone I met was really nice and seemed genuinely enthusiastic about the company. The technical interviewers were helpful when I had questions. Since I was fresh out of college and it was a busy hiring period, even though the job was for backend, they offered me a support engineer role instead. They did say I could move to backend after about a year though.
Confirmed questions4 questions
- Mostly standard coding questions covering data structures and algorithms.
- My coding questions coincidentally involved a lot of 2D arrays.
- One interview specifically focused on databases.
Deliverr Backend Engineer Interview Questions
Quoted word for word from Deliverr interview reports.
“Given meetings as a 2D array, determine if any meetings conflict.”
Read reports →“What are some average medium difficulty toy problems?”
Read reports →“For an ordering system sending line items to a warehouse for distribution, how would you model the database?”
Read reports →“Could you build a tic tac toe implementation?”
Read reports →“Can you tell me about your decision to study computer science and your background in the subject?”
Read report →“What led you to pursue computer science, and what's your experience in that field?”
Read report →“Are you familiar with [specific technical topic relevant to backend engineering]?”
Read report →Formats, difficulty and experience
Across all 10 Deliverr interview reports.