Bloomberg behavioral interview: Company values
The culture page frames these as traits rather than a scored rubric; recruiter and manager rounds probe motivation for Bloomberg specifically, teamwork and conflict handling.
| Progress | Principle | Your story |
|---|---|---|
| PassionateOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
| InspiredOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
| CuriousCuriosity and growth | Write a story | |
Sample answer: Tell me about something you had to learn quickly for a projectWhether you can learn something unfamiliar quickly and on purpose: a plan for what to learn first, using people and code as well as documents, and applying it to real work. Curiosity should lead to a result, not just a course you finished. Situation The engineer who owned our team's pricing service moved to another team with two weeks' notice. The service was written in a language nobody else on the team knew, and it was due for a change to support a new discount type in five weeks. Task I volunteered to take it over. I had never written that language, so I needed to become safe on call for the service within two weeks and ship the discount change on time. Action I made a plan around the service rather than the language. In the first three days I read the code path for a single price request from start to finish and drew it, writing down every language feature I did not understand. I learned only those features first, from the official tutorial and by writing small throwaway programs. I booked three one-hour sessions with the departing owner and used them only for questions I could not answer from the code, such as why certain decisions were made. To learn by doing, I fixed two small open bugs in my first week and asked an engineer from another team who used the language daily to review them. I kept a notes page of patterns and pitfalls, which became the service's onboarding guide. Result I took over on-call for the service after two weeks and shipped the new discount type a week early, with no incidents. A second teammate onboarded in four days using my notes. I still use the same approach for unfamiliar systems: trace one real request, learn what it needs, and ship something small in week one. Tip: Show something you learned on your own and how you used it at work. Curiosity and growth: weak answer, follow-ups and level differences | ||
| ProudOwnership | Write a story | |
Sample answer: Tell me about a time you took ownership of something outside your roleWhether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Situation My team owned an order service, and almost every Monday our on-call engineer was paged because a nightly export to the finance system had failed. The export job belonged to a data team that had been reorganised, so for months each of us had simply re-run it by hand and moved on. Task It was not my job and not on our roadmap, but it cost every on-call about two hours a week and the finance team kept getting late numbers. I decided to find the real cause and get it fixed properly, without letting my sprint work slip. Action I went through six weeks of job logs and saw that every failure lined up with a database maintenance window that had been moved earlier; the export was timing out on a locked table. I wrote a one-page note with the evidence and two options and took it to the data team's new lead rather than quietly patching their code. They agreed with the fix but had no time, so I offered to make the change if they reviewed it. I moved the start time, added retries with backoff, and routed the failure alert to the owning team instead of our rotation. I also wrote a short runbook and put the job back in the service catalogue with a named owner. Result The export has not failed since. That gave our rotation back about eight engineer-hours a month, and finance got its numbers on time every Monday. Now, whenever a recurring page looks like someone else's problem, the first thing I check is who owns it. Tip: Show you took responsibility beyond your task: you noticed, you acted, you followed through. Ownership: weak answer, follow-ups and level differences | ||
How to answer
Use STAR: the Situation in one or two sentences, the Task you owned, the Actions you took (in the first person, the longest part), and the Result with a number. One strong story can cover several principles, so write a few good ones in the story bank and tag them.
Behavioral questions by theme, with a tip for each · How the behavioral round is scored
Questions people ask
What is the Bloomberg behavioral interview based on?
Company values: Passionate, Inspired, Curious, Proud. The culture page frames these as traits rather than a scored rubric; recruiter and manager rounds probe motivation for Bloomberg specifically, teamwork and conflict handling.
How do I answer Bloomberg questions on "Passionate"?
Whether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Show you took responsibility beyond your task: you noticed, you acted, you followed through. A typical question: Tell me about a time you took ownership of something outside your role
How do I answer Bloomberg questions on "Inspired"?
Whether you treat the outcome as yours, not just the ticket. They want to see that you noticed a problem nobody assigned to you, judged it worth fixing, used the right channels, and followed it through to a result without dropping your own work. Show you took responsibility beyond your task: you noticed, you acted, you followed through. A typical question: Tell me about a time you took ownership of something outside your role