Skip to content

How to Prepare for Accenture

Accenture is a multi-gate filter: cognitive, technical MCQs, coding, then communication. Treat each gate as its own exam. Most rejects die on cognitive or communication, not on hard DSA.

What Accenture actually tests

First round: Accenture NLT / Cognitive + Technical + Coding + Communication

Time split that matches how candidates report outcomes (not a marketing pie chart):

  • Aptitude 40%
  • Coding basics 30%
  • Core CS 20%
  • HR 10%

Patterns are from student reports and vary by role and drive. Trust your college placement email over blog folklore.

Hiring flow you should prep for

Stage Time What they check
Cognitive ~50 min English, critical reasoning, abstract - main volume filter
Technical MCQ ~40 min Pseudo-code, CS fundamentals, MS Office
Coding ~45 min 2 array/string-level problems, not LeetCode hard
Communication ~20 min Written + spoken English - hard gate for many
Interview 20-40 min Projects, basics, HR fit

Time allocation

  • Aptitude Mastery (40% time) - Practice quantitative and logical reasoning daily, solve previous Accenture NLT papers
  • Programming Basics (30%) - Revise C/C++/Java/Python basics, practice output and logic questions
  • Core Subjects (20%) - Review DBMS, OS, OOPs, networking, prepare for project discussion
  • Communication & HR (10%) - Practice English communication, prepare HR answers

Daily loop (90-120 minutes)

  1. One timed block that matches Accenture’s first round (aptitude + coding OA)
  2. Log misses: topic + why you failed (speed, concept, carelessness)
  3. Re-solve yesterday’s misses cold
  4. Twice a week: 10 minutes of resume/project narration out loud

6-8 week service-company plan

Week Focus Exit criteria
1-2 Quant + reasoning speed 2 full aptitude mocks, >70% accuracy
3-4 Verbal + programming logic / pseudo-code Comfortable under sectional timers
5-6 Coding basics + CS fundamentals 1-2 coding problems solvable cleanly
7-8 Full mocks + interview answers Sectional cutoffs cleared in mocks

Round-by-round strategy

Online Assessment

  • Sectional cutoffs matter more than a hero score in one section
  • Quant/reasoning: skip time sinks after 90-120 seconds
  • Verbal: accuracy over vocabulary flex
  • Coding/pseudo: get one clean full solve before polishing a second

Technical interview

  • OOPs, DBMS, OS, Networks - definitions plus one example each
  • Be ready to write a simple program on paper/editor
  • Project explanation: problem → your work → result (numbers if any)

HR

  • Why Accenture, gap years, location preference, bond/notice if asked
  • Speak clearly; service HR rounds fail quiet candidates more than imperfect ones

Accenture-specific drills

  • Daily timed cognitive sets (English + critical + abstract)
  • Pseudo-code tracing and OOPs/DBMS MCQs under 1 min/Q
  • Two easy-medium coding problems with clean I/O, not fancy algorithms
  • Record a 2-minute spoken intro and an essay draft every other day

Topic checklist

  • Aptitude speed with sectional accuracy
  • One coding language for basic problems
  • OOPs, DBMS, OS one-liners you can expand
  • HR answers: why company, relocation, gaps

Final stretch

30 days out: 3+ full Accenture-pattern mocks per week; build an error log by section.

7 days out: one mock every other day; revise only error-log topics; rehearse HR answers aloud.

Day before: light revision, no all-nighters - sectional exams punish fatigue.

Common mistakes for Accenture aspirants

  1. Cognitive sectional failure - coding never saves a weak cognitive score - fix this first
  2. Preparing only interviews while failing Accenture’s first round
  3. Collecting notes without timed mocks
  4. Listing five frameworks on the resume and defending none
  5. Changing language/stack one week before the drive
  6. Grinding LeetCode hard while failing aptitude cutoffs

Practice on this site

Comments & Suggestions

Similar companies

TCS · Infosys · Wipro · HCL · Cognizant · Capgemini