I applied online. The process took 8 weeks.
The application process for the position of Data Engineer is divided into three stages:
After I applied for a position as a Data Engineer in mid-January, 7 weeks passed before the first interview.
In the first (and for me last) interview, I was told a little about the position and given ample opportunity to ask questions. This was followed by a part with technical questions. After a few simple SQL questions, the focus was on detailed knowledge of database systems. The questions were technically challenging. Something I definitely didn't expect in a first interview.
I would have liked more communication and information in advance, as the questions would have been easy to answer. The interviewer recommended the book "Designing Data-Intensive Applications: The Big Ideas Behind Reliable, Scalable, and Maintainable Systems". I can now pass this advice on to future applicants: Get the book and read it in advance.
At the end, I was told that I would receive an answer the same week. After a week, I then wrote an e-mail myself and enquired about the status of my application, after which I received a rejection.
Overall, the company still seems interesting to me. However, the application process is very slow and the communication in the process is really bad. The technical system on the other hand, as it was explained to me, sounds really interesting and might be worth to have a look at.
In summary: Try it out. It might be worth it.
What methods are there for deleting data in a database?
What is the difference between row-based and column-based database systems?
Why is it (in an OLAP setting) better to have column-based systems?
The following metrics were computed from 1 interview experience for the DeepL Data Engineer role.
DeepL's interview process for their Data Engineer roles is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for DeepL's Data Engineer interview process.