Bloomberg Business Analytics Interview Questions & Answers
Curated interview practice questions with answers. These are practice scenarios, not a verified list of past interview questions.
About Bloomberg hiring for Business Analytics roles
Bloomberg is a financial data, software and media company best known for the Bloomberg Terminal used by finance professionals. It provides market data, analytics, news and trading tools. Its India presence includes Mumbai-based teams, and its interviews for engineering and data roles focus on problem solving and an interest in financial markets.
For Business Analytics roles, this Bloomberg practice set focuses most on Case Studies and Guesstimates (8), SQL for Business Analysis (6), UAT and BA Documentation (5), Excel for Business Analysts (4). It has 6 easy, 26 medium, 8 hard questions, so you can start easy and work up to the harder ones.
Company type
Fintech
Headquarters
New York, USA
Main India offices
Mumbai
Bloomberg Business Analytics interview process
Recruiter screening
Technical phone interview (coding)
Onsite technical rounds
Manager round
HR round
Typical pattern based on public candidate experiences. Rounds vary by role, team and year.
Solved for BloombergStart practicing
3 QUESTIONS FREESign up to unlock the full question bank and track your progress.Unlock every question and answer, then continue practising company-wise and package-wise.
CALCULATE evaluates an expression under a modified filter context. You pass a measure plus filter arguments that add, replace or remove filters, for example CALCULATE([Sales], 'Region'[Name] = "North") or CALCULATE([Sales], ALL('Product')). It is the basis of time intelligence, percent-of-total and comparison measures. It also triggers context transition when used inside a row context, which is powerful but a common source of confusion.
A model classifying features as basic, performance or delight attributes based on how they affect customer satisfaction, helping decide what to build first.
03
Write a defect report for an invoice that calculates GST incorrectly.
Title: Invoice applies 12 percent GST instead of 18 percent for service items. Environment: UAT, build 2.4.1. Steps: create an order with service item SRV-101 at 1,000 rupees for a customer in Maharashtra and generate the invoice. Expected: CGST 90 and SGST 90, total 1,180. Actual: CGST 60 and SGST 60, total 1,120. Severity: high, as it affects tax compliance. Attachments: invoice PDF and screenshot. Linked requirement: FR-TAX-07.
04
What is Excel Solver and give a business example of using it.
Solver is an optimisation add-in that finds the best value of a target cell by changing decision cells within constraints. Unlike Goal Seek, it handles many variables and constraints. Example: choose how many units of three products to make to maximise profit, subject to machine hours, raw material and minimum order limits. You set the objective, the variable cells, constraints and a method such as Simplex LP for linear problems.
05
How do you write an effective executive summary for an analysis report?
Put it first and keep it to one page or five lines on a slide. Start with the answer or recommendation, then the two or three key findings that support it, each with a number, then the impact in rupees or percentage, and finally the decision or action needed and by when. Avoid methodology details, which go in the appendix. Test it by asking whether a busy leader could act after reading only this section.
06
What are heatmaps and session recordings, and when would you use them alongside funnel analysis?
Heatmaps aggregate where users click, move and scroll on a page, while session recordings replay individual user sessions. Funnel analysis tells you where users drop off, for example 40 percent leave on the address page; heatmaps and recordings help explain why, such as a hidden Continue button or a confusing pin code field. They are qualitative, so use them to form hypotheses and then validate fixes with an A/B test. Personal data must be masked in recordings.
07
What is an impact-effort matrix and how do you use it to prioritise recommendations in a case?
An impact-effort matrix is a 2x2 grid that plots options by expected business impact against effort, cost or time. High impact and low effort are quick wins to do first; high impact and high effort are major projects to plan; low impact and low effort are fill-ins; low impact and high effort should be dropped. In a case interview, it helps you end with a clear, prioritised recommendation rather than a long list of ideas.
08
Gross margin fell from 38 percent to 34 percent in one quarter. How do you investigate?
Break the change into drivers. Price: were discounts or promotions deeper? Mix: did sales shift towards lower-margin products, channels or regions? Cost: did raw material, freight or supplier prices rise, or did currency movements raise import costs? Also check one-offs like inventory write-offs and accounting reclassifications. Build a margin bridge showing how many percentage points each driver contributed, then take the biggest driver to the business owner with a specific action.
09
A client's profits are falling. How do you structure the problem?
Split into revenue and cost, then revenue into price, volume and mix, and cost into fixed and variable; check internal factors and external market factors.
10
Write a SQL query for a signup to purchase funnel from an events table.
WITH steps AS (
SELECT user_id,
MAX(CASE WHEN event = 'signup' THEN 1 ELSE 0 END) AS s1,
MAX(CASE WHEN event = 'add_to_cart' THEN 1 ELSE 0 END) AS s2,
MAX(CASE WHEN event = 'purchase' THEN 1 ELSE 0 END) AS s3
FROM events
WHERE event_date >= '2026-10-01'
GROUP BY user_id
)
SELECT SUM(s1) AS signups,
SUM(s1 * s2) AS carts,
SUM(s1 * s2 * s3) AS purchases,
ROUND(100.0 * SUM(s1 * s2 * s3) / NULLIF(SUM(s1), 0), 2) AS conv_pct
FROM steps;
11
Write Tableau calculated fields for profit ratio and a flag for loss-making orders.
// Profit Ratio (aggregate so it works at any level)
SUM([Profit]) / SUM([Sales])
// Loss Flag (row level)
IF [Profit] < 0 THEN "Loss" ELSE "Profit" END
// Put Loss Flag on Color to highlight loss-making orders
SUMIFS is faster and easier for sums with AND conditions on ranges. SUMPRODUCT multiplies arrays and sums the result, so it handles cases SUMIFS cannot: weighted totals like price times quantity, OR logic, conditions on calculated values such as MONTH(date)=4, or comparing two columns row by row. On very large sheets SUMPRODUCT is slower, so prefer SUMIFS or a helper column when possible.
13
What is product analytics and how is it different from business reporting?
Product analytics studies how users behave inside a digital product, using event data such as sign-ups, clicks, feature use and purchases, to improve activation, engagement and retention. Business reporting usually summarises outcomes like revenue, cost and orders by period. Product analytics answers questions like where users drop off, which features retained users adopt, and whether a change worked, often through funnels, cohorts and experiments.
14
Two analysts report different monthly active user numbers from the same database. How do you resolve it?
Put both queries side by side and compare definitions: which events count as active, time zone, calendar versus rolling month, test and internal accounts, deleted users, and DISTINCT on user ID versus device ID. Run both on a single day to find where they diverge. Agree on one definition with the metric owner, document it, and publish it as a shared view or metric so everyone queries the same logic.
15
Three departments describe the same order process in three different ways during workshops. How do you arrive at the true AS-IS?
Treat each version as a hypothesis. Walk the process physically or observe real cases end to end, and pull a sample of 20 to 30 recent orders from the system to trace what actually happened. Compare timestamps and status changes with each department's story. Then hold a joint session, show the evidence-based map and mark the variants openly. Often all three are partly right because different order types follow different paths, which should be modelled explicitly.
Alpha testing is done internally, by employees or a selected group, in a controlled environment before the product is released to outsiders, and aims to catch major issues early. Beta testing releases the product to a limited group of real external users in real conditions to gather feedback on usability, performance and missing features before general release. For a mobile app, beta often uses store testing tracks, and feedback is fed into the final release backlog.
18
A hospital chain's average patient waiting time has risen from 30 to 50 minutes. How would you approach the case?
Clarify where the wait is measured: registration, consultation, diagnostics or billing. Split the problem into demand and capacity. On demand, check patient volume, peak-hour mix, walk-ins versus appointments and new departments. On capacity, check doctor availability, no-shows of staff, consultation time per patient and process bottlenecks such as manual billing. Identify the biggest stage and suggest fixes like slot-based appointments, triage and digital billing.
19
What is the difference between OLTP and OLAP systems?
Active Customers 30D =
CALCULATE(
DISTINCTCOUNT(Sales[CustomerID]),
DATESINPERIOD('Date'[Date], MAX('Date'[Date]), -30, DAY)
)
-- MAX('Date'[Date]) makes it relative to the date in the current filter
Start from the test cases and list the data each needs: customer types, product variants, edge values and historical records. Decide whether to use masked copies of production data, synthetic data or both, because real personal data must be anonymised under data protection rules such as the DPDP Act. Prepare data for negative and boundary cases, keep a refresh plan for repeated cycles, and assign owners. Poor test data is one of the most common causes of blocked UAT days.
22
What steps do you follow to plan and run a UAT cycle?
Plan: agree scope, entry and exit criteria, testers and schedule with the business owner. Prepare: write scenarios and test cases from requirements, set up the environment and test data, and brief testers. Execute: run test cases in daily sessions, log defects with evidence and hold a daily triage. Monitor: report progress, pass rate and open defects by severity. Close: check exit criteria, get the business sign-off with known issues documented, and hold a short lessons-learned review.
23
What are process levels such as L0 to L4 in a process architecture?
Process levels organise models from broad to detailed. L0 shows the value chain or main process areas, such as Order to Cash. L1 and L2 break these into process groups and end-to-end processes, such as Credit Management. L3 shows the detailed BPMN flow with roles and decisions. L4 covers work instructions or system steps. A level structure keeps hundreds of diagrams consistent, avoids duplicates and lets executives and operators each read the right depth.
24
A critical defect is found on the last day of UAT, and the go-live date cannot move. What do you do?
Confirm the impact and reproduce it quickly. Work with development to estimate a fix and its regression effort. Then present options to the business owner with risks: fix and do targeted retesting before go-live, go live with a temporary workaround or manual process, go live with the affected feature switched off, or delay. The decision belongs to the business, documented at the go or no-go meeting. Never hide a critical defect to protect a date.
25
What is an issue tree and how does a hypothesis-driven approach work?
An issue tree breaks the main question into smaller, MECE sub-questions until each can be answered with data, such as 'why are profits down?' into revenue and cost branches. A hypothesis-driven approach starts with a likely answer, for example 'profit fell because delivery costs rose', and uses the tree to decide which data proves or disproves it first. It focuses effort and keeps the case structured and fast.
26
How do you build a PivotTable to analyse sales by region and product?
Situation: we tested a simplified pricing page expecting higher paid conversion. Task: I owned the experiment design and analysis. Action: after two weeks the variant showed no significant change, and segment checks revealed that heavy users missed the plan comparison table. I documented the result and shared it openly rather than searching for a winning segment. Result: the next version kept the simple layout with an optional comparison, and we learned to interview users before testing.
28
A company reports a profit every quarter but is running out of cash. How do you explain and investigate it?
Profit is an accrual figure, while cash depends on timing. Check working capital first: receivables may be growing because customers pay late, inventory may be piling up, or suppliers may be demanding faster payment. Then look at large capex, loan repayments, and dividends. Review the cash flow statement and compute days sales outstanding and inventory days over time. Fixes include tighter credit terms, collection drives, inventory reduction and renegotiating supplier terms.
29
Write a SQL query to calculate the repeat purchase rate.
WITH per_customer AS (
SELECT customer_id, COUNT(DISTINCT order_id) AS orders
FROM orders
GROUP BY customer_id
)
SELECT
ROUND(100.0 * SUM(CASE WHEN orders >= 2 THEN 1 ELSE 0 END)
/ COUNT(*), 2) AS repeat_rate_pct
FROM per_customer;
30
How do you calculate cycle time, touch time and process efficiency? Give an example.
Cycle time (lead time) is the total elapsed time from the start to the end of a case. Touch time is the time someone actually works on it. Process cycle efficiency is touch time divided by cycle time. Example: a refund takes 5 working days (40 working hours) end to end, but the agents spend only 2 hours in total working on it. Efficiency is 2 / 40 = 5 percent, so 95 percent of the time is waiting, and queues are the main target.
First split by who cancels: riders or drivers. For rider cancellations, check wait times, pickup accuracy, price surges and changes in ETA. For driver cancellations, check trip distance, payment mode, low fares, destination visibility and incentive changes. Then segment by city, time of day and area. Link to recent changes like a new pricing rule. Recommend fixes for the largest driver, such as better matching or adjusted incentives.
33
Stakeholders give conflicting requirements. What do you do?
Clarify the goal behind each request, map them to business objectives, prioritise with MoSCoW, run a joint session, then document the decision and get sign-off.
A/B testing is a controlled experiment where users are randomly split into a control group that sees the current version and a treatment group that sees a change, such as a new checkout button. You compare a pre-decided primary metric, like conversion rate, between groups. Because assignment is random, a significant difference can be attributed to the change rather than to seasonality, marketing or user mix.
37
Write a SQL query to find the percentage of orders delivered late in each city.
-- late = delivered after the promised date
SELECT
city,
COUNT(*) AS total_orders,
SUM(CASE WHEN delivered_at > promised_at THEN 1 ELSE 0 END) AS late_orders,
ROUND(100.0 * SUM(CASE WHEN delivered_at > promised_at THEN 1 ELSE 0 END)
/ COUNT(*), 2) AS late_pct
FROM orders
WHERE status = 'DELIVERED'
GROUP BY city
ORDER BY late_pct DESC;
38
Write Excel formulas for IRR with yearly cash flows and XIRR with irregular dates.
# Yearly cash flows in B2:B7, year 0 investment negative
=IRR(B2:B7)
# Irregular dates: cash flows in B2:B7, dates in C2:C7
=XIRR(B2:B7, C2:C7)
# XIRR returns an annualised rate based on actual dates,
# which suits SIP returns or projects with uneven payments.
Restructure it into levels. Create a high-level map with 7 to 10 main steps, then collapse detailed parts into sub-processes with their own diagrams. Move complex decision logic into a decision table rather than chains of gateways. Show the happy path first and handle exceptions in separate views. Use consistent naming in verb-noun form and remove duplicated steps. Finally, test readability by asking a stakeholder to explain the diagram back to you.
Tips to crack the Bloomberg Business Analytics interview
Practise DSA problems with a focus on clear communication, as Bloomberg interviewers often discuss your approach in detail.
Learn basic market concepts like stock prices, bonds and indices, since Bloomberg products serve financial users.
Read about the Bloomberg Terminal and its features so you can explain why financial data products interest you.
Keep a one-minute story ready for every project on your CV: problem, your part, tools, result.
Practise the hard questions on this page aloud; Bloomberg interviewers usually ask follow-ups on your first answer.
Frequently asked questions
How many rounds are there in the Bloomberg Business Analytics interview?
Candidates usually go through 5 stages: Recruiter screening; Technical phone interview (coding); Onsite technical rounds; Manager round; HR round. The exact rounds change with the role, team, location and your experience, so confirm the process with the recruiter.
Which topics should I prepare for the Bloomberg Business Analytics interview?
This practice set leans on Case Studies and Guesstimates (8), SQL for Business Analysis (6), UAT and BA Documentation (5), Excel for Business Analysts (4). Revise those first, then practise explaining one or two of your own projects end to end, because most Bloomberg interviewers ask you to walk through real work.
Are these the exact questions asked at Bloomberg?
No. These are curated practice questions that match the skills and difficulty usually tested in fintech interviews like Bloomberg's. They are not a leaked or verified list of past questions.
Where does Bloomberg hire Business Analytics professionals in India?
Bloomberg has large teams in Mumbai. Openings and locations change often, so check the Bloomberg careers page and filter by city and experience.
Business Analytics questions for similar companies