Is It Okay to Solve the Same Problems Multiple Times for Revision?

Is It Okay to Solve the Same Problems Multiple Times for Revision?

Not only is it okay, it's one of the best things you can do.

A lot of students feel guilty when they revisit old problems. They think they should always be solving new questions because that's what "real progress" looks like. The result is that they solve hundreds of problems once, forget most of them a few weeks later, and then wonder why they struggle in interviews.

The goal of DSA preparation is not to see as many problems as possible. The goal is to develop pattern recognition and problem-solving ability.

Revision plays a huge role in that process.

Why Re-Solving Problems Works

When you solve a problem for the first time, you're usually focused on understanding the pattern and getting to a working solution.

When you solve it again later, something different happens.

You start recognizing the underlying idea more quickly. You remember the mistakes you made before. You understand why the approach works instead of just following the steps.

This strengthens your memory and helps turn concepts into instincts.

Interviews Reward Recognition

In interviews, you're rarely expected to invent a completely new algorithm.

Most interview questions are variations of common patterns such as:

• Sliding Window
• Two Pointers
• Binary Search
• BFS and DFS
• Dynamic Programming
• Greedy Algorithms
• Hashing

The more times you revisit these patterns, the faster you'll recognize them in new problems.

That's exactly what interviewers are testing.

Don't Memorize, Understand

There's an important difference between revision and memorization.

If you're simply remembering every line of code, you're not gaining much.

Instead, focus on answering questions like:

• Why does this approach work?
• What clues in the problem suggest this pattern?
• What alternative solutions exist?
• What is the time and space complexity?

The objective is to strengthen understanding, not memorize code.

How Often Should You Revisit Problems?

A common strategy is:

• Solve a problem today.
• Revisit it after a few days.
• Revisit it again after one or two weeks.
• Revisit it before interviews.

This form of spaced repetition helps retain concepts far better than solving a problem once and never seeing it again.

Balance Revision and New Problems

Revision is valuable, but it shouldn't replace exposure to new problems entirely.

A good approach is to split your practice between:

• New problems for learning patterns.
• Old problems for strengthening retention.

Many successful candidates spend a portion of every week revisiting previously solved questions.

The Honest Truth

Students often believe that solving 500 unique problems is better than solving 200 problems deeply and revisiting them multiple times.

In reality, the second approach usually produces stronger interview performance.

If you can revisit an old problem, identify the pattern immediately, explain the reasoning, and implement the solution confidently, that's a sign that the concept has truly become part of your problem-solving toolkit.

So yes, solving the same problems multiple times is not a waste of time. It's one of the most effective ways to build long-term DSA mastery.