It was two stages of the interview: first one - phone screen with an HR manager - a typical one; second stage - technical interview - one of the worst I was involved in. It looked like the guys had a list of questions with answers, and checked against that list. Most of the questions were quite generic, with various possible answers or solutions, but any alternatives were rejected. You had to guess the correct answer, otherwise - "it's not the answer I expected".

One of the most unpleasant interview experiences I’ve had in recent years. The initial conversation with the recruiter was pleasant and went smoothly. However, the technical interview that followed — a two-hour session with two engineers — felt more like an oral exam with the strictest and most disengaged professor than a professional interview. One of the engineers (Engineer A) was communicative, supportive, and showed genuine interest in my experience and approach. Unfortunately, the other engineer (Engineer B) was the complete opposite: cold, passive-aggressive, and uninterested in learning about my background, projects, or how I approach solving problems. His focus was solely on whether I could recall the exact terminology for specific Python features — particularly around tasks, coroutines, and threads — rather than engaging in a thoughtful technical discussion. Engineer B seemed poorly prepared for the interview. He complained about his internet connection, had issues with his equipment, and kept turning his camera on and off throughout the call, which added to the overall lack of professionalism. The interview began with 20 minutes of repeated questioning about my past project transitions. Despite providing clear and consistent answers, Engineer B was visibly dissatisfied and kept returning to the same topic. At one point, I even heard him mutter “Oh my God” in response to one of my answers — a reaction that struck me as inappropriate and dismissive. It also became apparent that Engineer A and Engineer B were not aligned on how to conduct the interview. They disagreed on certain points during the discussion and at times seemed on the verge of arguing. The whole process felt disorganized and tense from start to finish. When I asked questions about the team, company processes, and current projects, the only answer I received was “It depends on the team.” I was also told that they follow a waterfall-style development process, which was surprising for a tech company. Engineer B mentioned he had been with the company for over five years, which led me to believe that this kind of behavior might be considered acceptable within the broader company culture. Based on this experience, I decided to withdraw from the process.