Accenture Behavioural Interview: Competencies and How to Answer

What to expect from an Accenture behavioural interview

Accenture's process varies by country, business area and level, so check your invitation and the job description rather than relying on a generic account. What is well established is that large consulting and professional-services employers commonly include a competency-based (behavioural) interview. Depending on the role, this can be live, with a recruiter or manager, or a recorded one-way video stage where you answer on-screen questions against a timer.

The logic is the same in either format: past behaviour is treated as the best available evidence of future behaviour. Instead of 'What would you do if a client changed the brief?', you are more likely to hear 'Tell me about a time when priorities changed at short notice.' Your job is to pick a specific, real example and show clearly what you did and what happened.

Competencies these interviews typically assess

We can't tell you Accenture's exact question list or scoring criteria, and nobody outside the company should claim to. But consulting-style competency interviews tend to probe a recognisable set of themes. Use the job description and Accenture's careers pages to see which ones your role emphasises.

• Client or customer focus: understanding what someone else needs and adjusting your work to deliver it.
• Teamwork and collaboration: contributing in mixed groups, handling disagreement, supporting others.
• Adaptability and handling ambiguity: staying effective when scope, tools or priorities shift.
• Problem solving and analytical thinking: breaking down a messy problem and using evidence to decide.
• Learning agility: picking up unfamiliar skills or subjects quickly and applying them.
• Ownership and initiative: acting without being asked and following through.
• Communication and influence: explaining complex points simply and persuading without authority.
• Resilience and integrity: recovering from setbacks and doing the right thing under pressure.

Use STAR, but spend your time on Action and Result

STAR stands for Situation, Task, Action, Result. It keeps answers structured, which matters most when you are being timed or speaking to a camera. The common mistake is to spend half the answer on background. Aim for roughly this split: Situation and Task in about 20%, Action in about 50%, Result and reflection in about 30%.

Say 'I' when describing your own actions. Interviewers are assessing you, not your team, so 'we decided' hides your contribution. For the Result, give something concrete: an outcome, a measure, feedback received, or what you changed afterwards. If you don't have hard numbers, a specific qualitative result is fine. Never invent figures.

Worked example: adapting when priorities change

Question: 'Tell me about a time you had to adapt quickly to a change.' The answer below is an illustrative example of structure and level of detail, not a script to copy. Your story must be your own.

Situation: 'In my final year I led a four-person team building a market analysis for a local charity as part of a university project. Two weeks before the deadline, the charity told us it now needed the findings for a funding bid, so the audience had changed from academics to non-specialist trustees.'

Task: 'I was responsible for coordinating the team and making sure the final output still met both the marking criteria and the charity's new purpose.'

Action: 'First, I arranged a call with the charity contact to confirm exactly what the trustees needed to decide. Then I re-planned our remaining time: I moved two teammates from detailed methodology write-ups to building a one-page summary and three clear charts, and I took on rewriting the executive summary in plain English. I also set a short daily check-in so we could catch problems early.'

Result: 'We delivered both versions on time. The charity said the summary was easy to use in its bid, and our tutor highlighted the clarity of the recommendations. What I took from it is to confirm the audience and purpose early, because that determines where to spend limited time.'

Do and don't: what separates strong answers

Small habits in how you tell the story often matter more than the story itself.

• Do pick examples with a real challenge or tension; don't choose a story where everything went smoothly.
• Do explain your reasoning ('I chose X because…'); don't just list tasks.
• Do include what you learned or would do differently; don't claim you would change nothing.
• Do keep to one example per question; don't ramble across several projects.
• Do be honest about mistakes and how you fixed them; don't blame others.
• Do tailor the story to the client-facing, team-based nature of consulting work where it's true; don't stretch the facts to fit.

Build a story bank and practise under time pressure

You don't need 30 stories. Prepare five or six strong ones from work, university, volunteering or projects, then map each to several competencies. A single example about a difficult stakeholder might serve for communication, resilience and client focus, depending on which part you emphasise.

Write each story as brief STAR bullet points, not a script, then say it aloud. Aim for about 90 seconds to two minutes, which suits most recorded-interview time limits. Reading your notes silently hides rambling that only shows up when you speak.

Practising on camera helps too, because eye contact and pacing feel different from rehearsing in your head. A tool such as ScreenReady lets you answer timed questions on video and get AI feedback on structure and clarity, which is useful for checking whether your Action section is doing enough work. A friend asking follow-up questions is a good complement, since live interviewers often probe with 'What was your specific role?' or 'What would you do differently?'