Skip to content
Tutorials Center
My learning

Topics

Lesson 4 of 77 ยท How Interviews Work

Building a Study Plan and Practice Routine

Build an interview study plan with spaced repetition, mock interviews and a weak-topic tracker, then run a small spaced-repetition scheduler yourself.

Most people prepare for interviews the same way: read a lot, solve a few problems at random, panic the night before. The facts you read on Monday are mostly gone by Friday. A plan that fits memory research and your real schedule beats an occasional cram, even if the total hours are lower.

This lesson builds a practical routine: how to spread study over time with spaced repetition, how to use mock interviews, how to track weak topics, and how to size a plan for the weeks you actually have. You will also run a small spaced-repetition scheduler.

The three loops of preparation

Three loops, three skills

Recall Facts and definitions, reviewed on a schedule.
Solve Problems from scratch, no solution peeking.
Perform Mock interviews under time pressure.

Each loop fixes a different failure.

1 / 2

Recall is for things you need to say fluently: what a closure is, the difference between a process and a thread, the complexity of common operations. Solve is for problems you must work out: it builds the pattern recognition that cannot be memorized. Perform is for the live part: talking, being timed, and being watched. Skipping a loop leaves a predictable hole. People who only read blank under a timer; people who only solve problems cannot explain trade-offs.

Spaced repetition in one idea

Memory fades quickly after learning and more slowly each time you successfully recall something. So review an item just before you would forget it: after a day, then a few days, then a week, then a month. Items you get right move to longer gaps; items you miss start over.

A simple version that needs only paper boxes is the Leitner system: five boxes, reviewed at different frequencies. Correct cards move up a box, wrong cards drop back to box one. A software version stores a "next review day" per card.

The intervals below (1, 3, 7, 14, 30 days) are a common, reasonable choice, not a scientific constant. Tools differ, and what matters is reviewing regularly and recalling actively rather than rereading.

A scheduler you can run

This stand-in simulates a small deck over 11 days. The "learner" answers from a fixed script, so the output is deterministic. Real flashcard apps work the same way at a larger scale.

JS Spaced-repetition scheduler

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Look at what happens to "Process vs thread?": it is missed on day 0 and returns after one day, while correctly remembered cards drift to longer gaps. You spend time where you are weakest.

Writing good cards

  • One idea per card. "List five facts about HTTP" is a bad card; "Which HTTP method is idempotent but not safe?" is a good one.
  • Make cards from your own mistakes. A missed practice question becomes a card the same day.
  • Use why questions, not only what. "Why is 0.1 + 0.2 !== 0.3?" teaches more than a definition.
  • Answer out loud before flipping the card.

Mock interviews

A mock interview is the only practice that trains the whole loop at once: nerves, narration, and time.

  • Use a person if you can. A friend, a colleague, or a peer practice group. Ask them to follow the structure from How Technical Interviews Work: problem solving, communication, collaboration.
  • Solo version. Pick a problem, set a 35-minute timer, explain out loud as if someone listens, and record your screen and voice. Review the recording; you will notice silences and filler words immediately.
  • Score yourself with the rubric, then compare after a week. Scores that rise over time show the routine works.
  • Do the first mock early, not at the end. It exposes what to study.

Track your weak topics

Keep a simple tracker. After each practice session record the topic, whether you solved it alone, with hints, or not, and the mistake. Review the tracker once a week and let it choose next week's focus. The tracker can be a spreadsheet; here is the same idea as a stand-in:

JS A weak-topic tracker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The weights are arbitrary; the habit is the point. Without a record, people keep practicing what they already like.

Fit the plan to your calendar

  • Four weeks or less: prioritize your main language's core, arrays/strings/hash maps, one system design pattern, and your stories. Mock interviews weekly.
  • Eight to twelve weeks: add all data structure families, SQL, and a broader language review. Two mocks a week near the end.
  • Always: reserve the last two days for rest, light review and logistics, not new topics.

Study time matters less than consistency. Forty-five minutes five days a week beats a six-hour Sunday.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What is the main idea behind spaced repetition?

    Each successful recall strengthens memory, so the gap before the next review can grow.
  2. 2. Which loop does a mock interview train?

    Mocks add the live elements, nerves, timing and narration, that solo study cannot.
  3. 3. What should you do with a practice question you missed?

    Mistakes show where to focus; a card plus a tracker entry makes sure you revisit them.
  4. 4. Which is the best use of the last two days before an interview?

    New topics rarely stick that late, while rest and calm help performance.

Summary

  • Prepare in three loops: recall, solve and perform.
  • Spaced repetition reviews items on growing gaps; misses reset the gap.
  • Good cards hold one idea, ask why, and come from your own mistakes.
  • Mock interviews, even solo and recorded, train narration and time pressure.
  • A weak-topic tracker keeps your practice honest; consistency beats long cram sessions.

Next: JavaScript: Types, Coercion and Equality