InterviewLegend

How Accenture Tests System Design

Alex Chen10 min readGuide updated
In this lesson
  • Know whether your Accenture track gets a design round at all, and what takes its place
  • Prepare the design questions most candidates face: your own project and the microservices patterns
  • See the 2026 design prompts by role, newest first, and the older ones labelled by year

Most Accenture engineering loops have no system design round, and campus loops almost never do. That holds across roles and countries in 2026.

Design still comes up, just in other shapes. Accenture's careers blog describes a "skills interview, a time to discuss your knowledge and expertise" and never mentions a design round. For most candidates, design means explaining the architecture of something you built and answering pattern questions about the stack on your resume. Real design scenarios depend on your track. Architect, GenAI and frontend roles get them, and so do some software roles in Europe and the US.

Where design shows up, by track

Campus hires explain their project

ASE, AASE, AAE and Elite Engineer candidates don't get a dedicated design round. The 2026 campus interview is short, often 10 to 30 minutes, and mostly projects, OOP, DBMS and HR. Design usually means the "architecture/flow of the project", as an Elite Engineer in Bengaluru put it in October 2026. One June 2026 AAE candidate did get a basic RAG chatbot architecture question.

Experienced India hires get pattern questions

Inside the skill interview, design arrives as rapid questions on your resume stack. Through 2026, as late as September, that meant Saga, circuit breakers, API gateways, service discovery, Kafka dead letter queues, Builder and Factory. You'll defend your own choices too. A full-stack candidate with four years of experience said in March 2026 the interviewer kept "questioning my design choices".

Architect tracks get real scenarios

Technical and Solutions Architect loops are where whiteboard-style scenarios appear. A Solutions Architect in Bucharest (February 2026) spent about two hours on mostly technical questions, including a cloud design that could later move on-premise. The same month, a Technical Architect in Gurgaon was asked how to keep cloud native solutions scalable.

GenAI roles get RAG and agent design

Design shows up as RAG and agent architecture on top of ML fundamentals. GenAI rounds from April to August 2026 covered RAG pipelines or GenAI project architecture, one of them a client chatbot. An LLM Operations final in December 2025 stayed on concepts, such as why a multi-agent system needs routing.

Frontend roles get component design

Expect component design and React performance. A front-end developer in Singapore (August 2026) was asked for a solution for a table component. The follow-ups covered side effects in custom hooks and performance in large component trees.

UK graduates get a case study

A case study round sits where system design would. UK graduate loops in 2026, a data and AI scheme among them, had one. In Newcastle it was a task-based interview after a HackerRank test. A London Enterprise Architect got a case study before the partner interview in July 2026. Expect a client scenario and a plan for it, closer to consulting than to distributed systems. Lead with the client's goal, give a phased plan, and name the risks up front.

Some software loops outside India hold a real round

A true design conversation is likeliest in Europe and the US. In 2025, a software engineer in Italy designed a basic messaging system, and an applications developer in San Jose had a virtual round on system design and data structures. A full-stack software engineer in August 2026, location not given, said the technical rounds "were more system design than coding".

Data engineering rounds in 2026 stay on architecture knowledge: Medallion architecture, Spark architecture, CDC and data quality. The pipeline and lakehouse design prompts date from October 2025.

The Accenture angle
Your current project is the design question. Accenture puts engineers on client projects, so the interviewer wants proof you understood the system you worked on. Draw it in one picture, walk one request through it, and have a reason for each choice. A Hyderabad SDE in January 2026 advised explaining everything you write in the design round, and why.

Design prompts reported in 2026, newest first

Read these as the shape your track gets. The wording will change. Two design asks come up far more often than any of them: your own project's architecture, and the microservices and design pattern drill. The RAG chatbot, table component and REST API prompts have worked lessons below.

  • April to August 2026: A RAG chatbot or GenAI architecture. AI and GenAI roles. A June 2026 campus candidate for Advanced Application Engineering Analyst was asked for the basic architecture of something like a RAG chatbot for a pharmacy client, answering on the dosage and effects of the client's own drugs. An AIML engineer in Bengaluru (August 2026) got GenAI project architecture face to face, including evaluating RAG with a graph database.
  • July to August 2026: A frontend table component. Something like "give a solution for a table component" (Singapore, August 2026), with follow-ups on custom hooks and large component trees. Chennai and Pune loops in 2026 had component design scenarios and a React architecture discussion.
  • August 2026: An AI system that trains on documents. Something like "How would you build an AI model with training for documents?" for a full-stack software engineer whose two technical rounds leaned on design.
  • February to July 2026: A client case study. UK graduate loops and a London Enterprise Architect loop. In 2025 a New York software engineer got something like "How would you go about creating a commerce website?" and called the round "more towards the consulting side".
  • February to May 2026: Build a REST API end to end. An Associate in Bengaluru (May 2026) was asked about "building custom api end to end", then to build a REST API in code. An Associate Manager (February 2026) got how to build an application and create a REST API. Follow-ups covered REST principles and connecting Spring Boot to a database.
  • March 2026: A Salesforce portal for 100k+ users. Something like "How would you architect an Experience Cloud portal for 100k+ users?" for an applications developer in New Delhi, with follow-ups on sharing models, custom LWR templates and license limits.
  • February 2026: A cloud design you can move on-premise. Something like building a solution in a cloud provider that can later be lifted and shifted on-premise, under constraints the interviewer sets (Solutions Architect, Bucharest). A Technical Architect in Gurgaon got the scalability version that month.

