Top 50 Most Asked Business Analytics Interview Questions

Escalate immediately to the business sponsor with the impact: each day without testers delays sign-off and go-live. Ask for named testers with protected time, even part-time. Meanwhile, prepare so no time is lost: finalise test cases, check the environment and data, and plan a short tester briefing. If testers cannot be released, propose re-planning UAT dates rather than letting IT or the BA test on the business's behalf, because acceptance must come from the users.

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.

Use FORECAST.ETS or a trendline on monthly history, check seasonality, compare with a simple moving average and present a range, not a single number.

Break sales into footfall, conversion and average basket, compare with last year and competitors, and check stock, pricing, staffing and local events.

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.

Log the change, assess impact on scope, cost and timeline, get approval through change control or backlog grooming, and update documents and stakeholders.

Aggregate revenue per month and use LAG(revenue) OVER (ORDER BY month) to compute (revenue - previous) / previous.

Growth came from more value per customer, not more customers. Break revenue into customers times orders per customer times average order value to see which moved. It could be price increases, larger baskets, a shift to premium products or a few large accounts. Then check risks: is new customer acquisition stalling, is churn being masked, and is growth concentrated in a small segment that could leave?

Population about 20 million, adult tea drinkers about 50%, cups bought outside per person around 1 on average. This gives roughly 10 million cups, then adjust for offices and stalls.

Top-down: two-wheeler market x EV share x addressable segment. Bottom-up: target households x adoption rate x price. Compare both for a sanity check.

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.

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.

Check the refresh history error first: expired credentials, gateway offline, source schema change or timeout. Fix the quick cause and trigger a manual refresh. If it cannot be fixed in time, inform the stakeholders early, state the last refreshed date clearly on the report and share the key numbers from a direct query if needed. Afterwards add refresh failure alerts and a data-as-of label so it never surprises anyone.

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.

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.

Standardise both first: trim spaces, fix case, convert IDs to the same type and remove duplicates. Use a unique key like customer ID, or a combined key of phone and email if IDs differ. Then use XLOOKUP or COUNTIFS to mark each record as matched, only in sales or only in billing, or a Power Query merge with anti joins. Summarise mismatches by type and share the exception list with both owners.

Users are coming but not completing transactions, so look at the gap. Possible causes: a release that broke a payment flow, new security steps like extra OTPs adding friction, logins driven by balance checks or offers, or transactions shifting to another channel. Compare the funnel from login to transaction by app version and device, check failure and error rates, and review support complaints before recommending fixes.

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.

Go back to the requirement and acceptance criteria. If the system matches the agreed requirement, the developer is right, and the business need is a change request. If the requirement is unclear or the design misread it, it is a defect, and the requirement wording should be fixed. Discuss it in triage with both parties, using examples. Either way, close the loop with the tester so they understand the outcome and keep trusting the process.

Identify which documents are actually used: usually a product overview, process maps, business rules, data dictionary and integration details. Update those first rather than everything. Make documentation part of the Definition of Done, so a story is not complete until related docs are updated. Keep living documents in a shared wiki with owners and last-reviewed dates, and archive outdated files clearly. Test the result by having a new joiner use it during onboarding.

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.

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.

Use tables, Power Query, remove volatile functions, filter before calculating and move to Power Pivot or a database when rows reach the millions.

Top-down: NCR population aged 18–30 × share of graduates × share wanting paid upskilling × average fee. Cross-check bottom-up with institutes × batches × students × fees. State your assumptions.

First agree on the definition: date range, gross or net, tax, returns, currency and which date (order or invoice) is used. Then reconcile at a small grain, such as one month and one region, comparing row counts and sums between the source query and the sheet. Common causes are filters on the page, missing relationships, duplicate rows after a join or a late refresh. Document the agreed definition in the report tooltip.

Ask what decisions they make weekly and which three to five KPIs drive them. Propose a summary page with those KPIs, trends and one breakdown, then drill-through or separate pages for detail. Show a quick mock-up of both versions so they see the clutter and the load time. Use bookmarks or a field parameter to let them switch views without adding charts. Agree on the layout before building.

NFR-01 Performance: the payment page loads within 2 seconds for 95 percent of requests at 500 concurrent users. NFR-02 Availability: 99.9 percent monthly uptime outside planned maintenance. NFR-03 Security: card data is never stored by the application, and all traffic uses TLS 1.2 or higher. NFR-04 Compliance: the flow meets PCI DSS and RBI payment guidelines. NFR-05 Usability: works on mobile screens from 360 pixels wide. NFR-06 Audit: every transaction attempt is logged with a timestamp.

Compare against the baseline you measured before the change, using the same definitions: cycle time, first-time-right rate, cost per case, backlog and customer complaints. Pull data from system timestamps rather than surveys. Check that the gain is not explained by lower volumes or seasonality, ideally by comparing similar periods. Also check for side effects, such as faster processing but more rework downstream. Present the before-and-after with the business owner, and note where adoption is still incomplete.

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.

Demand: population density, smartphone and digital payment penetration, average basket size and how often people buy groceries. Supply: dark store rent, rider availability and local sourcing. Unit economics: orders per store per day needed to break even, given lower average order values. Competition: local kirana delivery and other apps. Then propose a pilot in two or three cities with clear success metrics such as orders per day, contribution margin per order and repeat rate before scaling.

Usually rounding. Excel may display rounded values while summing the full-precision numbers, or line items were rounded individually in the source system and the total was computed differently. Check whether finance rounds each invoice line before summing, and apply ROUND at the same level in Excel. Other causes include floating-point artifacts, values stored as text being skipped by SUM, or hidden filtered rows. Agree and document one rounding rule with finance.

Map the steps first: which files arrive, what cleaning is done and which outputs are needed. Move the import and cleaning into Power Query so a refresh replaces copy-paste. Base calculations on Excel Tables and PivotTables that update automatically, and keep a fixed template for the output. Use a small macro or Office Script only for the remaining formatting or emailing. Add checks such as row counts and totals so errors surface quickly.

The story is ambiguous, so bring the three amigos together: BA or product owner, a developer and a tester. Walk through concrete examples, including edge cases and error cases, and write them as acceptance criteria, ideally in Given-When-Then format. Add business rules, sample data and mock-ups where needed. Update the story and use the same practice in refinement for future stories, so gaps are found before coding starts.

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.

A sequence flow is a solid arrow that shows the order of activities inside one pool, so it represents work controlled by one participant. A message flow is a dashed arrow with an open circle at its start and shows communication between two different pools, such as an order email from a customer to a seller. A common modelling mistake is drawing sequence flows across pools, which wrongly implies one party controls the other's work.

First measure each handoff: waiting time, rework rate and volume, using system timestamps where possible. Then classify steps as value-adding, required for compliance or waste. Look for patterns: repeated approvals, information re-entered in two systems, work bouncing back for missing documents. Typical fixes are merging roles, adding a checklist at intake so applications arrive complete, parallelising checks and automating rule-based approvals. Quantify the expected reduction in cycle time for each option.

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.

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.