Hey CF fam — many of you ask how to turn competitive programming skills into an offer from MAANG companies. Here’s a compact, battle-tested roadmap I’d post for anyone serious about making it happen.

1) Mindset first

Treat it like a long contest with phases: preparation → polishing → interviewing → negotiation.

Consistency beats intensity. Daily focused practice (1–3 hours) for many months wins.

Track progress (problem lists, mock interviews, resume versions).

2) What the companies actually test

Coding & algorithms: data structures, graph/tree/DP, greedy, bitmasks, complexity analysis.

System design (mid–senior roles): high-level system thinking, trade-offs, scalability.

Behavioral: clear communication, ownership stories, impact metrics.

(Optional) ML/infra/OS/DB knowledge for specific roles.

3) Concrete 6–12 month plan (competitive programmers)

Months 0–3 — Foundation

Master arrays, strings, sorting, two pointers, hashing, stacks/queues.

Implement all common D.S. from scratch (heap, union-find, segment tree basics).

Solve ~100 problems: easy→medium.

Months 3–6 — Core algorithms

DP (linear, knapsack, bitmask), graphs (BFS/DFS, Dijkstra, MST), advanced DS (fenwick/segment trees).

Solve 150–250 problems: medium→hard. Participate in CF contests weekly.

Months 6–9 — Polishing & system design intro

Timed mock interviews, blind 75 / leetcode premium lists.

Do ~20 timed mock interviews (pair with peers/interview coaches).

Start reading system design basics if applying to senior roles.

Months 9–12 — Interview phase

Intensify mocks, refine storytelling for behavioral questions.

Revise core templates: binary search, two pointers, DFS skeletons, hashing tricks.

Apply, schedule interviews, repeat until offer.

4) Weekly schedule (example)

Mon–Fri (1.5–2 hr/day): 1 problem (timed), 30–45 min theory/DS implementation or review.

Sat (3–4 hr): 2–3 contest-style problems or a CF/AtCoder contest.

Sun (2–3 hr): Mock interview or system design case + behavioral prep.

5) Interview day tactics

Read problem aloud, ask clarifying Qs, state constraints & complexity target.

Before coding: explain the approach and outline edge cases.

Write clean code, test simple cases aloud, and optimize if needed.

If stuck: present partial solutions, trade-offs, and what you'd improve with more time.