I experienced the interview process as very disrespectful. Only during the feedback conversation after my rejection did I learn that the position had effectively shifted toward a mid‑level role, something that had not been communicated to me beforehand. I was told that this feedback that I am, somehow, actually a mid level developer (despite covering the job of a senior) was told to me “for the sake of my future.” In my view, questioning a candidate’s seniority, especially when they have already held comparable roles for years, is inappropriate. I ultimately accepted a senior position elsewhere with higher compensation and full remote, without mandatory “pillar days” of attendance or whatever you called it. For me personally, remaining unemployed would have been preferable to working here.

The process started with an initial screening round, followed by a technical interview with system design and then a round with deeper technical discussion with code review. The team was professional and direct throughout the process. Communication from HR was clear and timely. The interviews were heavily focused on core Python fundamentals, concurrency concepts, messaging systems (queues, Kafka/RabbitMQ), transactions, and system design. The technical depth expected was quite high, especially around language-level concepts such as context managers, decorators, and concurrency primitives. In the later round, the discussion became very detailed around Python internals and low-level constructs. When I wasn’t able to confidently explain a specific core concept (context managers), the interview was concluded early with the feedback that for a Senior role, strong fluency in core Python fundamentals is expected. What I liked: Interviewers were technically strong and clearly knowledgeable. Questions were practical and relevant to backend engineering. Clear feedback was given directly. What could be improved: The process felt somewhat unforgiving; the interview was ended early based on one foundational gap rather than evaluating overall system design and backend experience. A slightly more holistic evaluation of seniority (architecture, real-world impact, problem-solving) alongside language fundamentals would make the process more balanced.