One more design ask hides inside live coding. In August 2026 a Kafka engineer in Bengaluru, later offered Sr Analyst at Management Level 10, got a simple string problem, then pseudocode for a Kafka consumer application. It's worked in the skill interview lesson.

When the round just says "system design"

Plenty of 2026 rounds, as late as October, ask design questions without a named prompt. They lean on fundamentals more than on boxes and arrows. An Associate Software Engineer in Lucknow (October 2026) had a round on web development, database architecture and "system design basics": state management, authentication flows, relational database design and API security. A senior engineer in Pune (August 2026) was told to expect "design level questions", then asked to explain API architecture and front controllers. A .NET engineer in Gurgaon got middleware and its flow. So brush up on the parts of a web system you already use. A senior candidate in Gurgaon (January 2026) was asked JWT versus sessions, then rate limiting and DDoS protection, and said the questions were the same ones a two-year engineer gets. Seniority doesn't change the topics much. Depth on your own stack does the work.

Older design prompts (2021 to 2025)

These are older than a year. Give one a practice rep only if it matches your role.

  • A parking system, object-oriented (November 2025). Something like a parking lot in classes, pair-coded with a team lead in Istanbul, with follow-ups on dependency injection and mutexes.
  • A lakehouse data platform (October 2025). A senior data engineer in Mumbai was asked about Data Lake and lakehouse design, query optimization and disaster recovery.
  • A basic messaging system (August 2025). A software engineer in Italy designed the send and delivery path, and said they "struggled a bit with scaling".
  • A mobile system design round (2025). A senior iOS developer in Mumbai had one between live coding and the hiring manager in June 2025, and a senior Android developer in Bengaluru got architecture questions that July.
  • An AWS architecture deep dive (2021). A US phone interview for an AWS solution architect opened with behavioral questions and then went deep on AWS system design.

Prepare for the design you will get

Start with your own project, because nearly everyone gets it. Draw it in one picture. Walk one request through it, name the data model, and be ready for one scaling question and one failure question. Then have an answer for "why not X" on each big choice. Defend your project's architecture turns that into a structure you can repeat, and it's free. Experienced candidates in India should learn the microservices patterns next, by name and by trade-off. On an architect, GenAI or frontend track, add the matching worked design below. A from-scratch whiteboard design is the exception at Accenture, so give it real time only when your track points there.

The design lessons

Defend Your Project's Architecture

The design question nearly every candidate gets, from campus to senior. One diagram, the request path, and answers for "why not X".

Microservices and Design Patterns in the Skill Interview

Saga, circuit breakers, gateways, dead letter queues and Builder and Factory, shown on one small order service.

Design a RAG Chatbot (GenAI Roles)

Ingestion, retrieval, grounding and evaluation for a client chatbot, plus RAG versus fine-tuning.

Design a Table Component (Frontend)

A sortable, paginated table: component API, state, data fetching and rendering large data fast.

Build a REST API End to End

The design-and-build ask for Associates and Associate Managers, from REST principles to the database.

Common questions

Does Accenture have a system design interview?

Not for most roles. Architect tracks, GenAI and frontend roles, and some Europe and US software loops do get design scenarios. Everyone else meets design as questions about their own project and the patterns in their stack.

Do Accenture freshers get system design questions?

No dedicated round. The campus interview is short, and design usually means explaining your project's architecture and flow. An AASE candidate in July 2026 also got N-tier architecture and middleware, and an AAE candidate in June 2026 was asked for a basic RAG chatbot architecture.

What design questions do experienced Accenture candidates get?

In India, mostly microservices and design pattern questions tied to the resume: Saga and its implementations, circuit breakers, API gateways, service discovery, Kafka dead letter queues, Builder and Factory. Expect a deep dive on your current project's architecture too, and challenges to your design choices.

Key Takeaways

  • ✓Most Accenture loops have no system design round, and campus loops almost never do.
  • ✓Campus design means explaining your project. Experienced India hires get microservices and design pattern questions tied to their resume.
  • ✓Architect, GenAI, frontend and some Europe and US roles get real scenarios. UK graduate schemes get a case study.
  • ✓Start with your own project. Add the worked design that matches your track only after that.
Accenture interview guide

Know what Accenture asks before you walk in.

23 coding · 5 system design · 34 behavioral questions

Get Premium$49 a year · Instant access
Or start freeNo card.

Get their questions first.

Older Practice Problems (2023-2024)Had your Accenture interview?How we research

InterviewLegend is independent and not affiliated with or endorsed by any company it covers.