Interviewing quietly while employed. Did Bloomberg's OA and first coding round earlier this week. Here's the breakdown because I could not find recent data.
Online assessment (OA): Two coding problems, 90 minutes. Platform is HackerRank (as of June 2026). Both problems were medium difficulty by LeetCode standards. One was clearly a graph problem (shortest path variant), one was string manipulation. No trick input at the end, no weird edge cases that broke solutions. I thought it was straightforward.
First technical phone screen (post-OA): 45-60 minutes with one SWE. They share a collaborative code editor, you code in whatever language you want. I used Python. One coding problem, medium-hard. Mine involved interval merging with some extra constraint. Interviewer was not hostile, asked me to think aloud, gave hints when I was stuck for more than a few minutes. They also asked two conceptual questions at the end, not coding: one about time/space complexity, one about "how would you test this function."
Notes on difficulty: The OA is not tricky. If you're comfortable with graph traversal, BFS/DFS, and basic string problems, you'll pass. The phone screen can be harder. Interval problems, sliding window, dynamic programming have all come up based on what I've seen people mention. Bloomberg is not trying to filter on LC Hard. They seem more interested in whether you write clean, runnable code than whether you nail an esoteric problem.
One thing that surprised me: they asked me what language I'd use in production for this and why. So knowing the tradeoffs of your language choice matters, not just "I picked Python because I know it."
Still waiting to hear back. Will update if I get to onsite.