Start with the fundamentals, not random hard problems
Jumping straight into the hardest problems on a practice site before the basics are solid usually wastes time on frustration rather than learning. Spend the first stretch specifically on arrays, hash maps, strings, and basic recursion — the large majority of interview questions draw from this small set of core structures, combined in different ways.
A practical weekly structure
- Weeks 1–2 — arrays, strings, hash maps; easy-to-medium problems, focused on pattern recognition over speed
- Weeks 3–4 — trees, graphs, and recursion/backtracking; this is where most candidates' preparation is thinnest
- Weeks 5–6 — dynamic programming, plus a first full pass of mock interviews
- Ongoing — system design practice (for mid-level and senior roles) and behavioral question prep, run in parallel rather than left until the end
Practice explaining out loud, not just solving silently
An interview isn't graded solely on reaching a correct answer — it evaluates how you think out loud, how you handle a hint, and whether you can explain tradeoffs. Solving a problem silently at home builds a different skill than solving it while narrating your reasoning to another person; the second one is what the actual interview requires, and it needs its own separate practice.
The behavioral side is not an afterthought
Situation: Describe the context
Task: What was your specific responsibility
Action: What you actually did
Result: The outcome, ideally with a concrete detailThe STAR format keeps a behavioral answer concrete and complete instead of vague. Preparing three to five real stories in advance — covering a conflict, a failure, a technical challenge, and a leadership moment — means you're adapting a known story to the question asked, rather than improvising one from scratch under pressure.
Mock interviews matter more than solo practice, past a certain point. The nervousness and pressure of talking through a problem with another person watching is a real skill on its own, separate from problem-solving ability — and it only improves with actual practice under those conditions, not more solo problems.
What to do the day before
Review your prepared behavioral stories, skim a summary of core data structure complexities (not new problems), and stop grinding new material entirely. Cramming a new topic the night before an interview rarely helps and often just adds anxiety on top of material that isn't solid yet.
After the interview, regardless of outcome
Write down what came up — question types, what you struggled to recall, what went well — while it's fresh. This turns every interview, including ones that don't lead to an offer, into concrete input for what to study next, rather than an isolated, unexamined event.
Comments