How to crack Accenture: The Management Consulting Delivery Associate internship, from a real experience
Accenture Management Consulting Delivery Associate internship interview guide: the guesstimate-style OA and interview, and how it differs from Accenture's engineering drives.
On this page
Last reviewed November 17, 2026.
For students interviewing for the Management Consulting Delivery Associate internship on Indian campuses.
Built by the Codinzhub team from one Accenture Management Consulting Delivery Associate internship interview experience shared on Codinzhub in October 2026. This is a single-report guide, not a pattern across many candidates, so we mark every claim as one person's experience. We searched LeetCode Discuss, Glassdoor and Reddit for Accenture consulting-internship reports and found general Accenture Technology/Software Engineer write-ups but nothing specific to this consulting internship track; we have not used those as sources here. Use this guide as a starting point and confirm the current format with your placement cell.
Why this gets its own guide. This internship is a different hiring track from Accenture's Elite Technology Engineer / AEH / ATE family (see our Elite Technology Engineer guide). It uses mental maths, mathematical reasoning and guesstimate questions instead of DSA, SQL and frontend coding. If you are preparing for an engineering role at Accenture, this guide is not the one you want; if you are applying for the consulting/delivery track, keep this preparation separate from DSA-style practice.
Important things to know before the interview
This role wants business reasoning, not code. The one candidate we have evidence from explained it directly: "don't expect that you will be building some model to analyse data and write C++ code to do something. You will be taught different skills to manage and analyse data." If you strongly prefer writing code, this candidate suggests the engineering tracks (SDE/Elite Technology Engineer) may suit you better.
Guesstimate questions are part of the interview, not just the OA. The one report describes being asked, in the interview itself, "How many people are wearing yellow shirts at South Kolkata now?" — a classic guesstimate question with no real answer, where the interviewer is grading your reasoning process.
Interviewers can pivot into technical basics even for this track, based on your CV. The same candidate, who had listed SDE and ML projects on their CV despite applying for a consulting role, was asked a basic C++ palindrome-check question and a question on how a PNP transistor and avalanche breakdown work, because those topics were on their resume. Know everything on your CV, even if it looks unrelated to the role you are interviewing for.
Multiple CVs for different tracks is one candidate's real strategy. The report describes preparing three separate CVs (core electrical, SDE, and "other roles" like product/consulting/business) and applying through whichever CV fit the specific internship opening. This is one person's approach, not a confirmed requirement.
What this guide covers
This guide covers the Management Consulting Delivery Associate internship at Accenture, based on one candidate's full process report from an October 2026 on-campus drive (college not stated in the report). It does not cover Accenture's engineering roles (Elite Technology Engineer, AEH, ATE); see our separate guide for those.
Given the single-report dataset, treat every specific question and number here as one person's experience, not a confirmed pattern.
Round-by-round breakdown
Stage 1: Application, where candidates applied
How it works. The one candidate applied through their college's CDC (career development cell) portal, using a CV tailored specifically for "Product, Consulting, Business"-type roles, separate from CVs they had prepared for core electrical and SDE openings.
Stage 2: Online assessment
How it works. Described as questions "based on mental maths and mathematical reasoning and other analytical questions." No specific questions were listed in the report.
At a glance
- Duration: Not reported
- Questions per round: Not reported
- Topics: Mental maths, mathematical reasoning, analytical reasoning
Stage 3: Interview round 1
How it works. This round opened with an introduction, then moved into CV-based questions, since the candidate's CV included ML, SDE and some data-analysis projects. The round also included a guesstimate question.
Reported questions
| Question summary | Skill or pattern | Level / scope | Codinzhub question or experience |
|---|---|---|---|
| How many people are wearing yellow shirts at South Kolkata right now? | Guesstimate / estimation reasoning | Management Consulting Delivery Associate internship, 2026 | Management Consulting Delivery Associate Internship |
Stage 4: Interview round 2
How it works. The interviewer noted the candidate's projects leaned toward SDE despite their core branch being Electrical, and tested both a basic coding question and electrical fundamentals before moving to a consulting-style case question.
Reported questions
| Question summary | Skill or pattern | Level / scope | Codinzhub question or experience |
|---|---|---|---|
| Check if a string is a palindrome, in C++. | Basic coding | Management Consulting Delivery Associate internship, 2026 | Management Consulting Delivery Associate Internship |
| How does a PNP transistor work? What is avalanche breakdown? | Core electrical fundamentals | Management Consulting Delivery Associate internship, 2026 | Management Consulting Delivery Associate Internship |
| An electrical production house has all its data on pen and paper and wants to digitise it. Given three equally powerful tools A, B and C, what criteria would you use to choose one? | Business case reasoning | Management Consulting Delivery Associate internship, 2026 | Management Consulting Delivery Associate Internship |
Accenture experiences shared on Codinzhub
| College | Role and result | What was asked | Experience |
|---|---|---|---|
| Not stated | Management Consulting Delivery Associate Internship, result not reported | OA (mental maths/reasoning); guesstimate question; coding + electrical fundamentals; business case on choosing a digitisation tool | Read it |
The Codinzhub next-round playbook
To prepare for the OA
- Practise mental maths and quick arithmetic reasoning under light time pressure, since the OA is described as analytical rather than coding-based.
To prepare for the interview
- Practise the guesstimate method: state your assumptions out loud, break the city/population/behaviour into estimable parts, multiply them back together, and sanity-check the final number.
- Know every project on your CV, even ones that seem unrelated to a consulting role; interviewers reportedly pivot into your technical background directly.
- For a business/case-style question, structure your answer around clear criteria (cost, ease of use, support, scalability) rather than picking an answer with no stated reasoning.
- If you like structured problem-solving, case competitions, or holding positions of responsibility, the one candidate's own advice is that this track fits that profile better than a pure coding-and-building role.
Variations within this role
Not enough data to describe variations across colleges or years. This guide is built from a single report.
Do's and don'ts
| Do | Don't | Why it matters |
|---|---|---|
| Prepare a guesstimate method (assumptions, breakdown, sanity check). | Give a single guessed number with no reasoning. | The reported question explicitly asks for a people-counting estimate with no real answer. |
| Know every project on your CV, including unrelated ones. | Assume a consulting interview will skip your SDE/ML projects. | The interviewer in this report pivoted directly into the candidate's SDE and core-branch background. |
| Structure a business case around clear decision criteria. | Give a one-line preference with no justification. | The digitisation-tool question is a case question that rewards visible reasoning. |
Most-asked topics
This dataset is a single report, so we list what appeared without ranking by frequency.
| Topic | What it means | Reported examples | Codinzhub practice |
|---|---|---|---|
| Guesstimates | Structured estimation of an unknowable number | People wearing yellow shirts in South Kolkata | Management Consulting Delivery Associate Internship |
| Business case reasoning | Choosing between options using stated criteria | Choosing a digitisation tool | Management Consulting Delivery Associate Internship |
| CV-driven technical basics | Core-subject or coding questions pulled from your own CV | Palindrome check, PNP transistor, avalanche breakdown | Management Consulting Delivery Associate Internship |
Preparing for the behavioural aspects
The one report describes a conversational, CV-led interview rather than a separate formal HR round. Be ready to explain why your CV includes the projects it does, and to connect them back to why you want a consulting/delivery role rather than a pure engineering one.
Practice problems that match the experiences
These are practice analogues, not proof that Accenture asked the exact problem, unless marked otherwise.
| # | Practice problem | Pattern | Related reported question or variant |
|---|---|---|---|
| 1 | Valid Palindrome (LeetCode) | String checking | Same underlying task reported |
| 2 | Guesstimate practice: "How many pizzas are ordered in your city on a Friday night?" (standard consulting-prep exercise) | Structured estimation | Same question type reported |
How to handle a question you have never seen
- For a guesstimate, state your assumptions aloud, break the number into factors (population, percentage relevant, rate of occurrence), and multiply them back together.
- For a business case, list 2 to 3 decision criteria before giving your recommendation, and explain the trade-off between options.
- For a CV-based technical question, answer plainly and honestly; if you are unsure, say so and reason through what you do know rather than guessing confidently.
Why candidates were rejected
No report in this guide gives an outcome or rejection feedback for this role.
If you remember only five things
- This internship tests business and mental-maths reasoning, not DSA, SQL or frontend coding.
- Prepare a clear guesstimate method before the interview.
- Interviewers may ask about anything on your CV, including unrelated technical projects.
- Structure business-case answers around explicit decision criteria.
- This is a different Accenture hiring track from the Elite Technology Engineer / AEH / ATE family; don't mix their preparation.
FAQ
Is this the same process as Accenture's Elite Technology Engineer (ETE/AEH/ATE) hiring?
No. Based on the one report we have, this consulting internship uses mental-maths OA questions and guesstimate/case interviews, not the DSA + SQL + frontend OA pattern used for the engineering roles.
Do I need to know DSA for this role?
Not based on this report. The one candidate was asked a single basic coding question (palindrome check) only because it appeared relevant to their CV, not as a standard DSA round.
What if my CV has engineering projects but I'm applying for this track?
Based on the one report, expect the interviewer to ask about those projects directly and to connect them to your reasoning for wanting a consulting role instead.
About this guide
The Codinzhub team wrote this guide from 1 Accenture Management Consulting Delivery Associate internship interview experience shared on Codinzhub in October 2026. We searched LeetCode Discuss, Glassdoor and Reddit for additional reports on this exact internship track and found none; general Accenture Technology/Software Engineer reports exist but describe a different hiring track, so we have not used them as sources here. Questions are short paraphrases in our own words.
You can help other students by sharing your Accenture experience on Codinzhub.
Interview processes change by college, year and specific drive. Your placement cell or recruiter can confirm the current format.
Other company and role guides
Keep track of what you’ve learned.