
Accenture Business Analyst interviews typically start with an HR or recruiter screen, often move into a group business case, and continue with one or more individual rounds covering client-handling scenarios, project or agile experience, and occasional SQL, Power BI, or finance questions.
$108K
Avg. Base Comp
$128K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Across the Accenture Business Analyst reports gathered here, the process usually opens with a recruiter or HR screen covering background, motivation, and a classic "why Accenture" question. It is sometimes paired with a psychometric assessment or short questionnaire. From there, candidates frequently describe a group business case, such as organizing an event, solving a practical business problem, or presenting a recommendation as a team. Interviewers use it to watch collaboration as much as the final answer. Several candidates then moved into one or two individual rounds with a manager or senior manager. Questions there shifted toward client-handling scenarios, such as managing a difficult client or handling gathered requirements that aren't the intended solution. They also covered agile or project-management experience, and sometimes a five-year-plan or role-fit question about leaning toward a technology versus advisory track.
Technical depth varies by report. Some candidates faced only behavioral and case-style questions. Others were asked about SQL, Power BI, basic accounting concepts like IND AS or IFRS, or quick estimation exercises such as estimating mask sales in Germany during COVID. Given how much the exact sequence varies across reports, treat it as a general pattern rather than a fixed script. Come ready with concrete examples of stakeholder management, teamwork, and basic analytical reasoning.
Synthesized from 87 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Accenture process.
The whole thing was a bit of a mixed bag. I started with an HR phone screen, then a video call with HR again, and then a video interview with the team lead—so three rounds total before they made a decision. Along the way I had to take an English test, which was straightforward multiple-choice listening and comprehension, and a logic test that wasn't easy but I managed to pass it. There was also a cognitive assessment and a case study prep where I had to analyse some case information and share my findings with the team lead. I remember doing a market-sizing exercise and being asked to identify trends in my market and globally, plus a SQL component. They also wanted me to think about implementation considerations specific to Singapore, which was a nice touch—it forces you to think beyond the generic answer. The process was slow, to be honest; scheduling took forever and results came back after a long wait. But it wasn't stressful overall, just drawn out. I got the offer.
Prep tip from this candidate
Expect to show SQL competency alongside case-style thinking. More importantly, prepare to localize your solutions—they want to see that you understand regional context and can adapt recommendations to specific markets, not just give textbook answers.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Accenture
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Top 5 Turnover Risk | |
| Google Maps Improvement | |
| Largest Salary by Department | |
| Resumable Fact Table Load | |
| Hurdles In Data Projects | |
| Target Indices | |
| Assumptions of Linear Regression | |
| Digitizing Student Test Scores | |
| Count Transactions | |
| Identify Managers | |
| Classification and Regression | |
| Slow SQL Query | |
| Data Pipelines and Aggregation | |
| User Event Data Pipeline | |
| Demand Metrics | |
| Smart Home Security Launch | |
| Addressing Data Quality Issues | |
| Different Parcel Effectiveness | |
| String Palindromes | |
| Popular Products | |
| Deciding Between Solutions | |
| Merchant Dashboard Design | |
| Safe Deployments | |
| Trucks for Same-Day Coffee Delivery | |
| Scalable Data Pipelines |
Synthesized from candidate reports. Individual experiences may vary.
Most candidates report an initial recruiter or HR conversation covering work history and why they want to join Accenture. It sometimes includes a "where do you see yourself in five years" or long-term fit question. This stage is typically conversational rather than technical.
Several candidates describe a psychometric or aptitude-style assessment, a separate test, or a mail-in questionnaire somewhere early in the process. This step is not universal across reports, so candidates may or may not encounter it depending on the specific role and location.
A recurring stage across many reports is a group case study, where candidates work with others to solve a business problem, organize an event, or prepare a presentation. Interviewers appear to focus on how candidates collaborate and contribute without dominating the conversation. Reported durations range from about two hours to a full assessment day.
Candidates typically move into one or more individual conversations with a manager or senior manager. These cover resume walkthroughs, agile and project experience, and scenario questions about handling difficult clients or requirements that don't match the intended solution. Some reports mention a later round focused on why the candidate chose Accenture and where they'd fit best.
A subset of candidates report technical or quantitative questions layered into the individual rounds. These include SQL, Power BI, basic accounting concepts such as IND AS or IFRS, or consulting-style estimation questions like estimating mask sales during COVID. These appear tied to specific roles or interviewers rather than a universal requirement.