The communication throughout the process was good until the last interview, but overall, the selection process felt overly long and exhausting. After the initial contact, I was placed into a pipeline of interviews that immediately seemed unusual, with many repetitive steps. The process began when a recruiter reached out to me on LinkedIn, followed by a 30-minute call where we discussed my career. Nothing out of the ordinary so far. After that, I received a link to a challenge on an online platform, which included open-ended and multiple-choice questions about .NET and Flutter. Next, I had another interview with an HR representative, who asked the same questions as the recruiter from the first call. While I had no issue answering them again, it felt redundant. Following the HR conversation, I was required to complete a test and fill out a form providing two reference contacts along with my ID. At this stage of the process, I found this requirement unnecessary, and I was uncomfortable submitting my personal document without having any real connection with the company. However, it was mandatory to proceed. Once past this stage, I had two technical interviews—one for .NET and another for Flutter, given that the position required both technologies. While I felt this was an extra step that could have been streamlined, I had no problem completing them. Both interviewers were very professional, and the discussions were smooth and engaging. I particularly enjoyed this part, even though I once again had to answer repetitive questions. The first half of both interviews covered general programming topics like object orientation, cloud, CI/CD, SOLID principles, and design patterns, while the second half focused specifically on each technology. After completing these technical interviews, I received a message on LinkedIn stating that the Hiring Manager liked my profile and wanted to schedule a 30-minute call to discuss the client. The invitation was titled "Fit Interview," leaving it unclear whether this was a discussion about the client or a cultural fit assessment. To my surprise, it turned out to be neither. During the call, a Flutter developer joined, followed by a .NET developer who was not even listed in the meeting invite. They barely introduced themselves, and the Flutter developer kept his camera off the entire time. The .NET developer spoke very little, and when he did, his English was difficult to understand. Eventually, he mentioned that they would ask a few questions to validate some points, and then he asked me about the four pillars of object orientation. At that moment, I felt frustrated—this was my third technical interview, and I was once again being asked a question I had already answered in the online test, the .NET interview, and the Flutter interview. Realizing this, I started to answer but quickly found myself too frustrated to continue. Instead, I paused and asked, "Wait, is this another technical interview?" They confirmed that it was. I then expressed that I didn’t see the purpose of repeating the same process yet again, apologized, and left the call. Overall, the process felt overly complex, unclear, and lacked objectivity. It gave me the impression that the company struggled to define whether a candidate was qualified. Given my time constraints, I decided it was not worth continuously proving my abilities, especially without clarity on how many more validation steps might follow.