Did the Bloomberg senior PM loop earlier this year. There isn't much PM-specific content out there for Bloomberg, so here's what I actually encountered.
First thing to know: Bloomberg PM is not like PM at a consumer tech company. The users are financial professionals. The products are often internal tools, terminal features, data feeds, or analytics surfaces for traders and analysts. If you have only consumer PM experience, you'll need to translate it convincingly.
Product sense questions: "Walk me through how you'd approach improving a feature of the Bloomberg Terminal for portfolio managers." "How would you prioritize which markets/asset classes to add to a new data product?" "A key client says our API is too slow for their use case. Walk me through how you'd investigate and respond."
What they're looking for: rigor and specificity. A vague "I'd talk to users and A/B test" answer gets you nowhere. They want to see that you know how financial professionals actually work, that you understand latency requirements, data accuracy, compliance constraints. Do your research on Bloomberg's product surface before you go in.
Execution / prioritization questions: "Tell me about a time you had to ship under real constraints." (Time, engineering resources, regulatory) "How do you handle a situation where the engineering team and a key stakeholder want completely different things?"
Behavioral: Same themes as engineering: ownership, directness, shipping through ambiguity.
The case-style question: I got one loosely case-like question about estimating TAM for a hypothetical new Bloomberg data product. Not a full McKinsey case, but structured thinking and sizing mattered.
My honest take: Bloomberg PM interviews are harder than average because the domain expertise bar is real. Generic PM frameworks will not save you. Read up on market data infrastructure, understand what the terminal does (get a demo if you can), and have a point of view on where Bloomberg's products have room to improve.