Bloomberg · Primly Community

Bloomberg frontend engineer interview: yes they go deep on JS fundamentals

frontend_fran · 4 replies

Finished the Bloomberg frontend engineer loop in March 2026. Sharing because the frontend interview experience there is a bit different from what I was used to at product companies.

Background: 4 years in frontend, mostly React, Bay Area. Applied to a NYC-based role, did the loop fully remote.

What the loop looked like. Phone screen with recruiter. Technical screen with an engineer (45 minutes, mostly JavaScript). Then an onsite with four rounds over a day: two coding, one system design for frontend, one behavioral.

JavaScript fundamentals. This was the biggest surprise. Bloomberg went deeper on raw JS than any interview I've had before. We're talking closures, prototype chains, event loop and call stack, this binding edge cases, promise internals. Not "what does async/await do" but genuinely: what does the event loop actually do with a microtask queue vs a macrotask queue. If you've been writing React for years and kind of forgot the underneath, go back and review it. MDN + Jake Archibald's event loop talk.

Coding rounds. Algorithmic but not pure LeetCode. One round was a DOM manipulation problem: build a simple component from scratch without a framework. Vanilla JS. No React, no library. Had to handle event delegation, manage state manually, make it accessible. That was harder than I expected. Second round was more standard algorithm problem, medium level.

Frontend system design. Design a real-time financial data dashboard. Think: streaming updates, rendering performance, handling slow network. I talked about websockets for the data layer, virtual scrolling for large tables, debouncing/throttling, Web Workers for heavy computation off the main thread. They pushed on accessibility and performance testing which I thought was a good sign of what they actually care about.

Behavioral. Similar to what others have said for Bloomberg generally. Ownership and failure stories, specific examples. I told a story about a performance regression we shipped and how we found and fixed it. That landed well.

The Bloomberg terminal is used by finance professionals who want precision and reliability, not a flashy consumer app. I think that shapes what they look for in frontend engineers. Performance, correctness, and solid fundamentals over the latest framework.

4 replies

qa_quinn

The accessibility question in the system design round is interesting. A lot of companies claim to care about a11y but never actually ask about it. The fact that it came up as a probe is a decent signal.

qa_quinn

Genuine question: is the vanilla JS DOM manipulation test actually relevant to the job, or is it one of those interview-only skills that has no bearing on what you'd actually build there? Asking because Bloomberg uses their own framework (B-PIPE, various internal tools) and whether you can imperatively wire up a button click seems kind of arbitrary.

frontend_fran

Honestly, probably a mix. My read is it tests whether you actually understand what React is doing under the hood vs. just knowing the API. If you can't build a simple interactive component without a framework you probably don't understand the fundamentals well enough for a company that writes a lot of internal tooling. Still, fair point that it's a proxy.

staff_steph

The event loop microtask vs macrotask question is one of those things that separates people who've been writing JS for years from people who've been writing React for years. Very different things. Good call-out.