The process consists of four stages:
An interview with human resources, who are usually very pleasant.
A technical test that you do at home. This test involves creating a project from scratch where you must implement concurrency with the Sequelize ORM and make database queries to pay salaries and retrieve information. This test is conducted online.
The technical test has an average difficulty. However, the technician who interviews you afterward usually does not review it; a separate department handles that. Consequently, you often end up in an interview with a technician who needs to re-evaluate your skills based on information they haven't seen in your code (because they never saw your code).
They literally don't care what you did on the technical test. In this interview, they are only looking for people who are genuinely skilled in database modeling and can solve database challenges by sharing your screen live and creating live tables.
In the third stage, I had an interview for an AWS and Node.js Backend Developer role. After completing the challenge, I was asked to show my screen and create tables from a statement.
They take it in parts, asking you to make tables and show how you would relate one table to another, demonstrating relationships like one-to-one, one-to-many, etc.
After progressing through several exercises, they asked me:
If you had a table with departments and a table with employees, how would you safely migrate a specific field? The difficulty of these questions increases.
The point is that if you don't have experience discussing live database modeling and thinking quickly about relationships and entities (which almost no one does, and it's nonsensical to ask this for a Node.js developer position with AWS requirements), then this interview will be a total waste of time.
During the question round, I inquired about my technical test and their thoughts on it. They stated they hadn't even looked at it, meaning I invested significant effort into producing something excellent for people who didn't truly value it. Additionally, I prepared some code to discuss the latest implementations in AWS, NLP, and Kafka, and asked if we could talk about those topics.
They responded very rudely: "What does that have to do with this interview?"
My summary of their attitude is that they approach the interview with a bad attitude, are ill-tempered, distrustful, and possess very little patience.
This interview, far from being comfortable, was stressful, rude, poorly planned, and a waste of time.
My summary is that this company has a very, very incompetent technical evaluation process. It's a meat grinder that interviews for the sake of interviewing a lot of people, just to see if, by some chance, a backend developer also knows how to be a DBA.
They are neither pleasant nor professional; they are cold and very unprofessional people.
I sincerely regret not realizing that this interview was a total waste of time, during which they would make me waste weeks of my free time developing a test that no one was ever going to look at.
Don't waste a single second of your time with these people. This is a company that is stuck in the past.
Tell me about your current project, please. Do it quickly because we only have 4 minutes.
The following metrics were computed from 1 interview experience for the Deel Senior Backend Engineer (Node Js) role in Spain.
Deel's interview process for their Senior Backend Engineer (Node Js) roles in Spain is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Deel's Senior Backend Engineer (Node Js) interview process in Spain.