Business Analyst Assessment Test 2026: SQL, Excel, Case Study & Prep Plan
If you've been asked to take a "business analyst assessment test" before your interview even gets scheduled, you're not imagining a new hurdle — it's now a standard part of the hiring funnel at most companies that hire business analysts, from Amazon and Capital One to Indian GCCs and consulting firms. This guide breaks down exactly what these tests cover, how they're scored, which companies use them, and how to prepare in the two weeks before yours.
Unlike a business analyst interview, which is a conversation, a business analyst assessment is a timed, scored exercise — usually SQL queries, an Excel/data task, logical reasoning, and a short business case — that happens before or alongside your interview loop. Passing the interview questions but bombing the assessment (or vice versa) is a common, avoidable way candidates get filtered out.
What a business analyst assessment test actually covers
Most business analyst assessments, whether administered through a vendor platform or built in-house, cluster around four areas:
- SQL fundamentals and querying. Expect 2–4 SQL problems of increasing difficulty: basic
SELECT/WHERE/GROUP BY, then multi-table joins, then window functions, subqueries, and aggregations against a messier schema. Amazon's BA assessment, for example, is well known for including SQL questions that test whether you can extract a specific business insight from raw tables rather than just write syntactically correct queries. - Excel and spreadsheet skills. Pivot tables, VLOOKUP/XLOOKUP, conditional formatting, basic statistical functions, and data cleaning tasks. Some platforms (Adaface and WeCP are two vendors many companies use) frame this as a timed practical test rather than multiple choice.
- Logical and quantitative reasoning. Data interpretation from charts and tables, basic probability, and case-style "which option is more efficient" questions, similar in format to what you'd see on aptitude tests like AMCAT or CoCubes but focused on business scenarios instead of pure math.
- A short business case or scenario. A prompt like "how would you improve customer retention" or "how would you decide whether to launch this feature," usually with a 60–90 minute window, sometimes as a written response and sometimes as a live case discussion folded into the interview itself.
How these tests are scored
Most vendor-administered assessments (think Adaface, WeCP, HackerRank-style platforms, or a company's in-house tool) score you on a mix of:
- Correctness — did your SQL query return the right result, did your Excel formula work, did your reasoning answer land on the right conclusion.
- Efficiency — cleaner, more optimized SQL (fewer nested subqueries, correct join types) and Excel approaches (using a pivot table instead of manual filtering) tend to score higher even when the final answer is the same.
- Business framing on the case portion — for the case study section, scorers are typically looking for structured thinking (clarify the problem, state assumptions, walk through a framework, land on a recommendation) more than a single "correct" answer.
A candidate who gets every SQL answer technically right but never explains their business reasoning on the case portion often scores lower than one with slightly rougher SQL but sharper business judgment — the test is trying to simulate the actual job, not just a coding screen.
Which companies use business analyst assessment tests
You'll run into a formal, timed assessment most often at:
- Large tech and e-commerce companies (Amazon, Flipkart, and similar product-based companies) as a pre-interview or first-round filter, frequently including a dedicated SQL section.
- Banks, NBFCs, and BFSI companies as part of a broader aptitude + domain knowledge screen, often bundled with the kind of assessments covered in our NBFC and fintech lending interview questions guide.
- Consulting and Big 4 firms, where a case-style written exercise frequently substitutes for (or precedes) a live case interview — see our Big 4 interview prep guide for how the case portion typically plays out.
- GCCs and IT services companies hiring for business/data analyst hybrid roles, often via the same assessment vendors used for their broader campus hiring (similar in spirit to CoCubes or AMCAT, but with a business-analyst-specific module layered on top).
Why this stage exists at all
Assessment platforms built specifically for this role, like Adaface's Business Analyst Test, explicitly cover "Worksheet and Charts, Operators, Excel Functions, Excel Formulas, Pivot tables, Data analysis, Data visualization, Conditional formatting, SQL Basics, SQL CRUD Queries, and Logical Reasoning" as a single, standardized module — which tells you what hiring teams have decided actually predicts on-the-job performance for this role. Interview guides like Indeed's business analyst interview questions reinforce the same pattern from the employer side: companies want proof of structured, data-literate thinking before they invest interviewer time in a conversation. Recruiters use a scored, standardized test earlier in the funnel for a simple reason: a 90-minute assessment can screen 50 candidates in parallel, while a live interview can only evaluate one person at a time. That's also why the same skills get tested twice — once quantitatively in the assessment, and again conversationally in the interview — rather than the assessment replacing the interview outright.
A realistic prep plan (10 days)
Days 1–3: SQL fundamentals refresh. Don't just review syntax — practice against messy, multi-table datasets. Focus on joins, GROUP BY with HAVING, window functions (RANK(), ROW_NUMBER(), running totals), and subqueries. Time yourself: most assessments give you 20–30 minutes for 2–4 queries, so speed matters as much as correctness.
Days 4–5: Excel practical drills. Rebuild a messy dataset into a clean pivot table, practice VLOOKUP/XLOOKUP and INDEX-MATCH cold, and get comfortable with conditional formatting and basic charting without hunting through menus. If your target company's assessment is Excel-heavy rather than SQL-heavy, weight your prep here instead.
Days 6–7: Logical and data-interpretation reasoning. Practice reading a chart or table quickly and answering "which of these four conclusions is actually supported by this data" style questions — this is closer to GMAT data sufficiency than pure math, so drill the format, not just the arithmetic.
Days 8–9: Case study structure. Practice a structured approach: clarify the goal, state 2–3 assumptions, walk through a simple framework (e.g., break the problem into acquisition/retention/monetization, or cost/benefit), and land on a clear recommendation with a stated trade-off. Use ClavePrep's mock interview from a job posting tool to generate a realistic case-style prompt tied to the actual role you're applying for.
Day 10: Full timed run-through. Simulate the whole assessment — SQL, Excel, reasoning, and case — back to back under the real time limit, ideally the day before or two days before your actual test, so the format isn't a surprise.
A worked example: what an Amazon-style SQL question actually looks like
Most candidates underestimate how much of the difficulty in these tests comes from ambiguity in the business question, not the SQL syntax itself. A typical prompt might read: "Given an orders table (order_id, customer_id, order_date, amount) and a customers table (customer_id, signup_date, region), find the second-highest order amount for each customer in the last 90 days." The syntax challenge (a window function like DENSE_RANK() OVER (PARTITION BY customer_id ORDER BY amount DESC)) is the easy half. The harder half is noticing the unstated constraints: does "last 90 days" mean from today or from the query's reference date, should customers with only one order return null or be excluded, and does "second-highest" mean second-highest distinct amount or second row overall if there are ties? Strong answers explicitly state these assumptions in a comment before writing the query. Weak answers write technically correct SQL against the wrong interpretation of the question and lose most of the credit anyway. This is exactly why assessment scorers weight reasoning and assumption-stating as heavily as raw syntax: it's a proxy for how you'll behave in the job, where the business question is almost never fully specified up front.
The same pattern shows up in Excel sections. A prompt asking you to "identify which product category is underperforming" is rarely solved correctly by only building a pivot table — it requires you to also decide what "underperforming" means (below category average? below last quarter? below plan?) before the pivot table output means anything. Treat every seemingly mechanical task as a mini business case with an implicit question behind it.
How assessment difficulty scales with seniority
Entry-level and associate business analyst assessments typically stay close to the fundamentals: single or two-table joins, basic pivot tables, and a straightforward case with an obvious framework fit (cost-benefit, or a simple funnel breakdown). Mid-level and senior business analyst assessments raise the bar in three specific ways: the SQL problems involve three or more tables with intentionally messy joins (duplicate keys, null foreign keys), the Excel tasks expect you to build something reusable (a templated pivot or a small dashboard) rather than a one-off answer, and the case portion drops the obvious framework fit, forcing you to construct your own structure rather than plug numbers into a textbook framework. If you're targeting a senior or lead BA role, spend proportionally more of your 10-day plan on unstructured case practice and less on SQL syntax drilling, since syntax fluency is assumed at that level and structured judgment is what actually differentiates candidates.
Business analyst vs. data analyst assessments: what's different
The two roles' assessments overlap heavily on the SQL and Excel sections, but diverge on the case and reasoning components. A data analyst interview and its associated assessment lean harder into statistical reasoning, larger and messier datasets, and sometimes a basic Python or R component for candidates at data-heavy companies. A business analyst assessment leans harder into the business case and stakeholder-communication angle — the SQL and Excel sections exist to prove you can get to the data, but the scoring weight sits more on what you do with the answer than on the analytical technique itself. If you're applying to hybrid roles that could be titled either way, prepare for whichever the job description's SQL/Excel expectations suggest is heavier, and default to over-preparing the business case structure regardless, since it rarely hurts and is the piece candidates most often under-practice.
Sample question types to practice
- Write a SQL query to find the second-highest order value per customer using a window function.
- Given a sales table with duplicate and missing entries, describe (or execute) the steps to clean it before analysis.
- A pivot table shows region-wise revenue is up but region-wise margin is down — what are three hypotheses you'd investigate first, and how would you test each one?
- You have 45 minutes: should the company launch a new feature to reduce churn, or invest in acquisition instead? Structure your answer.
- Interpret a funnel chart with drop-off at each stage and identify the highest-leverage stage to fix first.
Common mistakes candidates make
- Treating it like a pure coding test. Interviewers reviewing your assessment care as much about why you approached a query or case the way you did as whether the final number is right. Narrate your reasoning if there's any free-text or comments field.
- Ignoring time budgets. Spending 25 of your 30 SQL minutes on the first "easy" question and rushing the harder ones is one of the most common ways candidates lose points, even when every individual answer would have been correct with more time.
- Skipping the business case section because it feels "soft." It's usually weighted as heavily as the technical sections, and a structured, confident answer with reasonable assumptions almost always beats a technically perfect SQL query paired with a rushed, unstructured case response.
- Not clarifying ambiguous prompts. On live or semi-live case portions, asking one or two clarifying questions before diving in (What's the current retention rate? What's the budget?) signals the structured thinking the test is actually trying to measure.
- Under-practicing Excel because "everyone knows Excel." Timed, judged Excel tasks (build this pivot table in 10 minutes, clean this dataset) trip up plenty of otherwise-strong candidates who haven't done it under time pressure recently.
- Forgetting to sanity-check outputs. A SQL query that runs without an error isn't the same as a query that answers the actual business question — always eyeball the row count and a few sample rows before submitting, since an obviously wrong result (negative revenue, duplicated rows from an unintended join) is a red flag scorers specifically look for.
- Over-relying on a single memorized framework for every case. Reusing the exact same case-interview framework regardless of the prompt (forcing every question into a "cost vs. benefit" template, for instance) reads as rote memorization rather than genuine business judgment. Adapt the structure to the specific question instead of forcing the question to fit a template you rehearsed.
Once you've cleared the assessment, the interview itself will draw heavily on the same fundamentals in conversational form — our business analyst interview questions guide covers the most common questions companies ask in the interview rounds that typically follow.
What happens after you pass the assessment
Passing the assessment typically moves you into two or three interview rounds: a hiring-manager round that revisits your assessment answers in conversation (be ready to explain your SQL logic and case assumptions out loud, since interviewers frequently ask "walk me through why you approached it this way"), a stakeholder or cross-functional round testing communication and influence rather than technical depth, and sometimes a final round with a senior leader focused on judgment and prioritization. Because the assessment and interview test overlapping skills from different angles, the strongest prep strategy treats them as one continuous funnel rather than two separate hurdles — the reasoning you practice for the case section is the same reasoning you'll be asked to narrate live a few days later.
Logistics: what to expect on test day
Most vendor-hosted assessments (Adaface, WeCP, HackerRank-style platforms, or a company's own portal) run in-browser with a live code editor or spreadsheet embed, a visible countdown timer, and no ability to pause once started. A few practical notes that trip up otherwise well-prepared candidates: confirm whether the platform requires a specific browser or extension before your scheduled slot, check whether scratch paper or a local spreadsheet is allowed for working through the case section, and read the full instructions once before starting any section, since some platforms let you move between SQL, Excel, and case sections freely while others lock you into a strict linear order. If the assessment is proctored (webcam-monitored), test your camera and lighting in advance — a failed proctoring check can cost you meaningful time out of a tight window.
Frequently asked questions
What is a business analyst assessment test?
It's a timed, scored pre-interview or first-round exercise — typically covering SQL, Excel/spreadsheet tasks, logical reasoning, and a short business case — used to filter business analyst candidates before or alongside the interview loop.
How long does a business analyst assessment test take?
Most run 60–90 minutes total, sometimes split into a shorter SQL/Excel section (20–30 minutes) followed by a case study or reasoning section, though exact timing varies by company and vendor.
Do all companies require a business analyst assessment test?
No. Large tech, e-commerce, BFSI, and consulting firms use them most consistently. Smaller companies and startups more often skip the formal assessment and evaluate the same skills conversationally during the interview.
Is SQL required for a business analyst role?
Increasingly, yes, especially at data-heavy companies. Even roles that don't require you to write production SQL day-to-day often test basic-to-intermediate SQL as a proxy for structured, logical thinking about data.
What's the difference between a business analyst assessment test and business analyst interview questions?
The assessment is a timed, scored exercise (SQL, Excel, reasoning, case), usually completed independently before or alongside interviews. Interview questions are conversational and probe your experience, judgment, and communication — see our business analyst interview questions guide for the full list of what's typically asked.
Can I use a calculator or reference material during the assessment?
This varies by vendor and company; some open-book, browser-based assessments allow you to look up syntax, while proctored ones may not. Always check the instructions provided with your specific test link before assuming either way.
How should I prepare if I only have two or three days before my assessment?
Prioritize a fast SQL syntax refresh (joins, GROUP BY, window functions), one timed Excel pivot-table drill, and one practice business case done under a strict time limit — in that order, since SQL and Excel sections are usually weighted most heavily on tech and e-commerce assessments.
Does ClavePrep help with business analyst assessment prep?
ClavePrep's mock interview tools can generate role-specific practice questions from an actual business analyst job description, and the STAR Builder helps you structure clear, framework-driven answers for the business case portion, which carries over directly into how you'll be expected to communicate in the interview rounds that follow. See how ClavePrep's process works to get started.
What score do I need to pass a business analyst assessment test?
There's no universal cutoff — it varies by company, role level, and how the vendor's platform normalizes scores against other candidates in the same hiring window. As a practical target, aim to answer SQL and Excel sections with both correctness and reasonable efficiency (not just a brute-force working answer), and treat the case section as pass/fail on structure: a clearly stated assumption, a simple framework, and a defensible recommendation will usually clear the bar even if a rater might have chosen a different final answer than yours.
Should I practice on the same platform the company uses (Adaface, WeCP, HackerRank)?
It helps but isn't essential. The underlying skills — SQL joins and window functions, Excel pivot tables and lookups, structured case reasoning — transfer across platforms. If you know in advance which vendor a company uses, doing one timed practice run on that exact platform removes any interface-related surprises, but spending most of your prep time on the underlying skills rather than platform familiarity is the better trade-off with limited time.
