These are LLD questions of the kind Accenture actually asks — the patterns that keep coming back in Accenture's AI project interviews, where what matters is applying LLD sensibly for clients rather than research depth. Treat this page as a mock interview: say every answer out loud before revealing it. If one surprises you, the lesson behind it is linked at the bottom.
Accenture LLD concept questions
A common Accenture LLD question, reflecting their consulting/integration-heavy work: a client's legacy billing system exposes a generateBillXML() method, but the new reporting module expects a getBillJSON() interface. How do you connect them without touching either system?
Asked in
A client wants an approval workflow where the number of approval steps (1, 2, or 3 levels) varies by client and might change later. What's a clean way to model this?
Asked in
Different clients need different validation rules on the same order form (one requires a PO number, another doesn't). How would you avoid if (client == 'X') branches scattered through validation code?
Asked in
How to use this page: Accenture rarely asks something you've never seen — they ask a standard LLD concept and then push one level deeper ("why?", "what would you do if..."). Master the concept in the LLD course lessons, and the follow-up stops being scary.
Keep practising: SOLID Principles, Strategy Pattern, Design a Parking Lot and UML Diagrams cover what most Accenture LLD rounds test — and the Accenture exam guide covers the rest of their selection process.