Six weeks is a planning horizon, not a guarantee of readiness. Start with the role, your current capabilities and the time you can actually commit. Each week should produce evidence you can inspect.
If a plan says only “study probability” or “improve coding,” make its output more specific before putting it on the calendar.
The sequence
| Week | Main work | Output |
|---|---|---|
| 1 | Read relevant roles and attempt a diagnostic | Role matrix and two observed gaps |
| 2 | Repair the highest-priority gap | Fresh explanation or solution demonstrating the repair |
| 3 | Finish a bounded project | Reproduction instructions, result and limitation memo |
| 4 | Rebuild the resume from evidence | Verified document and support for its main claims |
| 5 | Practice changed assumptions and follow-ups | Two specific debriefs and a revised priority list |
| 6 | Apply, manage scheduling and reassess | Current tracker and next-cycle plan |
The sequence can overlap. A live application deadline may require an earlier resume revision. Preserve the reason for changing the plan rather than treating the original schedule as sacred.
Allocate by observed weakness
For six available hours, one illustrative split is two hours on the main technical gap, two on the project, one on applications and one on review or a mock. This is not an optimized formula.
A PhD candidate who struggles to explain their contribution may benefit more from a short research discussion than another familiar calculation. An engineer preparing for a stated coding round may need to prioritize the relevant technical work. Use evidence and the actual process.
Make progress visible
Keep the first attempt from week one. Compare it with a fresh attempt later. Memorizing the original answer is weaker evidence than handling a changed sampling rule, input constraint or evaluation boundary.
For a project, ask whether another reader can reproduce and explain the central result. For a resume, ask whether every claim is accurate and whether its relevance is clear. Completion should be observable.
Recover from a missed week
Do not move every unfinished task into the next week. Retain the output that affects your next decision most, remove optional work and revise dates. A realistic smaller task can preserve progress; an impossible backlog usually conceals priorities.
Use the probability error log, project selection guide and application tracker as free starting tools. The complete preparation library combines the three books when you need their respective scopes; one relevant book may be enough for a narrower gap.
01 / Probability & trading
Reason through the question.
Conditioning, expectation, stopping and uncertainty. Forty original exercises, full solutions and two mock sessions that change the assumptions.
02 / Research projects
Build something you can defend.
A reproducible synthetic study, from the data contract to the research memo. Investigate leakage, changing relationships and rolling estimates.
03 / Career preparation
Make your evidence count.
Choose a role direction, translate technical work and organize the next six weeks. Three worked candidate cases and editable planning sheets.
Choose the scope you need
Self-directed practice or written feedback.
Only need document feedback? Written resume review · $149.
Free samples are available for every book. Reviews begin after complete intake and are subject to available capacity.