Accenture software engineer candidates report project-heavy interviews: an online aptitude and coding screen, short HR-style conversations, and technical questions on OOP, Java, SQL and the stack on their resume.
$102K
Avg. Base Comp
$125K
Avg. Total Comp
Not reported
Typical Rounds
Not reported
Process Length
Accenture software engineer interviews, as candidates describe them, revolve around your resume. Across these reports, the most common thread is that interviewers spend much of their time on your projects: what you built, your exact contribution, the challenges you hit and the tools you used. Several candidates say this mattered more than algorithm depth.
Many candidates describe an online screen, usually aptitude plus coding, and some also mention a communication or English assessment. The coding is generally described as basic. One candidate had just two technical questions in the assessment, while another found the online coding test the main filter. In interviews, candidates mention simple tasks such as printing star patterns and checking for prime numbers.
Technical topics tend to follow the stack you list. Reports mention OOP, ACID properties, SQL joins, design patterns, Angular, JavaScript and front-end topics such as HTTP and first-page optimization. One Java-focused candidate was asked about Java 8 coding, Spring Boot concepts such as bean scope and actuators, and API basics. If you list a framework, expect follow-up questions on how you used it.
Behavioral and fit questions appear often. Candidates mention why you want to join Accenture, your goals, how you would fit into a team, and how you would make sure a team's code met recommended standards. Outcomes are mixed, with both offers and rejections. Several candidates also report scheduling delays or slow communication. Prepare a crisp project story and your fundamentals, and be ready for rounds that differ by team and role.
Synthesized from 529 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.
I came in as an Oracle HCM technical person, so almost the whole interview was on the integration side. The questions covered HCM extracts, BI Publisher reports, Fast Formulas, and value sets, and the interviewers wanted to hear how I had actually built and troubleshot those pieces, not just define them. A few functional scenarios also came up, so it helped to think about how HCM data moves between modules and what a business user is really asking for when they request a new report or integration. The pace felt conversational. I wasn't being tripped up on trivia. The focus was on whether I could do the work on a real project. I received and accepted an offer.
Prep tip from this candidate
Walk in ready to explain a specific HCM extract, BIP report, or Fast Formula you have built, including a problem you debugged, since integration depth was the main focus. Be prepared to connect those technical pieces to functional outcomes for the business.
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 | |
|---|---|
| Top Three Salaries | |
| Merge Sorted Lists | |
| Rolling Bank Transactions | |
| Top 5 Turnover Risk | |
| Largest Salary by Department | |
| Raining in Seattle | |
| Retailer Data Warehouse | |
| Bagging vs Boosting | |
| Google Maps Improvement | |
| Resumable Fact Table Load | |
| Hurdles In Data Projects | |
| Target Indices | |
| Real-Time Hashtag Partitioning | |
| FAQ Matching | |
| Digitizing Student Test Scores | |
| Identify Managers | |
| Count Transactions | |
| Slow SQL Query | |
| Data Pipelines and Aggregation | |
| User Event Data Pipeline | |
| String Palindromes | |
| Confidence Interval Explanation | |
| Deciding Between Solutions | |
| Safe Deployments | |
| Pipeline Transformation Failures | |
| Expansion Plan | |
| Scalable Data Pipelines | |
| Testing Constraints | |
| Azure Kubernetes Infrastructure |
Synthesized from candidate reports. Individual experiences may vary.
Many candidates report an online assessment covering aptitude and reasoning plus coding. Reports describe the coding as basic. One candidate had just two technical questions, and another called the coding test the hardest step. Some also mention a communication or English assessment that checks how clearly you express yourself.
Several candidates describe a short call with a recruiter or HR contact, one lasting no more than 20 minutes. It typically covers your introduction, background and project experience. It may come before or after the assessment depending on the role.
Candidates report that technical interviews focus heavily on resume projects, including the challenges you faced and your specific contribution. Fundamentals mentioned include OOP, ACID, SQL joins, Java, Spring Boot, Angular and JavaScript. Some report simple coding such as star patterns or prime checks. Difficulty is usually described as basic to average and tied to the stack you listed.
Candidates commonly report a final or additional conversation on fit. Topics include goals, teamwork, why Accenture and, in one case, how you would keep a team's code to recommended standards. Some describe a talk with someone from the project team. Round structure varies by role and team, so confirm the format with your recruiter, and expect scheduling or update delays in some cases.
