01 — What These Two Rounds Actually Are
Assessment #4 (Communication) and the Final Interview · Accenture India campus, 2027 batch Compiled 2026-09-17 from 40 local claims and 16 online sources. Read this before anything else.
The short version
Assessment #4 is a ~30-minute AI-graded English test that can eliminate you, delivered in Chrome on a separate date. Accenture publishes exactly what it scores. It is half listening, and it has a written email section that every prep site on the internet says does not exist.
The interview is one person, about 30 minutes, the last round. They decide on your overall performance across the whole process. Four of the questions asked are known verbatim.
The single biggest change from the predecessor handoffs: Accenture's own campus support page answers most of what three previous runs left open. It was never opened. It is the most authoritative source in this project and should be re-read the week of the test.
Part 1 — Assessment #4: Communication
Confirmed mechanics
| Item | What is true | Tag |
|---|---|---|
| Duration | ~30 minutes | [CONFIRMED] official |
| Scheduling | Separate email, separate date, own login details | [CONFIRMED] official |
| Delivery | Google Chrome 110+, ordinary browser. Webcam and mic mandatory. Not the Secure Exam Browser used for #1–#3 | [CONFIRMED] official |
| Does it eliminate? | Yes. "mandatory assessment. You are required to meet our sectional cut-off in order to proceed" — naming the communication assessment | [CONFIRMED] official |
| The cut-off value | Not published anywhere | [UNKNOWN] |
| Machine | Laptop/desktop only. "DO NOT use Mobile/Tablet." macOS 10.9+ is supported | [CONFIRMED] official |
| Internet | Stable 2 Mbps+ both ways. Broadband, not 3G/4G | [CONFIRMED] official |
| Audio | Good-quality wired headset with mic. No Bluetooth. Do not use the laptop mic | [CONFIRMED] official |
What it scores — the official parameter list
This is the rubric. Everything in the communication library is built against it.
| Group | Parameters |
|---|---|
| Verbal | Pronunciation · Fluency · Active Listening · Spoken English Understanding · Vocabulary · Articulation · Grammar |
| Written | Etiquette · Content · Grammar |
Two things worth noticing.
Two of the seven verbal parameters are comprehension, not production. Active Listening and Spoken English Understanding are scored separately from how you sound. A meaningful part of this round is simply hearing accurately — which is trainable, and which most candidates never practise.
The written group has no parameter for length or speed. It is Etiquette (register, greeting, sign-off, politeness), Content (did you actually address the task), and Grammar. Nothing else.
The sections you will probably see
Ranked by how good the evidence is. Prepare in this order.
| Task | Evidence | Confidence |
|---|---|---|
| Write an email | Official written parameters + both candidates + two named genres | High |
| Listen and repeat | Two independent candidates + official Active Listening | High |
| Read written sentences aloud | Two independent candidates + official Pronunciation | High |
| Grammar fill-in-the-blank (typed or spoken) | REV-001 twice + official Grammar | High |
| Speak on a given topic | One candidate + official Fluency/Articulation | Medium |
| Hear an error, correct it, say it | One candidate | Medium |
| Aural dash-fill (hear a gap, supply the word) | One candidate; may be the same task as fill-in-the-blank | Medium |
| Jumbled sentences · story retelling · short answers | Aggregators only, describing a different test | Low — secondary |
How many sections there actually are is unknown. The "seven sections" in the handoff is a union of two partial accounts; one candidate said "about 5–6", the other listed 3, then 4. Prepare the union.
The email section — the best-evidenced and most coachable part
REV-001 named the two topics: "Error reporting" and "Pitch based".
Vendor documentation for this class of test (Pearson Versant, used as a format model only) specifies an email task that matches the reported shape almost exactly — 2 items, 9 minutes, at least 100 words, a short workplace scenario naming the recipient, and three themes you must address. Responses under 30 words or off-topic score the minimum. The reported "two topics" and the vendor's "2 items" converging independently is the strongest structural signal in this library.
This is where the marks are. It is the one section with a published rubric, a known genre pair, a predictable skeleton, and enough time to think.
Timing
~10 seconds per short question (REV-001, hedged) and 5–10 minutes for the email — where REV-001 explicitly said he could not remember accurately. The vendor figure is 9 minutes. Practise the email to a 5-minute floor so a shorter allowance cannot hurt you.
The failure mode that should worry you most
Not a low score — a withheld one.
"When any noise from the surrounding is audible, system might prevent you from receiving a score." — Accenture "…the speaking score may not be available" due to "very soft voice, whispering, or background sounds" — vendor documentation
Two independent sources say the same thing: bad audio does not cost you marks, it costs you the score. Wired headset, quiet room, nobody else present, speak up.
On accent — the question the predecessors left open
A regional Indian accent is not itself penalised. Do not try to sound American.
Accenture's parameter list names Pronunciation and Articulation — never accent. The speech recognisers in this product class are explicitly optimised for non-native speech and calibrated against non-native distributions.
But be precise about the limit: pronunciation is scored, and scoring works by checking whether expected words are recognised in the expected sequence. An accent heavy enough to make words unrecognisable, or a mumbled or rushed delivery, will cost you. The mechanism is intelligibility, not preference.
What is actually measured: response latency · speaking rate · position and length of pauses · word stress · segmental pronunciation. So: start promptly, hold an even pace, pause at clause boundaries rather than mid-phrase, and finish your words.
Part 2 — The Final Interview
Confirmed mechanics
| Item | What is true | Tag |
|---|---|---|
| Panel | One panelist | [CONFIRMED] official |
| Duration | ~30 minutes scheduled (candidates report 20–45 actual) | [CONFIRMED] official |
| Position | The final round. "All the hiring rounds of our process will end here" | [CONFIRMED] official |
| Scheduling | You pick a slot; details arrive by email and WhatsApp | [CONFIRMED] official |
| Bring | Admit card + government photo ID — both are verified | [CONFIRMED] official |
| Decision basis | "Based on the overall performance" — the whole process, not just the interview | [CONFIRMED] official |
| Timeline | Official: results by Day 12. REV-001: interview mail 20–25 days after #4, results in a ~10-day window. These conflict | [UNKNOWN] |
| Length vs outcome | Length does not predict the result. 20-min → offer; 45-min → rejections | [REPORTED] |
The questions actually asked
Four are known close to verbatim from a selected candidate:
- Walk through your projects — expect depth on at least one.
- "Imagine you live in a society and you want to build a project that helps people living in it."
- What certifications or courses have you completed?
- "What tech are you most comfortable with, and can you switch between tech stacks within a month?"
Plus standard HR and cultural fit. And from a second selected candidate (Oct 2025): databases and operating systems came up and they credit it for their selection.
How technical is it, really?
REV-001: only 2–3 candidates per campus got genuinely technical questions, "not in depth" — but also "depends on the interviewer, be ready for both." The Oct 2025 account credits DBMS and OS knowledge.
Read it as: probably not deep, possibly present, and the variance is the panelist. Do not skip CS fundamentals, but do not build the prep around them either. The prep is your projects.
Does a weak coding round follow you in?
Not directly answerable. But the final decision is made "based on the overall performance", and REV-001 noted "each round had separate evaluation criteria." The honest reading: prior rounds almost certainly feed the final decision, but there is no evidence the panelist reads your code. Do not raise it. Be ready to discuss your approach if asked.
Part 3 — The honest uncertainty list
Everything below is genuinely unknown. Nothing in this library should imply otherwise.
Assessment #4
- The cut-off value. Confirmed to exist; never published.
- How many sections, and how many questions in each.
- Sample Accenture speaking topics. None exist anywhere online. The practice topics in this library are authored, not observed.
- Sample Accenture email prompts. Same — the two genre names are all that is known.
- Which grading product Accenture uses. Unresolved, and largely immaterial: prepare to the parameters Accenture publishes.
- Whether "10 seconds" covers reading plus answering, or answering only.
- Whether a failed recording can be retried.
- Whether you are told your score.
Interview
- The 12-day vs 20–25-day timeline conflict.
- Whether the panelist sees round #3's output.
- What weight the interview carries within "overall performance".
Structural
- Every candidate source describes the batch-2026 drive. There is no 2027-cycle account anywhere. The process could change.
- n = 2 for Assessment #4; n = 2 for the interview. One campus, one cycle, two voices.
Part 4 — The prioritised prep plan
Ordered by marks-per-hour, given the rubric and the evidence.
Assessment #4
| # | Priority | Why | Rough time |
|---|---|---|---|
| 1 | The hardware protocol | Free marks, and the only failure mode that voids your score entirely. Wired headset, broadband, quiet room, Chrome 110+. Do this first and test it once | 45 min, once |
| 2 | Email writing — the two genres | The only section with a published rubric (Etiquette/Content/Grammar), a known genre pair, and enough time to think. Highest yield per hour | 3–4 h |
| 3 | Listen-and-repeat + dictation accuracy | Two of seven verbal parameters are comprehension. Almost nobody practises this. Pure repetition gains | 2–3 h, spread |
| 4 | Read-aloud technique | Directly hits Pronunciation, Articulation, Fluency. Recording yourself is the whole method | 2 h, spread |
| 5 | Speak-on-a-topic — a 60-second structure | Single-sourced but high-yield. A reusable skeleton removes the freeze | 2 h |
| 6 | Grammar fill-in-the-blank + error correction | Scored under Grammar. Cheap drilling | 1.5 h |
| 7 | Jumbled sentences / story retelling | Unconfirmed for this sitting. Do only if time remains | 30 min |
Non-negotiable: fluency improves by repetition under time, not by reading. Every item above except #1 needs a microphone and a recording, not a highlighter.
Interview
| # | Priority | Why |
|---|---|---|
| 1 | One defence sheet per project | "Walk me through your projects" is the confirmed spine of the round, and depth on one is expected |
| 3 | The society scenario | Confirmed verbatim. A structured on-the-spot product answer, rehearsed once |
| 4 | STAR stories from real projects | True and specific. No invented metrics |
| 5 | Certifications and courses | Confirmed question, trivially preparable, easy to fumble |
| 6 | CS fundamentals refresh (DBMS, OS, OOP) | Low probability, low cost, and one account credits it |
| 7 | HR and closing, and the questions he asks | Standard, but the closing is where a flat interview is rescued |
Part 5 — What happens next
Phases 4 and 5 build the two libraries against exactly this picture.