How it worksPricingInterview questions
Accenture · Data Analyst

Accenture Data Analyst Interview Questions (2026): process, questions and answers

Updated 22 October 2026 · prep guide

Accenture Data Analyst interviews usually focus on practical SQL, reporting, dashboarding, data cleaning, and business thinking. Use this page to practise short, clear answers that connect technical choices to business impact, especially in consulting and client-facing scenarios.

Preparing for Accenture? Rehearse these questions with Interview AI Helper: ask any question and get a suggested answer in seconds, written from your own resume.

Free 5-minute demo

How the Accenture Data Analyst interview usually works

  1. Recruiter screen: Candidates commonly report a short screening focused on your resume, communication, location flexibility, and basic fit for data work. Be ready to explain your projects clearly and mention the tools you used, the business problem, and the result.
  2. Technical interview: This stage usually checks SQL, Excel, Power BI or Tableau, basic statistics, and data quality thinking. Expect live questions where you explain your logic, not just the final answer.
  3. Case or scenario discussion: You may be asked how you would analyse a business problem, find the right metrics, or diagnose a report issue. A strong answer shows structure, assumptions, and how you would communicate findings to stakeholders.
  4. Manager or panel conversation: The discussion often goes deeper into project handling, priorities, stakeholder management, and how you work with imperfect data. Keep answers practical and show that you can support delivery in a client environment.

Technical questions and answers

How do you decide whether to use INNER JOIN or LEFT JOIN in a reporting query?

Use INNER JOIN when you only want rows that exist in both tables, for example valid orders with matching customer records. Use LEFT JOIN when you want all rows from the main table, even if the other table has no match. In reporting, LEFT JOIN is useful when you want to keep all transactions and show missing reference data as NULL. The choice depends on whether missing matches should be excluded or kept for analysis.

What problem does COALESCE() solve in SQL?

COALESCE() returns the first non-NULL value from a list, so it helps you replace missing values with a default. For example, COALESCE(discount, 0) makes calculations safer when discount is missing. In reporting, it is useful for cleaner output and fewer NULL values in dashboards. I would use it carefully, because replacing missing data with a default is a business choice, not just a technical one.

How would you get the previous month’s sales for each month in SQL?

I would use a window function like LAG() ordered by month. For example, LAG(sales) OVER (ORDER BY month) gives the prior row’s sales, which is useful for month-over-month analysis. If the data is by customer or region, I would add PARTITION BY so the comparison stays within each group. This is better than self-joining when the goal is a simple time-based comparison.

What is the difference between a CASE statement and a lookup table in SQL?

A CASE statement is best for small, stable business rules, like classifying customers into High, Medium, or Low segments. A lookup table is better when the mapping is larger, changes often, or needs business ownership. In a client environment, lookup tables are easier to maintain and audit. I would use CASE for quick logic in analysis, but prefer a reference table for production reporting.

How do you handle data type mismatches when joining tables in SQL or cleaning data in Excel?

First, I check whether the join keys have the same type and format, such as text versus number or date versus text. In SQL, I may use CAST() or CONVERT() carefully, after checking for leading zeros or non-numeric characters. In Excel, I would clean spaces, hidden characters, and inconsistent formats before matching. The main goal is to avoid silent mismatches that create missing rows or incorrect joins.

Interview with Accenture coming up?

Practise these Data Analyst questions out loud and get suggested answers in real time, based on your own resume. Free 5-minute demo, no subscription.

Try the free demo

How would you use a pivot table to analyse a large dataset in Excel?

I would first make sure the data is clean, with one row per record and clear headers. Then I would use a pivot table to quickly summarise by dimensions like month, region, customer type, or product. I would add values such as sum, count, or average, and then apply filters to compare segments. Pivot tables are useful because they let you explore trends fast without changing the source data.

How do you choose the right chart type in Power BI or Tableau?

I choose the chart based on the question. Use a line chart for trends over time, bar charts for comparing categories, and scatter plots for relationships between two numeric variables. If the goal is a KPI summary, cards and gauges can help, but they should not overload the report. A good chart should make the point quickly, use clear labels, and avoid unnecessary decoration.

What is DISTINCT in SQL, and when should you avoid using it?

DISTINCT removes duplicate rows from the result set, so it is useful when you need unique values. But I would avoid using it as a fix for a bad join or messy data, because it can hide underlying issues. If duplicates appear unexpectedly, I would first check the data model and join conditions. DISTINCT is fine for summarising unique entities, but it should not replace proper data quality checks.

How do you test whether a dashboard metric is accurate?

I would verify the metric from the source table up to the final visual. That means checking filters, date logic, joins, aggregation level, and any transformations used in Power Query or SQL. I would compare the dashboard number with a small manual extract to confirm the calculation. If possible, I would test edge cases like missing values, duplicates, and boundary dates. Accuracy comes from tracing the full data path, not just the final chart.

How do you explain a moving average in simple terms?

