Cramming four topics in seven days leaves you shallow in all of them. This plan spends more than half the week on the single round most likely to fail you.
Written after two rushed weeks, one good and one bad · Updated September 2026 · 7 min read
Seven days is not enough to learn everything. It is enough to fix one thing properly.
The short version: day seven is an honest audit, days six to four go entirely on your weakest round, day three is one mock with a person, day two is your stories and questions, and day one is rest and logistics. Seven days is enough to fix one thing, and that is usually enough.
If you have four weeks, do this plan and then repeat the middle section. If you have two days, skip to the last three rows.
The week I wasted
Four topics, seven days, nothing learned.
My first crash week looked productive. A bit of dynamic programming, a bit of system design, some SQL, a few behavioral notes. On the day, the system design round exposed that I had skimmed rather than understood, and everything else I had touched was equally thin.
The second time, I gave more than half the week to the one round I dreaded. It was the only round that went well, and it was enough.
Seven days buys depth in one place or shallowness everywhere. Choose on day seven.
Day 7: the audit
One timed attempt per round type.
The one you avoided scheduling is usually the weakest.
Days 6 to 4: the weak round
Three days on one thing.
Three days is enough to move one round from panic to competent.
This is where a practice tool earns its place, because you need volume and instant feedback rather than a person. I used Phantom Code AI [https://www.phantomcodeai.com/]for these three days, attempting first and then comparing the approach and complexity, and its slower mode for the system design version of this plan. Covering SQL and behavioral rounds in the same tool mattered during a short week, since I had no time to assemble a toolkit.
Day 3: one mock with a person
The part you cannot fake alone.
A friend, a colleague, anyone willing to interrupt you. Ask them to push back once, ask "why" twice, and tell you afterwards what your delivery was like. This single session reliably produced my biggest fixes, usually about pace rather than content.
Day 2: stories and questions
Low effort, high return.
Prepare
Two project stories: problem, decision, result
One failure story you have actually processed
Three questions to ask them
A 60 second background answer
Skip
New topics
Reading interview horror stories
Rewriting your resume
Anything that raises anxiety without adding skill
Day 1: logistics and rest
Boring and important.
Test the setup
Link, camera, microphone, editor, backup contact.
One easy warm up
A problem you can solve, for confidence rather than learning.
Sleep
The single highest return activity of the week.
Plan the morning
Food, travel or login time, and a buffer.
Common questions
Short answers.
Can I prepare in one week?
How do I find the weak round?
Cram the night before?
How many problems a day?
Depth in one place beats panic everywhere
Every rushed week I have done badly was a week spread thin. The one that worked looked lazier on paper and went deeper where it counted.
Do the audit tonight. Whatever you avoid scheduling is the thing to spend the week on.
Written on a Sunday, calmly for once
What is your weakest round?
Be honest, that is the whole method.
Some third-party reviews of these tools are published by competing products, so verify prices on official sites before buying.
Top comments (0)