Business Analytics Interview Questions for 5 Years Experience
40 questions with answers for candidates with 5 years of experience — 1 easy, 28 medium, 11 hard.
What interviewers expect: 5 years experience
At five years, interviews shift towards senior analyst or lead expectations. You will be asked how you shape scope for large initiatives, design KPI frameworks, handle senior stakeholder conflict, improve team processes and mentor juniors. Technical questions remain, but depth of judgement, domain knowledge and examples of influencing decisions carry more weight.
This set is weighted towards SQL for Business Analysis (6), Product Analytics (5), UAT and BA Documentation (5), Requirements and Agile (5).
KPI frameworks and governance Requirements strategy for large projects Senior stakeholder management Mentoring and reviewing work
Solved at this levelStart 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.
✓ 3 questions free • Unlock the rest in seconds
01
Write a DAX measure that shows each category's percent share of total sales.
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.
03
What steps would you follow to create a tracking plan for a new 'save for later' feature?
Start from the questions to answer: how many users discover it, use it and later buy saved items. Define events such as save_clicked, saved_item_viewed, saved_item_removed and saved_item_purchased, with properties like product ID, price, source screen and platform. Follow the existing naming convention, assign owners, review with developers, and test events in a staging build. Build the dashboard before launch so data is checked on day one.
A UAT test plan defines how acceptance testing will be run. It covers scope and out-of-scope items, business processes to be tested, entry and exit criteria, roles such as testers, UAT lead and sign-off authority, test environment and test data, schedule and cycles, defect management process with severity definitions, communication and reporting, and risks. The BA usually drafts it with business owners so testers know exactly what they are accepting and when.
All three number rows within a window ordered by a column. ROW_NUMBER gives a unique sequence 1, 2, 3 even for ties. RANK gives ties the same number and then skips, so 1, 1, 3. DENSE_RANK gives ties the same number without gaps, so 1, 1, 2. Use ROW_NUMBER to pick exactly one row per group, such as the latest order, and DENSE_RANK for 'top 3 distinct salary levels' type questions.
07
What does the LTV to CAC ratio tell you and what is a healthy value?
LTV to CAC compares the lifetime gross profit from a customer with the cost of acquiring them. A ratio around 3 to 1 is commonly treated as healthy. Below 1 means you lose money on every customer. Far above 5 may mean you are underinvesting in growth. Always compute LTV on gross margin, not revenue, and check it by channel, because blended averages hide loss-making channels.
08
Write a DAX measure to count distinct active customers in the last 30 days.
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
The cash conversion cycle measures how many days cash is tied up in operations. It equals days inventory outstanding plus days sales outstanding minus days payables outstanding. Example: inventory sits 40 days, customers pay in 30 days and suppliers are paid in 45 days, so the cycle is 40 + 30 - 45 = 25 days. A shorter cycle means less working capital is needed. Some marketplaces have a negative cycle because they collect from customers before paying sellers.
10
In the middle of a sprint, a senior stakeholder asks to add an urgent feature. What do you do?
Understand the urgency and the business impact of waiting until the next sprint. Bring it to the product owner, who decides. If it truly cannot wait, the team agrees to swap out work of similar size so the sprint goal stays realistic, and the trade-off is made visible to the stakeholder. If it can wait, add it to the top of the backlog for the next sprint. Avoid silently adding scope.
11
After joining orders to a payments table, your total revenue doubled. What went wrong?
The join created a fan-out: some orders have more than one payment row, such as split payments or retries, so each order amount is repeated. Check the grain by counting rows per order_id on both sides. Fix it by aggregating payments to one row per order in a CTE before joining, joining on the full key, or summing from the table whose grain matches the metric. Always compare row counts before and after a join.
12
An order has a value of 600 rupees, product cost 360, delivery 60, payment fee 12 and a discount of 50. What is the contribution margin?
Net revenue after discount is 600 minus 50, which is 550 rupees. Variable costs are 360 plus 60 plus 12, totalling 432. Contribution margin is 550 minus 432, so 118 rupees per order, or about 21 percent of net revenue. This is what each order contributes towards fixed costs such as salaries and rent. If the discount were raised to 150, the order would contribute only 18 rupees.
13
Your project is going to miss its deadline by two weeks. How do you communicate this?
Tell the sponsor and key stakeholders as soon as you are confident, not on the deadline. Be direct about the delay, the cause and the impact. Come with options, such as reducing scope to hit the date, adding resources, or moving the date with a phased release, plus your recommendation. Agree on the new plan, update the communication plan and track the recovery visibly.
DMN (Decision Model and Notation) is an OMG standard for modelling business decisions, mainly through decision tables that list input conditions, outputs and a hit policy. BPMN shows the flow of work, while DMN holds the decision logic. Instead of drawing ten nested gateways for loan eligibility, you place one business rule task in BPMN that calls a DMN table. This keeps diagrams clean and lets business users change rules without redrawing the process.
15
What is an event tracking plan and why does it matter?
A tracking plan is a document listing every event the product should log, such as 'checkout_started', with its trigger, properties like price, plan or source, naming rules and owner. It keeps data consistent across web, Android and iOS, prevents duplicate or vague events and makes analysis trustworthy. Without one, teams end up with events like 'click1' and 'buttonClick' meaning the same thing, and analysis becomes guesswork.
16
What is root cause analysis and which techniques do you know?
Operating leverage describes how much of a company's cost base is fixed. With high operating leverage, such as software or airlines, a small rise in revenue produces a large rise in operating profit once fixed costs are covered, but a fall in revenue hurts profit just as sharply. It is measured as percentage change in EBIT divided by percentage change in sales. Analysts use it to judge risk, set break-even targets and stress-test forecasts.
18
How do you estimate the annual revenue of a coffee shop chain?
A model classifying features as basic, performance or delight attributes based on how they affect customer satisfaction, helping decide what to build first.
20
How would you build a simple financial model in Excel?
Read the execution plan to find full scans and expensive joins. Filter early on partitioned or indexed columns such as date, select only needed columns instead of SELECT *, and avoid functions on filter columns. Pre-aggregate in a CTE before joining, replace correlated subqueries with joins or window functions, and check join keys have matching types. For repeated use, build a summary table or materialised view refreshed daily.
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.
This is Simpson's paradox caused by a change in mix. If mobile converts lower than desktop and the share of mobile traffic grew sharply, the overall average can fall even though each segment improved. Show conversion by segment along with the traffic mix. The insight is not that conversion got worse but that traffic shifted, so the question becomes how to raise mobile conversion further.
26
Write a SQL query for Day-7 retention by weekly sign-up cohort.
WITH cohort AS (
SELECT user_id, signup_date,
DATE_TRUNC('week', signup_date) AS cohort_week
FROM users
),
ret AS (
SELECT DISTINCT c.user_id
FROM cohort c
JOIN events e ON e.user_id = c.user_id
AND e.event_date = c.signup_date + INTERVAL '7 day'
)
SELECT c.cohort_week, COUNT(*) AS users,
ROUND(100.0 * COUNT(r.user_id) / COUNT(*), 1) AS d7_retention_pct
FROM cohort c
LEFT JOIN ret r ON r.user_id = c.user_id
GROUP BY c.cohort_week
ORDER BY c.cohort_week;
27
A stakeholder keeps skipping review meetings and then rejects the deliverable at the end. How do you prevent this?
Talk to them one-to-one to understand why they skip, such as timing, relevance or workload. Offer shorter reviews, asynchronous reviews with a clear deadline, or a delegate with decision rights. Record sign-offs at each stage in writing so late changes become formal change requests. Share early drafts and mock-ups, because people react better to something visible. Escalate to the sponsor if the pattern risks the timeline.
A data object (page shape with a folded corner) represents information that an activity needs or produces during one process instance, such as an invoice or an application form. It is linked with dotted associations. A data store (cylinder) represents information that persists beyond the process instance, such as the customer database or ERP. Showing them helps developers see which systems are read or updated at each step and helps spot missing integrations.
Power Query is the data preparation engine inside Power BI and Excel. It connects to sources like Excel, CSV, SQL databases and web APIs, then lets you clean and shape data with recorded steps: remove columns, change types, split, merge, unpivot, append and group. Each step is written in the M language and replays on every refresh, so a monthly cleanup job becomes repeatable instead of manual.
Definition of Ready is a checklist a story must meet before the team pulls it into a sprint: clear description, acceptance criteria, dependencies identified, designs attached and estimated. Definition of Done is the checklist for calling work complete: coded, reviewed, tested, acceptance criteria passed, documented and deployable. The BA mostly drives readiness, while the whole team owns done. Both reduce rework and arguments at sprint end.
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.
It is a regression: the fix for one defect broke existing functionality, which usually means changes were not impact-analysed and there is no regression suite. Log it as a new high-priority defect linked to the fix. Agree with the team that every UAT build comes with release notes listing the changes, and that QA runs an automated or core manual regression pack before handing the build to business testers. Also add the broken flow to the UAT regression checklist.
36
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.
Combine several sources. Interview and observe users doing real tasks, and review screens, reports and outputs to infer business rules. Analyse the database and logs to see which data and functions are actually used. Work with long-serving staff and IT support for hidden rules and workarounds. Build AS-IS process maps, decide what to keep, drop or improve, and validate the findings with users. Plan data migration requirements early.
39
Inventory days rose from 45 to 70 over two quarters. What could be the causes and what would you recommend?
Possible causes include falling sales against unchanged purchasing, poor demand forecasts, bulk buying for discounts, slow-moving or obsolete SKUs, or deliberate stock-building ahead of a festive season or expected price rise. Analyse by SKU, warehouse and age bucket to find where stock is stuck. Recommend clearing aged items, adjusting reorder points using recent demand, and reviewing supplier minimum order quantities. Also quantify the cash locked up and the carrying cost to show urgency.
40
Tell me about a time poor or outdated documentation caused a problem. How did you fix it?
Situation: a new developer built a GST calculation from an old FRD version, and the error was caught only in UAT. Task: fix the defect and prevent repeats. Action: I moved all requirement documents into one shared space with version history, added a change log and status labels such as draft or approved, and linked each user story to the latest approved section. Result: in the next two releases we had no defects caused by outdated specifications.
Frequently asked questions
What is asked in Business Analytics interviews for 5 years of experience?
At five years, interviews shift towards senior analyst or lead expectations. You will be asked how you shape scope for large initiatives, design KPI frameworks, handle senior stakeholder conflict, improve team processes and mentor juniors. Technical questions remain, but depth of judgement, domain knowledge and examples of influencing decisions carry more weight.
How many questions should I practise before a Business Analytics interview?
Work through all 40 questions here, then the company-wise sets for the employers you are targeting. Quality matters more than count: be able to explain why each answer is right.
Which topics matter most for 5 years of experience?
Focus first on KPI frameworks and governance, Requirements strategy for large projects, Senior stakeholder management, Mentoring and reviewing work.