A moving average smooths short-term fluctuations by averaging values across a fixed recent period, such as the last 7 days or 3 months. It helps show the underlying trend more clearly. For example, if daily support tickets vary a lot, a moving average makes it easier to spot whether the volume is really rising or falling. It is useful for trend reporting, but it does not replace the original data.

Scenario questions

A client says a weekly operations report shows fewer active cases than last week. How would you investigate?

I would start by confirming the business definition of an active case, because the issue may be in the logic rather than the data. Then I would check source refresh timing, filters, joins, duplicate records, and any status changes that could move cases out of scope. I would compare this week and last week at a record level, identify the main drivers, and then explain whether the change is real or caused by a reporting issue.

You are asked to analyse delayed invoice payments for a finance team. What would you do first?

I would first understand how delayed payment is defined, for example due date minus payment date, and whether partial payments matter. Then I would segment by customer, region, invoice value, and aging bucket to find patterns. I would also check if delays are linked to invoice errors, approval issues, or specific client groups. Finally, I would present the findings with a clear recommendation, such as which segment needs follow-up first.

A dashboard used by managers is slow and hard to read. What improvements would you suggest?

I would check both performance and design. For performance, I would reduce unnecessary visuals, simplify calculations, and limit high-cardinality fields where possible. For usability, I would focus the page on key KPIs, use consistent labels, and keep filters limited to what managers actually need. I would also make sure the dashboard tells a story, with summary at the top and drill-down details below. The goal is faster decisions, not more charts.

HR and behavioural questions

Tell me about yourself.

Structure it as present, past, and future. Start with your current role or education, then briefly mention relevant data skills like SQL, Excel, dashboarding, and analysis projects, and end with why this role fits your next step. A short sample answer: "I work on data analysis and reporting, where I clean data, build summaries, and support business decisions. I have hands-on experience with SQL, Excel, and BI tools. I am now looking for a consulting environment where I can work with clients and solve business problems at scale."

Describe a time you found a data issue and how you handled it.

Use the STAR method: situation, task, action, result. Keep the focus on how you found the issue, how you verified it, and how you communicated it. Sample answer: "In one report, I noticed totals did not match the source extract. I checked joins and found duplicate customer rows. I corrected the logic, revalidated the numbers, and shared the impact with the team. This avoided an incorrect business update and improved the report quality."

How do you handle working with non technical stakeholders?

Show that you listen first, then translate technical work into business language. Mention that you ask clarifying questions, confirm the metric definition, and share findings in simple terms. Sample answer: "I avoid jargon and focus on the business question. I explain what I checked, what changed, and what action I recommend. If the data has limits, I say that clearly. This helps stakeholders trust the analysis and make faster decisions."

Why do you want to work at Accenture?

Connect your answer to consulting, client exposure, and structured problem solving. Mention that you want to use data to support business decisions across industries and learn from working with varied stakeholders. Sample answer: "I want to work in an environment where data analysis has direct business impact. Accenture interests me because it combines analytics with client problem solving, which fits my skills in SQL, reporting, and dashboarding. I also want to grow by working on different business contexts and larger datasets."

Your last 48 hours before the interview

  1. Revise your own projects so you can explain the problem, data sources, analysis steps, and result in 60 seconds each.
  2. Practise SQL joins, CASE, COALESCE(), LAG(), and basic subqueries by writing queries by hand.
  3. Review Power BI or Tableau basics, especially measures, filters, relationships, and dashboard design choices.
  4. Prepare 2 to 3 examples of data quality issues you have handled, such as duplicates, missing values, or mismatched formats.
  5. Do one timed mock interview where you answer out loud in short, structured responses.
  6. Prepare a simple closing statement about why you fit the role and what kind of work you want to do.

Common mistakes to avoid

Frequently asked questions

What SQL topics are most important for an Accenture Data Analyst interview?

Candidates commonly report questions on joins, filters, aggregation, CASE, subqueries, and window functions. You should also be ready to explain how you validate results and handle messy data, because practical thinking matters as much as syntax.

Do I need advanced statistics for this role?

Usually, you need solid basics rather than highly advanced theory. Be comfortable with averages, variance, correlation, sampling ideas, and how to interpret results in a business context. Interviewers often care more about correct interpretation than heavy mathematics.

How technical is the Power BI or Tableau part of the interview?

It is usually practical and report-focused. You may be asked about data models, filters, measures, and how you would choose visuals, rather than complex development. Be ready to explain why a dashboard is designed a certain way and how you would improve it.

How should I answer business case questions in this interview?

Start by clarifying the goal, then break the problem into a few measurable parts, such as volume, trends, segments, and root causes. Give a clear approach, not just a final guess. Interviewers like answers that are structured, realistic, and tied to business impact.

Interview with Accenture coming up?

Practise these Data Analyst questions out loud and get suggested answers in real time, based on your own resume. Free 5-minute demo, no subscription.

Try the free demo

More Accenture interview guides

Data Analyst interview questions at other companies

Related reading

This is an independent preparation guide based on commonly reported interview patterns. The process varies by team, location and year. Interview AI Helper is not affiliated with Accenture.

← All interview question guides