The interview process begins with an initial screening call with a recruiter, which includes some technical questions.

This is followed by an extensive coding challenge. You'll need to write SQL, solve a problem in Python, and write a REST API for it. This challenge is not straightforward and is quite time-consuming.

Feedback is really good.

Next, there are two more interviews conducted over video. The first focuses on your technical experience and explores your Python and SQL skills. This interview is quite straightforward.

The second is a system design interview. While this interview format works well, I don't think it's optimally designed to measure your experience. You are tasked with designing a system end-to-end based on a brief. However, at least for me, the brief didn't truly reflect the kind of work I would be doing or have done, so it didn't measure my skill set as effectively as other system design interviews I've encountered. What's the point of working through a system design question if it's not directly relevant to your work?

Furthermore, the interviewer in this session was off-putting and quite hard to understand.

All in all, it's a good interview process with nice and speedy feedback. However, the interview process currently seems designed for more senior individuals. It's also unusual that the role is presented as a data engineer role when you apply for a backend engineer position.

Basic Python stuff, including decorators and generators.