Skip to content
AI Engineer Guide.

drill · drills · beginner · concept 27 of 33

30-day plan

0 of 33 complete

Why it matters

A month is enough to change performance and not enough to relearn a field. Plans fail when they are topic lists: read retrieval, read agents, read evaluation. Without a diagnosis, most time goes to material you already know because it feels productive. A workable plan starts from two or three observed weaknesses, assigns each a practice format, and reserves the final week for full rehearsals so the improvements are tested under realistic conditions.

Mental model

It is a training block, not a reading list: baseline, targeted work, then a taper into performance. The metaphor breaks because a training block has a coach measuring load, while you must be both athlete and coach, which is why timed artefacts matter.

How it works

Mechanism, step by stepInteractive
  1. 1Take one mock per format in the first three days and score them against a rubric to find the two weakest.
  2. 2Choose one primary weakness and one secondary, and assign each a weekly practice slot rather than a reading list.
  3. 3For each week, define a deliverable such as a timed design answer, a debugging write-up or a recorded behavioural story.
  4. 4Keep a daily thirty-minute recall drill for facts, separate from the practice work.
  5. 5Review the score sheet at the end of each week and drop an activity that is not moving it.
  6. 6In the final week, run two full loop simulations and fix logistics: environment, notes, timing and rest.

Step 1 of 6

Take one mock per format in the first three days and score them against a rubric to find the two weakest.

Step 1/6 · step 1

Figure. The mechanism in this page's own steps. The figure adds sequence, not new claims.

What to notice. A step can be read alone, but the order is the mechanism. The control lets you stop on any one.

Text version

The page's steps: 1. Take one mock per format in the first three days and score them against a rubric to find … 2. Choose one primary weakness and one secondary, and assign each a weekly practice slot rat… 3. For each week, define a deliverable such as a timed design answer, a debugging write-up o… 4. Keep a daily thirty-minute recall drill for facts, separate from the practice work. 5. Review the score sheet at the end of each week and drop an activity that is not moving it. 6. In the final week, run two full loop simulations and fix logistics: environment, notes, t…

  1. Take one mock per format in the first three days and score them against a rubric to find the two weakest.
  2. Choose one primary weakness and one secondary, and assign each a weekly practice slot rather than a reading list.
  3. For each week, define a deliverable such as a timed design answer, a debugging write-up or a recorded behavioural story.
  4. Keep a daily thirty-minute recall drill for facts, separate from the practice work.
  5. Review the score sheet at the end of each week and drop an activity that is not moving it.
  6. In the final week, run two full loop simulations and fix logistics: environment, notes, timing and rest.

Trade-offs

ChoiceGood forCostFails when
Depth on weaknessesLargest score improvementNeglects strengths that may decayThe loop weights your strong area heavily
Breadth across topicsFewer surprisesNo skill reaches interview qualityThe round is applied and rewards depth
Daily short sessionsSustainable and habitualLess time for full rehearsalsThe format requires stamina
Full mocks every dayRealistic pressureBurnout and no time to fix anythingYou have not diagnosed the weakness yet
Trade-off mapInteractive

Good for

Largest score improvement

Cost

Neglects strengths that may decay

Fails when

The loop weights your strong area heavily

  1. The loop weights your strong area heavily
  2. The round is applied and rewards depth
  3. The format requires stamina
  4. You have not diagnosed the weakness yet

Figure. Each choice with what it buys, what it costs, and the case where it loses.

What to notice. The fourth column is the decision: if the losing case describes your situation, the choice is wrong.

Text version

Four trade-offs: Depth on weaknesses is good for Largest score improvement, costs Neglects strengths that may decay, and fails when The loop weights your strong area heavily. Breadth across topics is good for Fewer surprises, costs No skill reaches interview quality, and fails when The round is applied and rewards depth. Daily short sessions is good for Sustainable and habitual, costs Less time for full rehearsals, and fails when The format requires stamina. Full mocks every day is good for Realistic pressure, costs Burnout and no time to fix anything, and fails when You have not diagnosed the weakness yet

Failure modes

  • Reading plan. Weeks pass with notes and no timed answer. Debug: check whether each week produced an artefact you could show someone.
  • No diagnosis. Preparation targets topics you already know because they feel comfortable. Debug: compare the first mock scores with the plan's time allocation.
  • Crammed final week. New material arrives too late to become fluent and displaces rehearsal. Debug: check whether the last seven days contain any new topic.

In production

Book the real interviews before the plan starts, so the deadline is fixed. Keep a score sheet per format and stop any activity that has not moved a score in two weeks.

Common misconceptions

People think: Thirty days is enough to cover the whole field.

Actually: It is enough to fix two or three specific weaknesses and rehearse them, which is what moves a score.

People think: More study hours always help.

Actually: Unfocused hours produce familiarity, which is why timed artefacts and mocks are the unit of progress.

Interview angle

Asked to plan a month, strong candidates start from a diagnosis, allocate time to two named weaknesses and define a weekly artefact. They also say what they are deliberately not doing. Weak answers list topics and hours with no checkpoint.

Sources