The AmplifierReal cases · Student · Final year
Aarav, 21: placement season, three weeks, no story
A decent CGPA, three projects he cannot fully explain, and a résumé a tool wrote that sounds like everyone else's.
Planned for release phase 2. The page is complete as a draft; interactive parts run in the browser and do not yet save to an account.
In brief
The situation. Aarav is in his final year of computer engineering at a college in Nagpur. Placements start in three weeks. He has a 7.8 CGPA, three projects — two of which were largely generated — and a résumé he had an AI polish into something that reads well and describes nobody in particular. In his first mock interview a senior asks him to explain the caching strategy in his own project and he cannot. He recognises, with a cold feeling, that he has been Abhi.
Step 1 — Define the End State
Not "get placed". "Walk into the interview room with one project I can defend line by line for forty minutes, a résumé that sounds like me, and answers to the five questions I am most afraid of. The interviewer should leave thinking: he built that." Audience: one specific interviewer, and the version of himself sitting across from her.
Step 2 — Map the Flow
His list: pick one project, relearn it completely, rebuild the parts he does not understand, rewrite the résumé, prepare the fear questions, mock interviews. AI review adds: a gap list per project (what would an interviewer probe?), and a timeline that works backwards from the first company date — he had three weeks and no calendar. It suggests "learn system design"; he declines: three weeks, one project, depth over breadth.
Step 3 — Assign Tasks
Choosing which project: his (only he knows which he half-understands and half-loves). Generating the probable interview questions per module: AI, verifiable against the code. Explaining the generated parts of his own code back to him: AI as tutor; the re-implementation by hand: his. Résumé: he writes every line himself; AI is allowed only to check for jargon and length. Mock interviews: humans — two seniors and a cousin.
Step 4 — Select the Tool
A coding assistant inside the editor, used in a new mode — "explain, don't write" — and a conversational tool for question generation and for critiquing his spoken answers, which he records and transcribes with a voice tool.
Step 5 — Prepare and Direct
Criteria: I can rewrite any function in the project from a blank file; I can answer "why this and not that?" for every design choice; every résumé line names something I did, in my words; my recorded answers are under ninety seconds and contain no phrase I could not expand on. Plain-language brief, then the tool's optimised version, one edit: "assume I will lie to myself; make me prove it."
Steps 6 and 7 — Execute and Evaluate
The caching module fails the blank-file test three times. He rebuilds it, smaller, understanding it this time. The résumé draft he writes himself is clumsy and he is tempted to let the tool smooth it; he checks the criterion — his words — and keeps the clumsy version, fixing only length. The recorded answers fail the ninety-second criterion at first; the transcripts show him padding.
Step 8 — Integrate and Stress-Test
Assembled: the project, the résumé, the answers, tested in a mock with a senior who is deliberately unkind. Small fixes: two answers too long, one résumé bullet still vague. Structural: the résumé still lists the two projects he cannot defend, and the interviewer goes straight to one. A Step 3 problem — he had kept them on the résumé as "human task, leave it" without deciding. He removes them. A shorter résumé he can stand behind entirely.
What changed
He walks in with less on paper and more in his head. He is asked about the caching strategy. He explains it. The interviewer says, "That's the right answer" — or something like it. Three weeks was enough because he used them on depth.
One project, defended fully, beats three you cannot explain. Set "explain, don't write" as the tool's mode when the goal is capacity. Record yourself; the transcript is the criterion.
A composite case, not a client engagement; the person is invented, the situation is not.