Accenture Managerial Round Interview Questions 2026 for Freshers and Experienced Candidates

This page is for freshers whose Accenture interview includes a managerial or "techno-managerial" conversation, and for experienced candidates in Accenture lateral hiring, where a managerial round with the hiring manager is standard. It explains when the round happens, who runs it, what they decide, and gives 30 questions with sample answers split between fresher and experienced situations.

Accenture is consulting-led, and its managers interview like consultants. They care less about whether you know the answer and more about how you structure a problem, communicate a plan, and behave when a client changes their mind.

How the Accenture managerial round works in 2026

As of September 2026, Accenture's India early-careers page describes its entry-level roles and Tech Expressway training but not interview rounds. The following comes from 2026 placement-site and candidate reporting.

Freshers (ASE and Advanced ASE). After the cognitive and technical assessment, coding assessment and communication assessment, there is one interview of 25 to 40 minutes that mixes technical, managerial and HR questions. Some drives split it into a technical panel followed by an HR-plus-managerial conversation. Advanced ASE candidates and role-specific hires (Custom Software Engineer, Data Engineer) more often get a separate managerial slot of 15 to 25 minutes with a lead from the practice.

Experienced candidates. Typically a technical round, then a managerial or behavioural round of 45 to 60 minutes with the hiring manager, then HR. The managerial round frequently includes a scenario from the manager's own client project, a walk through your most recent delivery, and a discussion of notice period, expected CTC band and location.

Who interviews. A team lead, project manager, delivery lead or senior manager from the hiring practice: cloud, data, security, application services, or an industry group. For laterals, usually your future reporting manager.

Context that shapes the questions. Accenture allocates freshers to practices after training, has large delivery centres in Bengaluru, Hyderabad, Pune, Chennai, Mumbai, Gurugram and Kolkata, and staffs client work in Indian, UK and US hours. So relocation, shifts and "will you work on a different technology" are always asked, and "how do you handle a client" is asked even of freshers.

What the Accenture managerial interviewer is testing

• Structured thinking. Can you break a messy situation into steps and say them in order?
• Client sense. Do you understand that the client's problem, not the code, is the job?
• Ownership and honesty. "I" for mistakes, "we" for credit, and no blaming.
• Flexibility. Practice, technology, city, shift.
• Commitment. Other offers, higher studies, notice period, why you are leaving.
• Composure. Stress questions and repeated criticism scenarios.

Use STAR (Situation, Task, Action, Result) for every "tell me about a time" question and keep each answer near a minute; consultants value brevity.

30 Accenture managerial round questions with sample answers

Client and delivery situations

1. The client changes the requirement two days before delivery. What do you do?

"Size the change before reacting. If small, do it, test it, and tell my lead. If large, tell my lead immediately with an estimate and two options: deliver on time without it and patch next sprint, or slip with it. Then put the decision in writing to the client. My job is fast, accurate information; the call is the lead's."

2. Your deadline was pulled forward by two weeks. How do you handle it?

"Confirm the new date and the minimum scope with my lead, list the remaining work, mark must-have versus nice-to-have, and estimate honestly. In my final-year project the external review moved up two weeks; we dropped the notification feature, delivered the core flow on time, and shipped notifications in the next iteration."

3. A client is unhappy on a call and starts blaming your team. What do you do?

"Listen fully, acknowledge the impact without arguing about blame, and agree a time for the next update. After the call, gather facts with the team and send a short note: what happened, what we are doing, when we will update next. Tone matters more than the fix in the first hour."

4. You find a bug in a colleague's code just before a client demo. What do you do?

"Tell the colleague first, privately and factually, and offer to help fix it. If it cannot be fixed before the demo, tell the lead so the demo can avoid that path. What I would not do is announce it in front of the client or hide it and hope."

5. Your team wants to skip testing to hit a date. What do you say?

"I would push for cutting scope instead of cutting testing, because a bug found by the client costs more than the time saved. If the lead still decides to reduce testing, I would ask that we list the untested areas and test them first after release."

6. You are handed a task with vague requirements. How do you begin?

"Write my understanding in five lines and send it to the requester for confirmation before coding. Build the smallest version, show it early, adjust. In my internship this saved a week when my reading of a report format was wrong."

7. You realise you cannot finish your task on time. When do you tell your lead?

"The moment I am sure, not the day before. I would tell them what is done, what is left, why, and what I need. Leads can re-plan around early news; late news just becomes their problem."

8. A production issue appears after hours and your lead is offline. What do you do?

"Assess impact first, then follow the project's escalation path and post on the team channel so there is a record. As a fresher I would not push an unreviewed change to production unless the runbook explicitly allows it."

Teamwork and people

9. Tell me about a time you resolved a conflict in a team.

STAR. "Situation: in our hackathon team two members argued over the database and stopped speaking. Task: 24 hours left. Action: I proposed the option both had used before, parked the other for next time, and kept a shared task board so work continued. Result: a working demo, third place. Lesson: a quick decision beats a perfect late one."

10. A teammate is not pulling their weight. What do you do?

"Talk privately first; there is usually a reason. In one project a member disappeared for two weeks with a family illness; we moved him to remote-friendly documentation and testing and I took his module. We finished on time. If someone simply refuses, I document and escalate."

11. How do you take criticism from a senior?

"Ask for a specific example, fix it, and show the fix. If the criticism keeps coming with no specifics, ask for a short one-on-one to understand expectations. I do not argue in front of the team, and I do not go quiet."

