Competitive programming · 1,467 problems · 17 rating ladders · 32 topic ladders

Codeforces Ladders

Every problem here is pulled from the live Codeforces API with its real rating and solve count — nothing invented. Rating ladders are the spine; topic ladders are ramps through one tag, ordered easiest first.

How to actually use this

More problems is not the thing that improves you. These four are, and they are what strong competitors point at when asked.

1 · Ladder, do not wander

Work at your current rating and +100. When roughly 8 in 10 land inside 35 minutes, step up one rung. Jumping ahead feels productive and teaches nothing.

2 · Time-box at 35 minutes

Then read the editorial. Staring for three hours is the single biggest waste in competitive programming — the learning is in reading the solution after real struggle.

3 · Upsolve every contest

Do a virtual contest, then solve everything you could not finish during it. This is the habit most often named as the thing that actually moved someone’s rating.

4 · Re-solve failures after a week

A problem you needed the editorial for is not learned. Re-solve it cold seven days later. This is pattern recall under time pressure, and it decays.

One caveat, stated plainly: this is competitive programming, not Software Engineer interview prep. It will sharpen your implementation speed, binary search and graph instincts. It will also spend a lot of your time on constructive algorithms, number theory and game theory that interviews never ask about. Use it knowingly alongside the DSA track, not instead of it.

0 / 1,467 solved

1,467 distinct problems across 2,400 ladder slots · snapshot taken 2026-08-30 from the Codeforces API · pool of 11,087 rated problems

A problem can sit in several ladders at once — ticking it marks it solved in all of them. Ratings and solve counts drift over time; re-run the generator to refresh.

Back to the ledger →

Made By Jatin Bhargava · 2026