Real, anonymous reports from people who interviewed for Frontend Engineer at Citigroup, newest first and distilled into what to expect across the loop.
Get your personalized Citigroup Frontend Engineer prep plan
Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.
My interviews themselves were fine from a technical standpoint—during the loop I was told I was doing well and that the conversations went okay. But the process after that fell apart because HR was completely unresponsive.
I kept emailing people in the HR part of the interview loop after being told I was progressing. Over roughly five weeks, I didn’t get any replies back at all, despite following up multiple times. The whole time, I had the sense that the interview wasn’t the problem, but communication and decision-making follow-through were.
12 months ago
Average Negative Pune
My interview started abruptly with a direct set of questions, without much warm-up or introductions. I was asked JavaScript basics, then moved into project-related questions around roles and responsibilities and how deployment worked. The discussion also covered tooling details like what Babel is, what goes into package.json and package-lock.json, and how angular.json fits into the bigger picture.
Cloud questions came up, but they stayed at a high level rather than going deep into specifics tied to one vendor. The way the interviewer jumped straight into technical questions made the interview feel more like a targeted check on my frontend engineering knowledge than a broad conversation. Overall it landed in the average difficulty range for me, and while I got through the session, I didn’t end up receiving an offer.
Share your interview experience
Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.
