I applied through a recruiter. The process took 2 weeks. I interviewed at Citi (Dublin, Dublin) in May 2020
Interview
I was offered to apply through a 3rd party recruiter.
I got a phone interview with two engineers from Citi. They had very thick accent, making their questions hard to understand, I had to ask them to repeat several time. It was also quickly clear they had little to no experience in interviewing, I guess their manager grabbed them and told them "you two are on interview duty today". What I mean is that after a quick introduction, they asked me to describe code to them. On the phone. Which is probably the worst medium to do that. With the communication difficulties, I gave up soon after.
If you want to test a candidate's code proficiency, there's plenty of online tools for that: Leetcode, Test Dome, etc. I'm surprised a large, well established company like Citi use such a clumsy recruitment process.
Interview questions [2]
Question 1
What are the features brought by Java 8, and which one have you used?
Design and scenario based questions, not straight from theory or books. Keep your concepts clear in programming and skills for developer roles. I applied for senior role, more questions they were expecting were in distributed architecture, complex KARAT coding etc.
Interview questions [1]
Question 1
System design questions, related to event processing for communication between different microservices.
The initial interview round is conducted by Karat, a third-party technical screening company. You will participate in a live, person-to-person online coding assessment to evaluate your core engineering competencies. All in all, it was good.
I applied online. I interviewed at Citi (London, England) in Feb 2026
Interview
Easy first round they use screen tool to ask you write some code. Second round is scheduled then got cancelled saying they will not proceed further? Waste of time in my opinion, also the interview person has nothing to do with the role you apply for.
Interview questions [1]
Question 1
Figure out a bug in the code.
Then write a small method.