CRED Business Analytics Interview Questions & Answers

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.

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

Create a line or column chart of actuals and add the target as another series formatted as a line.

A BRD states what the business needs and why. An FRD details how the system should behave to meet those needs (functional specifications).

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

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

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

Testing how changes in key inputs such as price or volume affect the output, in Excel using data tables or scenario manager.

ROI = (incremental profit - campaign cost) / campaign cost. Measure incremental sales using a control group or before-after comparison.

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.

Fixed costs stay constant regardless of volume, such as rent; variable costs change with volume, such as raw materials.

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

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

Use STAR: Situation, Task, Action, Result. Show that you listened, found the underlying goal, used data to align people and reached a documented decision.

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

Look at the cost side: heavier discounts, higher CAC, logistics costs, product mix shifting to low-margin items, one-time expenses or pricing changes. Break contribution margin down by segment.

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.

An Excel add-in for building data models with relationships and DAX measures over millions of rows, beyond normal worksheet limits.

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.

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.

Check row counts against the source, nulls, duplicates on keys, value ranges, date coverage and that totals reconcile with finance reports.

Profit = Revenue minus Cost, where revenue = price x volume and cost = fixed + variable. Split each part to find which one explains a change.

Pareto principle: about 80% of outcomes come from 20% of causes, such as most revenue from a few customers or most defects from a few issues.

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

Check data accuracy, then segment by city, restaurant, time and user type; look at supply, delivery time, pricing, competitors and seasonality before proposing fixes.

Every KPI is a metric, but a KPI is tied directly to a strategic goal (e.g. monthly churn). A metric can be any measurement (e.g. page views).

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.

Assess market size and demand, customer need, competition, unit economics, capabilities, risks and strategic fit, then test with a pilot before scale-up.

Create a table, insert a PivotTable, drag region to rows, product to columns, sales to values, and add slicers for month or channel.

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

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

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.

As a customer, I want to reset my password by email so that I can get back into my account. Acceptance criteria: • Reset link expires in 15 minutes • Password rules are shown while typing • A success message appears after reset

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;

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

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.

Combine cost-plus, competitor benchmarks and willingness to pay from research, test tiers with experiments and check margin and churn impact.

Structure it: households × car-owning share ÷ replacement cycle + first-time buyers + commercial fleet. State each assumption clearly and sanity-check the final number.

Number of outlets x daily customers x average bill x operating days, then validate using footfall, peak hours and similar chains.

It returns a custom value when a formula errors out, keeping reports clean, for example =IFERROR(VLOOKUP(...), "Not found").

Low-fidelity layouts of screens that help stakeholders visualise and agree on requirements before development starts.

Clarify the underlying goals, present data and trade-offs, facilitate a joint session, escalate to the sponsor if needed and document the agreed decision.

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

Get distinct user-month pairs, self-join or use LAG on month per user, and keep rows where the previous month is exactly one month earlier.

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.

The total profit expected from a customer over the relationship, roughly average margin x purchase frequency x lifespan, compared with acquisition cost.

Functions that summarise rows into a value, such as COUNT, SUM, AVG, MIN and MAX.

A table linking each requirement to design, test cases and delivery status, ensuring nothing is missed and helping assess change impact.

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

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

Revenue is total money from sales; profit is what remains after subtracting all costs and expenses.

It breaks a top metric into drivers: Revenue = Users × Conversion × AOV; Users = New + Returning, and so on. It shows which lever to pull and where a drop came from.

A what-if tool that recalculates a formula for different inputs, for example loan payments across different rates and tenures.

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).

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

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

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

CAGR = (End value / Start value)^(1/years) - 1, entered as =(B2/A2)^(1/n)-1.

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

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

A measurable value showing progress to a goal, such as conversion rate, average order value, cart abandonment rate and customer retention.

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.

Define named scenarios such as best, base and worst with different input values and compare the outputs in a summary report.

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

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

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

Finding the underlying reason for a problem using the 5 Whys, fishbone diagrams or Pareto analysis, then fixing the cause not the symptom.

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.

A framework listing internal Strengths and Weaknesses and external Opportunities and Threats to assess a project or business position.

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

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

Check market size (population, online ordering share), competition, restaurant supply, unit economics per order, CAC and payback period. Propose a pilot with clear success metrics.

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.

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