
Deliverect Interview Questions
& Process
Real candidates share what happened, how many rounds they had,
and how the experience turned out.
Based on 111 interview experiences · FREE TO READ
Which role are you interviewing for?
30 roles · 111 reportsCandidate interview experiences
First-hand accounts from people who interviewed at Deliverect.
Product Manager
Recruiter call, then a long wait without communication, followed by an interview with the Design lead, another long wait without communication, then a task, another long wait without communication, and finally a task presentation. They ghosted me between each step for like 3 weeks, without any transparency or communicating timelines. I got my rejection update with a template email that could be used in the resume screening step. When a candidate invests on a role and goes through the process to the very last step, normal companies try to provide candidate-specific feedback. This takes only 15 mins, but shows how the company cares about people, but this company clearly doesn't! I strongly recommend you to stay away from this company as far as you can.
- What metrics do you use to define features?
Data Engineer
I applied online via their website. I made sure my CV was tailored to the job description and also wrote a genuine, handwritten cover letter, which I think was really important. I had one online interview in English with the Head of Data and a Data Engineer. It lasted about 30 minutes. They asked about my background, motivation, use of AI in projects, cloud awareness, and why one cloud provider might be preferred over another. They also asked about my use of SQL and Python. The main takeaway is that you should understand the reasoning behind your choices and show you're motivated and eager to join and learn. The interviewers were really nice.
- Can you explain the scenarios where SQL is appropriate versus when Python should be used?
Partner Manager
So I went through 3 rounds of interviews. First, a quick call to screen me. Then, a 30-min chat about partnerships, keeping clients, and preventing churn. The final stage was a presentation about Deliverect partnerships and what a typical day looks like. The very last call was kinda funny, with seven people from different teams asking random stuff like "If you were in a band, who would you be?" It felt totally unprofessional and not really aligned with the job. It's like they're taking advantage of the tough job market to waste people's time. Having seven interviewers for one person shows they're disorganized and not confident. I think I dodged a bullet. Don't bother with this company if they treat the final interview like a group therapy session; it's a joke.
- What makes a partnership successful?
- Which band member would you be if you were in a band?
Data Analyst
So for this Financial Data Analyst internship, it was pretty intense and tough. It had 5 stages. First, HR called to see if I fit the company culture, asking about my studies, why I wanted the internship, and my future plans. It was a basic intro chat. Then came the technical rounds. Tech round 1 was all about finance stuff, like basic finance knowledge, reading data, and solving finance problems. Tech round 2 was more intense with complex finance cases and data analysis, needing me to dig into numbers and give insights. Tech round 3 was about my core data skills – like playing with data, stats, and making charts. They wanted to see if I knew my tools and could explain data well. Last up was the people skills interview, checking how I work with others, talk clearly, and sort out disagreements. It was important to see if I'd be a good team player.
- Could you tell me a bit about yourself?
- What motivated you to apply for this particular internship?
- What are your aspirations for your career moving forward?
Deliverect Interview Questions
Quoted word for word from Deliverect interview reports.
“Which band member would you be if you were in a band?”
Read reports →“Could you tell me when you would choose to use a PATCH request instead of a PUT request?”
Read reports →“Can you explain scenarios where RESTful architecture principles might not be suitable?”
Read reports →“Can you explain the scenarios where SQL is appropriate versus when Python should be used?”
Read reports →“What measures could be implemented to avoid such an issue in the future?”
Read report →“How would you handle a situation where a customer is angry and refuses to follow troubleshooting steps?”
Read report →“Given a basic database situation, could you write an SQL query?”
Read report →“Can you share a time you felt completely absorbed in an activity, experiencing a 'flow of mind'?”
Read report →“How do you provide training and ongoing support to clients once the system is live?”
Read report →Formats, difficulty and experience
Across all 111 Deliverect interview reports.