Citicorp Finance Internship interview Experience


account_circleDewang Palav

Department : CSE

CGPA : 8.67

Profile
IT Services
Package/Stipend
Login to view this
Criteria
8+ but was raised later
Session
2015-16
Status
Accepted Offer
Round 1

Technical Interview

Time
20 mins
Difficulty
Medium
Interview Experience

The technical round consisted of applying your areas of expertise basically in data structure design. There were mainly implementations of classical data structure problems. You need to have basic conceptual knowledge of data structures. The questions were implementation based. They expect you to write code. The written code should be legible, organized and well indented. Speak as you write, let them glimpse your thought process of coding. It was followed by discussion on the major project in the resume. Never mention DSPD assignments in your CV. Mine consisted of Big Data analytics project I worked on during IIT-B intern. Try to do the most of the talking to lead the interview into your comfort zone. Select your words wisely

Round 2

HR Interview

Time
30 mins
Difficulty
Easy
Interview Experience

Be honest and yet diplomatic. Was asked about my hobby and family background. It was more of a conversation. Choose a hobby which you actually pursue. Do not yet blabber on and keep it formal at best. I was asked about the books I read, reading being the hobby I stated.

Round 3

Technical Interview

Time
30 mins
Difficulty
Difficult
Interview Experience

The reason for the difficulty level being high is we had the best interviewer for this round. The head of hiring process was an experienced person. And this interview was more of a combination of HR and technical interview. He knew how to ask the right questions and trap you. One just needs to be honest when it comes to the final selection interview, because the person is an experienced professional who knows his game. So good luck to all those who wish to be a part of this corporate paradigm.

Additional

Other comments

Just be yourself. Be very confident about the concepts you know. Never double guess, but be open to code review suggestions.