Deel Database Administrator DBA interview questions
Updated Apr 24, 2025
based on 2 ratings
Difficulty
Difficult
Experience
Very positive
How others got an interview
100%
Recruiter
Recruiter
Interview search
2 interviews
Deel interviews FAQs
Database Administrator DBA applicants have rated the interview process at Deel with 4 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 100% positive. To compare, the company-average is 60% positive. This is according to Glassdoor user ratings.
Common stages of the interview process at Deel as a Database Administrator DBA according to 1 Glassdoor interviews include:
One on one interview: 50%
Skills test: 50%
Here are the most commonly searched roles for interview reports -
By far, the most thoughtful company I had an interview process with.
Unfortunately , I didn't make it, but they actually took the time to schedule a 15' call with me to give me feedback on the whole process. Nobody does that, and for that, I am very grateful to this company.
The first interview was with the recruiter, lasted 30', and included a few technical questions.
The second interview was technical and lasted one hour. This was a conversation with a technical leader asking me questions.
Interview questions [3]
Question 1
How do you approach sudden slowness on a database system?
I applied through a recruiter. The process took 4 days. I interviewed at Deel (Buenos Aires) in Jul 2023
Interview
I had remote interviews (LATAM) directly with the company's recruiter. There were four stages in total: a 15-minute welcome call, a take-home assignment (given a few days to complete, but I finished it in a couple of hours), a one-hour technical interview, and a half-hour cultural fit interview. The take-home assignment was typical and not too challenging, involving database structure, reading statistics, and a few backend questions. The technical interview left a very positive impression. The Technical Director was genuinely knowledgeable and impressive. It was one of those rare instances where I felt eager to work not just on the project but under the guidance of that specific person. The questions were of high quality, and the discussions were engaging. After this round, I received "very positive feedback." However, the behavioral interview didn't go as well for me. Standard questions for such interviews were asked, but I sensed some stiffness from the CTO's side. He cut me off during my last answers, saying, "That's enough; we're running out of time, and I need to go to another meeting." Perhaps I should have chosen a different day of the week (it was a Friday) for this interview. In any case, I gained valuable experience, especially from the technical interview. It was my first experience with a behavioral interview, and it made me aware of my weaknesses and what I need to work on. I will be actively monitoring job listings to better prepare myself if a similar opportunity arises again.
Interview questions [1]
Question 1
Fixing performance issues and implementing features, system design, reading query plan and statistics