Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
Interviewed recently? Share your experience to try it free, or become a member for full access.
“Overall, I felt that the interview went well. I was able to clearly explain my experiences, discuss the projects I have worked on, and connect them to why I was interested in the position. I was also comfortable answering technical and behavioral questions, and I think I communicated my thought process effectively rather than just giving short answers.”
“Rigorous process, DSA questions for data engineering team. Cloud native questions and behavious. Team meeting, and vibe coding. ”
“The Overall Interview ProcessStep 1: Online Assessment (OA): A 60-90 minute screening on platforms like Codility or HackerRank, often featuring 2 LeetCode Medium coding questions and sometimes logic or SQL-based multiple-choice questions.Step 2: Technical Screening (often via Karat): A live technical interview with a third-party partner like Karat. This focuses on core Data Structures and Algorithms (DSA) and fundamental software engineering principles.Step 3: Technical Deep-Dive / Team Panel: A more thorough session with Citi engineers focusing on System Design, Java/Python specifics (like multithreading or database ACID properties), and a deep-dive into your past project architecture.Step 4: Hiring Manager / Behavioral Round: A "culture fit" discussion using the STAR method to evaluate your teamwork and communication, often ending with HR discussions on salary and policy”
“I completed four interview rounds, from the initial recruiter screen to the final System Design round. HR was very supportive throughout the process. The coding rounds consisted of one Medium LeetCode session and one scenario-based OOP coding session. I didn't pass the final System Design stage; feedback indicated they value design skills more than coding speed or syntax, noting that AI tools have made the implementation side of engineering much easier.”
“Hiring managers asked a lot of questions about Java internals, Java build system internals (Maven vs Gradle behaviors), networking internals (HTTP vs HTTP2)”
“Overall, the interview question was clear and easy to understand. The problem review system was clear for going through the task, though the review experience could be a little more intuitive and streamlined. A clearer way to review the problem details and navigate between sections would make the overall experience smoother. ”
“Process was straightforward with quick feedback. Got a 3d dp and then easy second interview which was standard hashmap manipulation.”
“In coding rounds, the questions asked were NOT leetcode based. Both coding rounds had follow ups. Expection is to have working solutions. In one of the system design rounds, there was unusally more focus on the APIs than the actual design.”
“I was refer to this job by my friend. After my profile got shortlisted I got my interview schedule immediately. And got the interview feedback within a day. All this process took around 2-3 days. ”
Preview full access of other recent interview experiences
“The weirdest Anthropic round was the company values interview. It was almost like a therapy session, and honestly if you went to a therapist at some point, you will pass that round much more easily.”
“What was very unusual is they didn’t give me any tooling to draw the system design, so I just sketched it on a piece of paper and talked them through it, then we got into this oddly deep debate about whether hover-over history should count as a recommendation signal.”
