The Prep Loop: Solve, Capture, Review, Prove

Most people do not fail interview prep because they are lazy.

They fail because their prep has no memory.

A problem gets solved on one platform. A note gets written somewhere else. A weak pattern gets forgotten. A revision reminder never comes back at the right time. After a few weeks, the candidate has done a lot of work, but the work is scattered across tools, tabs, screenshots, bookmarks, and vague confidence.

That is the problem the Prep Loop is meant to solve.

A good prep system should not only help you solve more problems. It should help every solve become part of a larger cycle:

Solve. Capture. Review. Prove.

1. Solve

Solving is where the loop begins, but it is not where prep ends.

Most candidates treat solving as the whole game. They open a problem, try to get accepted, maybe look at an editorial, and move on. That feels productive because the action is visible. The problem count goes up. The streak continues. The profile looks active.

But an accepted solution does not always mean the idea is yours yet.

Sometimes you solved it because the pattern was fresh. Sometimes the constraints pushed you toward the answer. Sometimes the editorial helped more than you want to admit. Sometimes you understood the code, but not the reason you should have chosen that approach in the first place.

That does not make the solve worthless. It just means the solve is raw material.

The goal of the first step is simple:

Get a real attempt into the system.

Not a perfect attempt. Not a polished explanation. A real attempt with enough signal to understand what happened.

A useful prep system should notice:

• What problem you solved
• Which platform it came from
• How hard it was
• Which topics were involved
• Whether you solved it cleanly or struggled
• Whether it should come back for review

Solving creates the event. The next step turns that event into memory.

2. Capture

This is where most prep systems break.

After solving, candidates often move on too quickly. They assume the learning has already happened because the submission was accepted. But the most valuable part of a solve is often the insight you almost forget five minutes later.

Capture is the act of saving the useful part of the solve.

Not everything. Just the part future-you needs.

A good capture might answer:

• What was the pattern signal?
• What was the trap?
• What mistake did I make first?
• What made the final approach work?
• What should I remember when this pattern appears again?

For example, after a sliding window problem, the review note might be:

Use sliding window when the problem asks about a contiguous range and the condition can be maintained while expanding or shrinking.

That note is more valuable than pasting the whole solution. The code may change from problem to problem, but the recognition signal is what helps you solve the next one faster.

Capture should be small, honest, and reusable.

If it takes too long, you will not do it consistently. If it is too vague, it will not help later. The best notes feel like a shortcut back into the mental model.

3. Review

Review is where solved problems become durable.

Without review, prep becomes a treadmill. You keep adding new problems, but old ideas quietly decay. This is why someone can solve 300 problems and still feel nervous when a familiar pattern appears in an interview.

The issue is not effort. It is timing.

A problem should return when it is useful to see it again:

• after the first solve
• after the first mistake
• after enough time has passed to test memory
• before a related harder problem
• when a weak topic keeps appearing

Review should not feel like starting over. It should feel like reopening the right context at the right time.

That is why capture matters. A review session is stronger when it includes the original signal, mistake, and takeaway. Instead of asking, “What was this problem again?”, you can ask, “Do I still understand why this approach worked?”

Good review is not passive rereading. It is a check for retrieval.

Can you explain the pattern without looking? Can you rebuild the approach? Can you spot the trap faster than last time?

If yes, the problem is becoming part of your working memory. If not, it should stay in the loop.

4. Prove

The final step is proof.

Proof is different from activity. Activity says, “I solved problems.” Proof says, “I am getting stronger in ways that matter.”

A prep system should help you see evidence of progress:

• weak topics becoming stable
• review items getting easier
• repeated mistakes disappearing
• similar problems taking less time
• harder variants becoming approachable
• notes turning into reusable pattern recognition

This matters because interview prep has a confidence problem.

Candidates often do not know whether they are ready. They rely on streaks, total solved counts, or vibes. Those signals can be motivating, but they do not always reflect readiness.

Proof should be based on behavior.

Can you return to a problem after time away and still solve it? Can you explain the tradeoff? Can you recognize the pattern in a new wrapper? Can you recover from a mistake without needing the full answer?

That is real progress.

Why the loop works

The Prep Loop works because it treats each solve as part of a system.

A single accepted submission is useful. But a solve that is captured, reviewed, and proven becomes much more powerful.

It becomes:

• a memory
• a signal
• a future review item
• a progress marker
• a guide for what to do next

This is also where AI can be useful.

AI should not simply hand you answers. In a serious prep system, AI should help connect the loop. It should notice patterns in your attempts, surface weak areas, suggest what to review, and help you decide what to solve next.

The best AI in interview prep is not the loudest assistant. It is the one that remembers enough context to guide the next move.

The better question

Instead of asking, “How many problems did I solve today?”, ask:

What did today’s solves add to my loop?

Did they reveal a weak pattern?
Did they create a review note?
Did they prove something you had previously struggled with?
Did they make tomorrow’s next step clearer?

That shift changes the quality of prep.

You stop chasing volume for its own sake. You start building a system that compounds.

Final thought

Interview prep should not feel like repeatedly starting from zero.

Every problem should leave something behind. Every mistake should become signal. Every review should make the next solve sharper. Every week should give you clearer proof that your prep is working.

That is the Prep Loop:

Solve to create signal.
Capture what matters.
Review before it fades.
Prove progress over time.

That is how practice becomes readiness.