Phase 6 — Competitive Mastery

M8.5 – M9 | Weeks 34–36+ | April 7–27, 2027

You made it here. Eight and a half months ago you sat down with shaky C++ syntax and a rough idea of what Big O notation meant. Now you’re entering the phase where the work stops feeling like drilling and starts feeling like playing a game you’re genuinely good at.

This is not the phase where you become a Codeforces tourist. This is the phase where the architecture you’ve built — complexity intuition, graph reasoning, DP decomposition, data structure fluency — gets put under time pressure, and you discover it holds.

What “Competitive Mastery” Means for You Specifically

Not every definition of “competitive mastery” applies to you. You’re a working ML engineer, not a full-time CP student. You have 10–15 hours a week, a full-time job, and a specific goal: rebuild genuine CS foundations and prove it publicly.

For you, competitive mastery means:

  • You sit down at a LeetCode Hard and don’t freeze. You have a process.

  • You recognize the pattern for roughly 70% of LeetCode Hards within 5 minutes of reading.

  • You enter a Codeforces Div. 2 contest and solve A+B comfortably, make a real attempt at C, and occasionally crack D.

  • You finish LeetCode weekly contests in the top 30–40% consistently.

  • You can explain why your solution works, not just that it works.

  • You feel something close to enjoyment when a Hard problem clicks.

That’s the target. Not Codeforces blue. Not LeetCode Guardian. Not ICPC finalist. A working engineer with genuine algorithmic depth who can walk into any technical interview, competitive round, or system design discussion and reason clearly.

The Mindset Shift This Phase Requires

Every previous phase asked you to learn something. This phase asks you to compete with what you know.

The shift: stop asking “can I solve this?” and start asking “what is this problem’s structure, and how do I enjoy the hunt of finding it?”

That sounds abstract. Here’s what it means in practice: when you open a problem and don’t immediately know the answer, your old response was anxiety. Your new response is curiosity. You’ve seen enough patterns. You know the toolkit. The question is which tool fits — and figuring that out is the fun part.

The competitors who plateau at this stage are the ones who never make this shift. They keep treating unsolved problems as evidence of inadequacy. The ones who break through treat unsolved problems as puzzles. There is a real difference in how those two states feel in your body when you sit down to compete.

What You Can Do at M9 — The Exit State

By April 27, 2027, you will be able to:

  1. Solve LeetCode Hards deliberately — not always, not easily, but with a structured approach instead of a blank stare

  2. Identify patterns under time pressure — constraints tell you the complexity class, keywords narrow the technique

  3. Compete in Codeforces Div. 2 with a realistic rating in the Pupil–Specialist range (1200–1450), which for a working professional with 9 months of structured effort is an honest, hard-won achievement

  4. Complete LeetCode weekly contests top 30% consistently

  5. Read an editorial without shame — and extract a reusable pattern, not just a solution

  6. Maintain a personal template library that you can deploy from memory in under 2 minutes

  7. Explain any solution you write — the invariant, the time complexity, the edge cases, the reasoning chain

None of this is given to you. All of it is earned by the 7 files in this folder.

The Emotional Payoff

Here’s the honest version of why this is worth it: you started this because AI was doing the coding and you felt hollow. You felt like the reasoning muscle was atrophying. You took 9 months to rebuild it from scratch, the right way, under your own power.

The payoff is not a rating number. The payoff is the moment you sit down at a problem — under contest pressure, timer running — and you recognize the structure. The edge collapses from the problem and you see the graph underneath, or the DP formulation, or the monotonic invariant. And you build the solution yourself, and it’s correct.

That moment is not available for purchase. It is not granted by a certificate. It exists only because you did the work.

That’s why it’s worth it.

Files in This Folder

File

What It Covers

01_contest_strategy.md

How to actually compete — the first 5 minutes, time boxing, upsolver habit

02_pattern_recognition_at_speed.md

Constraints as clues, keyword-to-pattern maps, the 3-second glance

03_reading_editorials_correctly.md

The correct protocol, sources, what most people do wrong

04_stress_testing_and_debugging.md

Brute-force + optimized comparison, common bugs, edge case checklist

05_template_library.md

What to template, template hygiene, full specs for 6 core templates

06_deliberate_practice_protocol.md

The meta-skill: what deliberate practice actually means for CP

07_exit_criteria_and_final_state.md

The M9 destination — behavioral markers, the pitch, what comes next

Time Budget for This Phase

You have roughly 3 weeks and 45–50 hours total.

Activity

Hours/Week

Priority

Live Codeforces contests (2–3/week)

5–6h

High

Upsolving after each contest

3h

Critical

LeetCode weekly contest + review

2h

High

Template library building/testing

2h

Medium

Deliberate practice (tagged problems, virtual contests)

3–4h

High

Don’t try to cover new theory in this phase. Your job is to deploy what you built.

Navigation: ← Phase 5: Advanced Topics | 07 Exit Criteria → | Back to Roadmap