The process was long and repetitive, involving multiple rounds (coding, SQL, system design, and several panel discussions). While the recruiter communication was timely and professional, the overall structure felt poorly coordinated. Several interviewers were swapped last-minute, and in most sessions (except one or two), interviewers appeared disinterested or disengaged even before the call began — as if they had already decided the outcome. Many rounds covered the same technical questions repeatedly, rather than exploring depth or role-specific capabilities. By the end, it felt less like an evaluation loop and more like a box-checking exercise, with minimal enthusiasm or ownership from the interview panel.

1) Initial recruiter interview 2) Hiring manager level interview. 3). Interview loop consisting of the following. Technical Systems Design ( 1 on 1): Presented with a Miro board outlining a system design problem I was asked to provide a solution for. This was an iterative process with the requirements changing as they would in the real world. Codility coding assignment. This io open book and includes Python and SQL. You have 72 hours to complete which is plenty of time. 3) Project Retrospective (1 on 1) : discuss prior projects in your career along with a discussion of challenges you faced and how you addressed them. Codility Review (panel): Code review of your Codility assignments with an emphasis on why you chose your solutions and edge conditions in your tests. Building together ( 1 on 1 ): discussion on your cross functional development experience with a focus on challenges you have faced and how you addressed them. Bar Raiser (1 on 1): typical bar raiser interview.