Intern

My interview process was for the Portfolio Construction Team within Aladdin Financial Engineering. The initial communication from BlackRock included information about the role and the technical interview format. I was informed in advance that the technical portion would involve live coding while sharing my screen, and that I could use a language such as Python or Java.

During the interview, the conversation started with questions about my background and resume. The interviewer asked me to explain several of my projects in detail, including what I personally worked on, the technical decisions I made, and the challenges I encountered. I was also asked why I was interested in BlackRock and why I wanted to work with the Aladdin Financial Engineering/Portfolio Construction team.

The technical discussion covered computer science and object-oriented programming fundamentals. Some of the questions included the differences between Java and C++, inheritance, multiple inheritance, and the diamond problem. The interviewer also asked follow-up questions to test whether I understood the concepts rather than simply knowing definitions.

The role itself is quite quantitative and technical. The Portfolio Construction team works on optimization and portfolio-construction problems, including mixed-integer constraints, multi-period portfolio transitions, restructuring, and liquidation strategies, so I would recommend candidates be comfortable discussing algorithms, optimization, programming fundamentals, and the technical details of projects listed on their resume.

My advice would be to know every project on your resume very well because the interviewer may go several levels deeper with follow-up questions. I would also review OOP concepts, Java/Python/C++ fundamentals, data structures and algorithms, and practice live coding while explaining your thought process clearly. It is also important to prepare a strong answer for "Why BlackRock?" and understand how Aladdin and the specific team fit within BlackRock.

My interactions with the interviewer were professional and technically focused. The discussion felt more like an evaluation of both problem-solving ability and depth of understanding rather than simply testing memorized answers. Overall, candidates should expect a combination of resume/project discussion, motivation and behavioral questions, computer science fundamentals, and live technical coding.