The interview was conducted in an online face-to-face format with the recruiter and consisted of two main sections.
In the first section, I was given around four coding-based questions where I had to analyze code snippets, predict the output, and identify errors.
In the second section, there was a live coding round where I was asked to debug code in real time. I explained my approach while identifying and fixing the issues under the recruiter’s observation.
Altre recensioni di colloqui per Python Developer presso Citi
Ho presentato la mia candidatura tramite un'agenzia di reclutamento personale. La procedura ha richiesto una settimana. Ho sostenuto un colloquio presso Citi (Toronto, ON) nel mese di apr 2025
Colloquio
A team of 4 people joined. Each one asked different questions, I don't understand why they ask questions like, why q is prounounced as queue. Absolutely ridiculous, I'd never join such team. I was literally explaining the concepts I used to update software and they asked what concepts I used. Either they don't understand basic english or they just took the interview to make it 'yet another rejection". Not to be personal but asians have the worst way of interviewing, and the accent was extremely difficult to understand and the questions are . For Eg, when you use QT framework to develop an application, they asked how does front end communicate with backend? What are you supposed to say for that? Newtons third law around a tree? They have absolutely no idea on how to assess a candidate. Too many questions and they barely want to listen to the candidate's responses. A new question even before I could answer my current one. Impatient. It was so excruciating to convince them of my experience that the names of these candidates will be in my mind even in my afterlife.
Domande di colloquio [3]
Domanda 1
What version of airflow you were using? How do you monkeypatch? What kind of data bases did you work on? How did you implement CI/CD pipelines?