12. Have you ever disagreed with a manager? What happened?

"In my internship I disagreed with rewriting a working script in a new framework. I said so once with my reasons, then did the rewrite because the manager knew the roadmap. It turned out the framework was needed for the next feature. I learned to state my view once and commit."

13. Do you prefer working alone or with a team?

"Both, by task. Focused coding and debugging alone; design, reviews and planning with the team. On a client project most of the day is collaborative and I am comfortable with that."

14. How would you explain your project to a non-technical client?

One plain sentence and one number. "A chemist was losing money on expired stock; our app warns them 30 days before expiry, and in a six-week pilot they had no expired sales. That is the level I would use with a client; details on request."

15. Describe a time you had to learn something quickly for a deliverable.

"For my project I learned PostgreSQL window functions in two days to build the expiry report, from the docs and one tutorial. I built a tiny example first, then the real query. I would do the same for any Accenture stack."

Flexibility and commitment

16. Are you open to relocating anywhere in India and to rotational shifts?

"Yes to both. I know allocation follows client need and that some projects run on US or UK hours; my family and I discussed this before I applied." A hard constraint should be stated now with a reason, not after the offer.

17. Would you work on a technology different from what you know, say SAP, Salesforce or mainframe?

"Yes. What I learned in my project was how to learn a stack. I would like to move towards cloud or data over time, but my first practice is Accenture's call and I will take it seriously."

18. Do you have other offers? Which would you take?

"I have a TCS Digital offer. I would choose Accenture for the consulting exposure and the practice structure. I am telling you so there are no surprises." Candour reads as low risk.

19. Any plans for higher studies or competitive exams?

"No. I want industry experience first. If I do a master's later, it would be part-time." Do not lie if you are preparing for something; but know the manager will weigh it.

20. Why Accenture rather than a pure IT services company?

"Because the work starts from the client's business problem. I want to learn why systems are built, not only how, and Accenture's practices, cloud, data, security, industry groups, let me move without leaving. The Tech Expressway training is the other reason."

Self-awareness and stress

21. What do you bring that the other candidates today do not?

"A project that is used by a real shop, and a month of timed mock interviews, so I can give a clear answer in a minute. I will not claim to be the best coder in the room; I will claim to be reliable and clear."

22. What is your biggest weakness at work?

"I used to over-build. Now I write the requirement in one line above every task and check against it before adding anything. My project shipped because of that rule."

23. Describe an environment where you would struggle.

"Long stretches with no feedback. I improve fastest when told what is wrong, so I ask for feedback proactively. Pressure and unclear requirements I can handle."

24. If your manager gave you an impossible deadline, what would you do?

"Say so early, with evidence: the task list and honest estimates. Offer options: reduce scope, add a person, or move the date. Then commit fully to whatever is decided. Silently missing the date is the only wrong answer."

25. Where do you see yourself in three years at Accenture?

"On a client project as the person trusted with the difficult module, with one specialisation, probably cloud or data, and an Accenture certification behind it, and having mentored a batch of new joiners."

For experienced candidates

26. Why are you leaving your current company?

"My project is in maintenance and no development work is coming; I want to build. Accenture has an opening on a stack I have been learning. I am not leaving because of a person; my manager knows I am interviewing." Never criticise the current employer.

27. Walk me through your last delivery end to end.

Two minutes, STAR with numbers: the client problem, your role, the team size, the technical approach, one thing that went wrong and how you handled it, and the measurable result. Be ready for "what would you do differently".

28. What is your notice period, and can you join earlier?

"Ninety days, negotiable to sixty with leave adjustment; buyout is allowed and I can share the policy. Realistically, within sixty days of an offer." Exact numbers; managers plan staffing around them.

29. What CTC are you expecting?

A number with a basis. "Current CTC is 8 LPA; I am expecting around 12 for this role's band and my four years in this stack. I am open on structure." Avoid "as per company norms".

30. What questions do you have for me?

"What does a typical first engagement look like for someone in this role?" and "How do you decide when a new joiner is ready to face the client directly?" Save salary and leave for HR.

Mistakes that get candidates rejected in the Accenture managerial round

• No structure. Rambling through a scenario instead of "first, then, finally".
• Refusing relocation or shifts, or a reluctant yes.
• Blaming others in every story. The pattern is what the manager remembers.
• Contradicting HR or the technical panel on offers, gaps or availability.
• Heroics instead of judgement. "I would work all night" is not a plan.
• Losing composure on a stress question; the reaction is being graded, not the answer.
• Asking about salary or leave in this round.

How to practise the Accenture managerial round

Structure and composure come from speaking answers under time pressure and reviewing them, not from reading lists. In MockMate Practice, attach your resume and paste the Accenture role description, choose a managerial or behavioural round, and run a ten-minute adaptive session in the browser. The interviewer persona pushes on weak stories and adds follow-up pressure the way an Accenture lead does. The report afterwards shows every answer, your response timing, recurring weaknesses and a recommended next practice. Eligible accounts get three free Practice starts of up to ten minutes each. Use MockMate Live assistance only in interviews or meetings where the organisation or interviewer permits it; when permission is unclear, which is the case for Accenture selection rounds, stay with Practice.

Plan: write six STAR stories (client or requirement change, deadline, conflict, failure, learning fast, disagreeing with a senior), run one round, rewrite the two weakest from the report, and run again. The assessments and the technical conversation are covered on the Accenture hub; company-mapped sessions are at /mock-interview.