
Software engineer candidates at BlackRock describe an early aptitude screen in some loops, easy-to-medium technical rounds covering DSA and SQL, and resume-focused conversations. Stack and pacing vary by team.
$124K
Avg. Base Comp
$142K
Avg. Total Comp
2-4 rounds
Typical Rounds
Not reported
Process Length
Reports for BlackRock software engineer roles describe friendly interviewers but a process that varies a lot by team. In some loops there is an early aptitude screen before any live technical conversation. One Software Engineer candidate's test mixed pseudocode, SQL input/output problems, reasoning and English comprehension. It aimed to catch basic gaps rather than go deep. Treat it as a fundamentals check and practice tracing SQL output by hand.
Where candidates reached live interviews, the technical bar was described as easy to medium. One Software Developer had a single 60-minute session on DSA and SQL alongside project discussion. The Software Engineer who sat the aptitude test then met inner and outer join questions and linked list problems. At the other end, an Associate Software Engineer faced separate rounds on Java and distributed systems and on algorithmic coding. Check the job description for the stack rather than assuming one.
Expect your resume to carry weight. An associate candidate was pressed on projects, especially websockets, plus OOP and database design, and was asked how they would explain AI to children or older people. Be ready to defend every line and to explain technical ideas plainly. Later HR conversations were behavioral, and one candidate was given a case study on handling an incident or competing priorities.
Several candidates in these reports did not receive offers, and pacing was often slow. Waits stretched to weeks, and in one case months, between rounds or before a decision, so a polite follow-up with the recruiter is reasonable.
Synthesized from 27 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Blackrock process.
The whole process moved faster than I expected. HR reached out on LinkedIn and started with a quick email to confirm salary expectations and whether I was genuinely looking to leave my current role. That was straightforward — no surprises there.
Then came four interview rounds spread over about five weeks. My first was a thirty-minute conversation with the hiring manager, pretty relaxed and focused on understanding my background and what I was looking for. The next two rounds were each thirty minutes with different Directors, and those felt similarly casual despite being with senior people. The final round was a longer forty-five-minute session with another Director, which gave us more time to dig into specifics.
Technically, I had two medium-difficulty interviews with software engineers on the team. They asked a lot about .NET and C#, some TypeScript, and a few SQL questions. Nothing felt like a surprise trick — just solid technical questions testing whether I could code and think through problems. The behavioral rounds happened with managers and were pretty standard: they wanted to hear about my projects, how I'd handled teamwork challenges, and situations where I'd had to collaborate under pressure.
What stood out most was how smooth the entire coordination was. HR stayed in touch throughout, scheduling was easy, and everyone I spoke with felt genuinely pleasant to work with. The interviews themselves were chill — no gotcha moments or aggressive questioning. People seemed interested in whether we'd be a good fit together rather than trying to trip me up. By the end of five weeks, I had an offer in hand. The whole experience felt less like being tested and more like getting to know a team that actually wanted to work with me.
Prep tip from this candidate
Focus on .NET/C# and TypeScript fundamentals plus SQL queries for the technical rounds — those are the core areas tested. For behavioral, have concrete project examples ready that show how you've collaborated and handled team dynamics, since the managers will dig into those heavily.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Blackrock
Identify the groups of anagrams in a list of words
| Question | |
|---|---|
| Data Stream Median | |
| Why Do You Want to Work With Us | |
| Justify a Neural Network | |
| LRU Cache 1 | |
| Accessible Data | |
| Tic-Tac-Toe Outcome | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| P-value to a Layman | |
| Rectangle Overlap |
Synthesized from candidate reports. Individual experiences may vary.
One Software Engineer candidate started with an online aptitude test mixing pseudocode, SQL input/output problems, reasoning and English comprehension. It was described as foundational rather than deep.
Some candidates report an early conversation about their experience and past projects. A Software Developer described a behavioral first round walking through projects and engineering practices. An Associate Software Engineer's first interview was with the hiring manager.
Technical rounds were described as easy to medium. One Software Developer reported a 60-minute session on DSA and SQL. Another candidate met SQL joins and linked list questions, and an associate candidate was asked about OOP, database design and websockets. One Associate Software Engineer had back-to-back rounds on Java and distributed systems and on algorithmic coding.
Later rounds were behavioral. One candidate described an HR round with a case study about handling an incident or competing priorities. An associate candidate met a director as a final round, then heard nothing for a month.