LinkedIn Business Analytics Interview Questions & Answers

Goal Seek (find the input for a target output), Data Tables (see outputs for many inputs) and Scenario Manager (save best, base and worst cases).

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

Clear, testable conditions a story must meet to be accepted, often written as Given-When-Then scenarios.

Waterfall runs fixed phases one after another with requirements frozen early. Agile delivers in short sprints with continuous feedback, so requirements can change. In Agile, BAs maintain the backlog and user stories.

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.

Both look up values flexibly; XLOOKUP is simpler with built-in not-found handling, while INDEX-MATCH works in older Excel versions.

SUM(sales) per category divided by SUM(SUM(sales)) OVER () and multiplied by 100 gives each category's share of the total.

Define a goal metric, a baseline and guardrail metrics, run an experiment or before-after comparison and review adoption, retention and revenue impact.

GROUP BY aggregates rows by column; WHERE filters before grouping and HAVING filters after, using aggregate conditions.

Break-even units = Fixed costs ÷ (Price − Variable cost per unit). Add a data table to test different price and volume scenarios.

Uncontrolled growth of requirements. Control it with a clear scope statement, change control process, impact analysis and sponsor approval for additions.

Separate inputs, calculations and outputs, link all formulas to input cells, add scenarios and checks, and avoid hard-coded numbers inside formulas.

An early assessment of whether a proposed solution is technically, economically, operationally and legally viable before committing budget.

INNER returns only matching rows; LEFT returns all rows from the left table and NULLs where there is no match.

Strengths and Weaknesses are internal; Opportunities and Threats are external. Example: S = strong faculty, W = low brand awareness, O = AI upskilling demand, T = free online content.

XLOOKUP can look left or right, uses exact match by default, returns a custom value if nothing is found and doesn't break when columns move. VLOOKUP only looks right and needs a column number.

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.

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

Map the funnel, find the biggest drop-off, check usability and load time, run A/B tests on fixes and track conversion lift.

VLOOKUP or XLOOKUP, INDEX-MATCH, SUMIFS, COUNTIFS, IF, text functions, PivotTables and charts.

Use MoSCoW (Must, Should, Could, Won't), value versus effort scoring or the Kano model, agreed with stakeholders based on business value and risk.

A short requirement written as 'As a user, I want X so that Y', backed by acceptance criteria. Good stories follow INVEST: independent, negotiable, valuable, estimable, small and testable.

Variance = Actual - Budget, shown as amount and percentage, with conditional formatting to flag large gaps and comments on the drivers.

A language for querying databases. BAs use it to pull data themselves, validate numbers, check reports and answer questions without waiting for engineers.

Compare the current state (as-is) with the desired state (to-be), list the gaps in process, people or technology, and plan actions to close them.

The product backlog is the ordered list of all desired work; the sprint backlog is the subset the team commits to in the current sprint.

Identifying everyone affected by the project and mapping their influence and interest to decide how to communicate with and involve each group.

A BA bridges business and technology: gathers requirements, analyses data and processes, documents BRD/FRD and makes sure the final solution actually solves the business problem.

A column or set of columns that uniquely identifies each row in a table and cannot contain NULL.

Functional requirements describe what the system does (login, reports); non-functional ones describe how well it does it (speed, security, availability, usability).

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

Anyone affected by or influencing the project: sponsors, product owners, end users, developers, testers, operations and customers.

The sales volume where total revenue equals total cost. It equals fixed cost divided by contribution margin per unit.

WITH m AS (SELECT month, SUM(amount) AS rev FROM orders GROUP BY month) SELECT month, rev, ROUND(100.0 * (rev - LAG(rev) OVER (ORDER BY month)) / LAG(rev) OVER (ORDER BY month), 1) AS mom_pct FROM m;

Use historical data with FORECAST.ETS or trend lines, state assumptions, compare against actuals and show best, base and worst scenarios.

Score them with RICE or value-vs-effort, align with goals, consider dependencies and risks, validate with stakeholders, then use MoSCoW for the release plan.

Interviews, workshops, surveys, observation, document analysis, prototyping and brainstorming, chosen according to stakeholders and project stage.

Stakeholders and the sponsor review the Business Requirements Document for completeness and accuracy, and the business owner gives formal sign-off before design begins.

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.

They help the Product Owner refine the backlog, write stories and acceptance criteria, clarify details with developers and support testing and demos.

A model assessing industry attractiveness through supplier power, buyer power, threat of new entrants, threat of substitutes and rivalry among competitors.

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 use case describes the full interaction between an actor and the system (main and alternate flows). A user story is a short statement of need from the user's point of view, refined with acceptance criteria.

OLTP handles many small day-to-day transactions; OLAP supports analysis over large historical data with aggregates and reporting.

A model classifying features as basic, performance or delight attributes based on how they affect customer satisfaction, helping decide what to build first.

Product, Price, Place and Promotion, the levers a business uses to bring an offering to market.

A query nested inside another, used for filtering or calculating values such as customers whose spend is above the average.

Reconcile totals with source tables using SQL, check filters and joins for duplication, compare with prior periods and verify with business owners.

A named temporary result introduced with WITH that makes long queries readable and reusable in the same statement.

About 20 million people, roughly 10% order pizza on a weekend, about 1 pizza per 2 people in an order. This gives roughly 1 million pizzas, adjusted for outlets and delivery capacity.

Clarify the scope, break the problem into logical parts, state assumptions with round numbers, compute step by step and sanity-check the answer.

A UML diagram showing actors and the actions (use cases) they perform with the system, giving a quick view of scope.