Business Analytics Interview Questions for 10 Years Experience
40 questions with answers for candidates with 10+ years of experience — 11 medium, 29 hard.
What interviewers expect: 10 years experience
At ten years, roles are usually head of business analysis, analytics director or practice lead. Interviews test vision for the function, operating model design, hiring and capability building, technology and tool choices, budgeting and how analytics drives company decisions. Expect deep discussion of past transformations and how you measured and communicated their value.
This set is weighted towards Process Modelling and BPMN (7), Business Metrics and KPIs (5), UAT and BA Documentation (5), Stakeholder Communication (5).
Function vision and operating model Hiring and capability building Business transformation outcomes Executive communication
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
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.
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.
03
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.
04
Because of a tight deadline, the business sponsor wants to skip UAT and go live directly. How do you respond?
Explain the risks in business terms: without UAT, there is no evidence that real processes work, and production defects cost far more to fix and can affect customers and compliance. Offer alternatives: a shortened UAT covering only critical business flows, parallel running with the old system, a phased rollout to one branch or user group, or extended hypercare. If the sponsor still decides to skip it, record the decision and accepted risks formally.
05
What is process mining and how does it help a business analyst?
Process mining uses event logs from systems such as ERP or CRM, each record holding a case ID, activity name and timestamp, to automatically rebuild how a process really runs. It shows actual paths, rework loops, bottlenecks and how often cases deviate from the designed flow. For a BA it replaces opinion-based AS-IS workshops with evidence, for example showing that 22 percent of purchase orders are changed after approval. Data quality of the logs is the main limitation.
IRR (internal rate of return) is the discount rate at which a project's NPV becomes zero, so it expresses the return as a percentage. NPV gives the value created in rupees at a chosen discount rate. Accept a project if IRR exceeds the cost of capital or NPV is positive. When comparing projects of different size or timing, NPV is more reliable, because IRR ignores scale and can give multiple answers when cash flows change sign more than once.
07
Vendor A has a lower licence price, but Vendor B has lower running costs. How do you compare them?
Compare total cost of ownership over the same period, usually 3 to 5 years. Include licence or subscription fees, implementation, data migration, integration, training, internal staff time, infrastructure, support and upgrade costs, and exit costs. Discount the yearly totals to present value if the timing differs. Then weigh the result against non-cost factors such as fit to requirements, scalability and vendor stability. Often the cheaper licence ends up costlier once customisation and support are added.
08
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.
09
What is an event-based gateway and when would you use it?
An event-based gateway is a decision point where the path is chosen by whichever event happens first, not by a data condition. It is followed by intermediate catching events such as a message or a timer. Example: after sending a quotation, either the customer's acceptance message arrives, or a 7-day timer fires and a reminder is sent. It models real waiting situations that an exclusive gateway cannot express correctly.
10
What is the difference between bookings, billings and revenue?
Bookings are the value of contracts signed in a period, showing future commitment. Billings are the amounts invoiced to customers in the period. Revenue is what is earned and recognised under accounting rules as the service is delivered. Example: a 3-year contract worth 36 lakh signed in April is 36 lakh in bookings, 12 lakh in billings if invoiced annually, and only 1 lakh in revenue for April. Confusing them is common when reporting sales performance.
11
Your TO-BE process cuts the account-opening cycle time by half, but the compliance team rejects it. How do you handle it?
Ask compliance which specific controls they believe are weakened, and map each regulatory requirement to steps in the old and new flows. Often the control can be kept in a different form, such as automated checks, risk-based sampling or a post-approval audit instead of a manual pre-check. Bring compliance into the redesign rather than presenting a finished model. Document the agreed controls in the TO-BE diagram so audit can trace them. Speed never overrides a mandatory control.
12
How do you manage conflicting requirements from two senior stakeholders?
Clarify the underlying goals, present data and trade-offs, facilitate a joint session, escalate to the sponsor if needed and document the agreed decision.
13
Marketing and product teams define 'active user' differently and report conflicting numbers. How do you fix this?
Bring both teams together and list each definition, its purpose and its numbers. Agree on one company-wide definition tied to real value, such as a user who completed a core action in the last 7 days, and allow clearly named secondary metrics like 'visitors' for marketing. Assign an owner, document it in a metric glossary, implement it once in the warehouse or semantic model, and retire the duplicate dashboards.
14
Managers want to click a region on a summary report page and jump to a detail page for only that region. How do you build it in Power BI?
Use drill-through. Create a detail page, add the Region field to the page's drill-through filter well, and design visuals for orders, products and trends. Power BI adds a back button automatically. On the summary page, users right-click a region and choose Drill through. Keep all filters on so date selections carry over. For guided navigation, you can also add buttons with bookmarks, but drill-through is the cleanest way to pass the selected region.
The team built what was written, but not what users needed, which points to gaps in elicitation, missing real-world scenarios or users not involved early. Capture each rejection and classify it as a defect, a missed requirement or a new request. Prioritise blockers with the product owner and agree on a fix plan and date. Going forward, involve users in demos every sprint and base UAT scenarios on real workflows.
17
Developers say a requirement is not technically feasible, but the business insists on it. How do you mediate?
Get to the underlying business goal behind the requirement, because the goal is often achievable in another way. Ask developers to explain the constraint and the cost of alternatives. Bring both sides together with options: a simpler version, a phased delivery, a manual workaround or a different design. Show effort, risk and value for each, and let the product owner or sponsor decide. Document the decision.
18
What is a cutover plan and a go-live readiness checklist?
A cutover plan is an hour-by-hour runbook for moving from the old system to the new one: freezing old transactions, final data migration, validation checks, configuration, smoke testing, switch-over and a rollback plan with clear decision points. A go-live readiness checklist confirms that UAT is signed off, users are trained, support and hypercare are staffed, data is reconciled, and communications are sent. The go or no-go meeting reviews this checklist before the cutover starts.
19
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;
20
What is operational acceptance testing and how is it different from UAT?
Operational acceptance testing (OAT) checks whether the operations and support teams can run the system in production: backup and restore, failover, monitoring and alerts, batch job scheduling, performance under expected load, security patching and support procedures. UAT checks whether business users can do their work. Both are needed before go-live. A system can pass UAT and still fail in production if nobody tested that the nightly batch finishes before the business opens.
21
How do sample size and minimum detectable effect affect an A/B test design?
The minimum detectable effect is the smallest lift worth detecting, such as a 2 percent relative increase in conversion. Smaller effects, lower baseline rates and higher required power need much larger samples, roughly four times the users to detect half the effect. Calculate sample size before starting using the baseline rate, MDE, significance level and power, usually 80 percent, then fix the test duration and avoid stopping early.
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.
23
Guesstimate: how many cars are sold in India every year?
Structure it: households × car-owning share ÷ replacement cycle + first-time buyers + commercial fleet. State each assumption clearly and sanity-check the final number.
24
What are MRR and ARR, and how do you calculate net revenue retention?
MRR is monthly recurring revenue from active subscriptions; ARR is the annualised figure, usually MRR times 12. Net revenue retention measures revenue kept from an existing customer cohort over 12 months: (starting MRR + expansion - contraction - churned MRR) / starting MRR. Example: 100 lakh start, plus 15 expansion, minus 5 contraction, minus 8 churn gives 102 percent. Above 100 percent means existing customers grow revenue even without new sales.
25
Tell me about a time you led or mentored a team of analysts.
Situation: I led three junior analysts on a pricing review with a six-week deadline. Task: deliver quality work while developing them. Action: I split the work by workstream, set up short daily check-ins and a shared query library, reviewed their logic rather than rewriting it, and let each present their section to the client. Result: we delivered a week early, two juniors later handled client calls alone, and the review practice became standard in our team.
26
A feature was launched to all users at once without an A/B test. How would you measure its impact?
Use quasi-experimental methods. Compare before and after with enough history to account for trend and seasonality. If it rolled out at different times in regions or platforms, use difference-in-differences between early and late groups. Compare users who adopted with similar non-adopters using matching, while being careful about self-selection. For future launches, recommend keeping a small holdout group so impact can be measured cleanly.
27
Tell me about a time you misunderstood a requirement. What did you learn?
Situation: I was asked for 'monthly active customers' and built it on login data. Task: deliver the report for a review. Action: in the demo, the stakeholder said active meant customers who purchased, not logged in. I owned the mistake, rebuilt the measure in two days and wrote down the definition for sign-off. Result: the report was accepted, and now I always confirm definitions and sample outputs with stakeholders before building anything.
28
Leadership wants to automate an invoice approval process with RPA. What do you check in the process model before agreeing?
Check that the process is stable, rule-based and high volume, with structured digital inputs. Look at the variant rate: if half the cases are exceptions handled by judgement, a bot will fail often. Verify that the underlying systems and screens will not change soon. Fix the process first, because automating a broken flow only makes errors faster. Finally estimate hours saved against bot build and maintenance cost, and define how exceptions get routed to people.
29
Write a SQL query to calculate monthly customer churn rate for a subscription business.
WITH monthly AS (
SELECT DISTINCT customer_id,
DATE_TRUNC('month', billing_date) AS month
FROM subscriptions_billed
)
SELECT
prev.month AS month,
COUNT(prev.customer_id) AS customers_at_start,
COUNT(prev.customer_id) - COUNT(nxt.customer_id) AS churned,
ROUND(100.0 * (COUNT(prev.customer_id) - COUNT(nxt.customer_id))
/ COUNT(prev.customer_id), 2) AS churn_pct
FROM monthly prev
LEFT JOIN monthly nxt
ON nxt.customer_id = prev.customer_id
AND nxt.month = prev.month + INTERVAL '1 month'
GROUP BY prev.month
ORDER BY prev.month;
30
What is the answer-first or pyramid principle approach to presenting analysis?
Start with the main conclusion or recommendation, then give the two or three supporting reasons, and only then the detailed data. Senior stakeholders have little time, so a summary like 'Churn rose because of payment failures; fixing retries can save 4 lakh a month' should come first. Detail goes in the appendix. It is the opposite of a chronological walk through every step of the analysis.
31
What is incremental refresh and when do you need it?
Incremental refresh partitions a large table by date so each refresh reloads only recent data, such as the last 10 days, while older partitions stay stored. You define RangeStart and RangeEnd parameters in Power Query, filter the date column with them, and set the policy for how much history to keep. It is needed when full refreshes of millions of rows take too long or fail, and it reduces load on the source system.
Situation: our company was replacing its loan origination system across five business units. Task: lead requirements with two other BAs in three months. Action: I set up a stakeholder map, ran structured workshops per unit, used shared templates and a traceability matrix, and held weekly review checkpoints with the sponsor to resolve conflicts quickly. Result: requirements were signed off on time, change requests in build stayed low, and the template was reused for later projects.
34
What is root cause analysis and which techniques do you know?
Find out whether it is a discovery problem or a value problem. Check how many users saw the entry point, how many tried it and how many returned. If few saw it, test better placement or onboarding prompts. If many tried and few returned, interview users and review session recordings to understand why. Also check if the 4 percent are high-value users. Then decide to improve, reposition or remove it.
36
A project's business case promised 30 percent cost savings, but after go-live only 10 percent is realised. What do you do?
Run a benefits review against the original baseline and assumptions. Check whether savings depended on actions that did not happen, such as reducing manual roles, retiring the old system or full user adoption. Check whether the baseline or volumes changed. Separate delayed benefits from lost ones. Then produce a recovery plan with owners, for example decommissioning the legacy licence or driving adoption. Also feed the lessons into how future business cases estimate benefits.
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.
38
Five departments each build their own Power BI reports with different revenue numbers. How would you design a better BI setup?
Create a shared, certified semantic model with one definition per KPI, built on a governed warehouse layer. Departments build thin reports on top of it through live connection instead of copying data. Set up workspaces by environment (dev, test, prod), deployment pipelines, naming standards, a KPI glossary and owners for each measure. Keep a small central team for the core model and let departments self-serve on top, which balances control and speed.
39
Write a DAX measure that shows each category's percent share of total sales.
ROI (return on investment) is the gain from a specific investment divided by its cost and is used to judge projects or campaigns. ROE (return on equity) is net profit divided by shareholders' equity and shows the return to owners; high debt can inflate it. ROCE (return on capital employed) is EBIT divided by equity plus long-term debt and shows how efficiently all long-term capital is used. ROCE is better for comparing companies with different debt levels.
Frequently asked questions
What is asked in Business Analytics interviews for 10+ years of experience?
At ten years, roles are usually head of business analysis, analytics director or practice lead. Interviews test vision for the function, operating model design, hiring and capability building, technology and tool choices, budgeting and how analytics drives company decisions. Expect deep discussion of past transformations and how you measured and communicated their value.
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 10+ years of experience?
Focus first on Function vision and operating model, Hiring and capability building, Business transformation outcomes, Executive communication.