← Back to Directory

BlackRock interview notes, page 1 of 2

Large Enterprises

Most of these BlackRock write-ups come from Software Engineers (16), then Data Scientists (3) and Product Managers (1). The most reported rounds are the technical phone screen (15), the behavioral / leadership round (2), the online assessment (1) and the system design round (1).

20 interview notes · updated Jul 2026

BlackRock·Software Engineer·Technical Phone Screen

Apr 2026
BlackRock data engineer interview, got a classic intervals problem. Nothing too surprising but the pressure of knowing it's BlackRock made me second-guess my approach more than I should have.
  • Given an array of intervals, merge all overlapping ones and return the resulting non-overlapping intervals.

“I knew this problem but blanked on the sorting step for a second.”

View Post

BlackRock·Software Engineer·Onsite - System Design / Architecture

Apr 2026
System design round at BlackRock for a software engineer role. The whole thing was basically one big OOP and design question about a parking lot, but with enough layers that it kept going for a while.
  • Design a parking lot system that handles multiple vehicle types (motorcycle, car, truck) with appropriately sized spots, multiple floors, ticket generation on entry, fee calculation on exit, and logic for finding available spots. Walk through the class hierarchy, key APIs, and how you'd extend it for reservations or real-time availability.

“I started with the class hierarchy which felt natural, vehicle types mapping to spot sizes and all that.”

View Post

BlackRock·Software Engineer·Technical Phone Screen

Apr 2026
BlackRock software engineer interview focused on a classic 2D prefix sum problem. Pretty algorithmic, not much else to it, but the follow-up about arbitrary range queries is where things got interesting.
  • Given an m×n integer matrix, design a solution that preprocesses it so any query for the sum of elements from (0,0) to (x,y) runs in O(1). Walk through the preprocessing time and space complexity.
  • How would you extend the prefix sum approach to support sum queries over an arbitrary submatrix from (r1,c1) to (r2,c2), not just from the origin?

“I knew prefix sums going in, so the core answer came out fine.”

View Post

BlackRock·Data Scientist·Technical Phone Screen

Apr 2026
BlackRock data science interview, one technical round focused entirely on quantitative modeling. The question was meaty and multi-part, covering the full lifecycle from design to production monitoring. Felt like they genuinely wanted to see if you'd actually shipped something versus just read about it.
  • Walk me through a quantitative model you built to analyze market data. What was its purpose, what assumptions did you bake in, what data did you feed it, how did you validate it, and how did you handle overfitting and model drift over time?

“This question is basically five questions stitched together and they expect you to hold the thread across all of them.”

View Post

BlackRock·Software Engineer·Technical Phone Screen

May 2026
BlackRock software engineer interview with a coding round that was basically a mini design-plus-implementation problem. One question, but it had enough layers to keep you busy for the whole session.
  • Design and implement a simplified Paint editor class that supports drawing, erasing, and flood-fill operations on a 2D canvas, along with full undo and redo functionality.

“The fill part was fine, BFS/DFS flood fill is pretty standard.”

View Post

BlackRock·Software Engineer·Technical Phone Screen

May 2026
BlackRock Quant Engineer interview with a big open-ended question about where quant finance is heading over the next decade. Felt more like a conversation than a technical grilling, which I wasn't fully prepared for.
  • Where do you see quantitative finance heading over the next 5 to 10 years, and what trends do you think will have the biggest impact on the industry and the broader global economy?

“This one sprawled in every direction and I let it.”

View Post

BlackRock·Data Scientist·Take-home Assignment

May 2026
Interviewed for a quant-facing Data Scientist role at BlackRock. Three written prompts covering model-building experience, cross-domain transferability, and a broader take on where quant finance is headed. No coding, no case math, just a lot of open-ended thinking put to paper.
  • Walk through a quantitative model you've built or worked with on market data. Cover the problem it solved, the data and signals used, your methodology and why it fit, how you validated it, and where the model breaks down.
  • How does your quantitative and markets background translate to other domains? Give a concrete example or two.
  • What's your view on the future of quantitative finance, including the opportunities, the risks, and the structural changes you see coming?

“This was the meat of the whole thing and I probably over-engineered my answer.”

View Post

BlackRock·Software Engineer·Technical Phone Screen

May 2026
BlackRock software engineer interview with a verbal reasoning / critical thinking component. The question was a passage-based true/false exercise, which I wasn't expecting at all for a SWE role.
  • Read a short passage about a bank's Q2 performance metrics, then classify four statements as True, False, or Cannot Say based strictly on the text. For one borderline case, briefly explain your reasoning.

“Tripped up on statement 3 for a second.”

View Post

BlackRock·Product Manager·Onsite - Behavioral / Leadership

May 2026
Behavioral prep session for a Product Manager role at BlackRock, focused on motivation and background questions. Pretty standard stuff but the 'not on your resume' question is sneakier than it looks.
  • What motivates you to work at BlackRock specifically?
  • Tell me about something that is not on your resume.

“I fumbled this the first time I practiced it because I kept defaulting to 'scale and impact' which sounds like I googled the company for five minutes.”

View Post

BlackRock·Software Engineer·Technical Phone Screen

Jun 2026
BlackRock software engineer interview with two back-to-back coding problems and a tight two-minute verbal explanation window after each one. Pretty focused on fundamentals but the submission constraint made it stressful.
  • Implement a sorting function from scratch (no built-in sort) that returns a list of integers in non-decreasing order. After coding, explain your choice of algorithm along with its time and space complexity and whether it's stable.
  • Write a function that takes two iterables of integers and returns a sorted list of unique elements appearing in both. You need to handle input parsing yourself, cover edge cases like empty inputs and duplicates, and explain time and space complexity. Only one submission allowed.

“I went with merge sort because I could at least explain stability confidently.”

View Post