Interview prep · Study plan · Software engineering
Technical Interview Prep: A Day-by-Day Plan
A technical interview tests four different skills, and most candidates only practise one. This guide gives you a 28-day plan that covers all four, a 7-day version for short notice, and a way to use curated questions and answers without just memorising them.
By the TestLab team · · 9 min read
Most candidates prepare for a technical interview by solving coding problems, and nothing else. Then the interview opens with “walk me through your last project”, moves to “what happens when a process forks?”, and ends with “tell me about a time you disagreed with a teammate”. The coding round went fine. The offer didn’t come.
A technical interview loop tests four different skills, and each one needs its own practice. This guide explains what each round checks, gives you a day-by-day plan for 28 days (and a 7-day version for when the call comes at short notice), and shows how to use curated interview questions and answers without falling into the trap of memorising them.
What a technical interview actually tests
Companies run different loops, but almost every software role draws from the same four areas:
-
Coding and problem solving. One or two problems in 30 to 45 minutes, usually on arrays, strings, hashing, trees, graphs or dynamic programming. The interviewer watches how you get to a solution: clarifying the problem, choosing an approach, talking through trade-offs, testing your own code.
-
Technical concepts. Questions on the fundamentals behind your work: operating systems, databases, networks, the language and frameworks on your résumé, and for many roles cloud, DevOps or machine learning. These are often short spoken answers followed by “why?”.
-
System design. Usually for mid-level and senior roles: design a URL shortener, a chat app, a news feed. It checks whether you can break a problem into components, reason about scale and data, and explain trade-offs.
-
Behavioral and project questions. Your projects, decisions, conflicts, failures and impact. Many companies weigh this round as heavily as coding, especially for senior roles.
Freshers usually get more of the first two. Experienced candidates get more of the last two. Look at the job description and any interview guide the recruiter sends, then adjust the plan below.
Before you start: three decisions
-
One language. Use the language you know best for every coding round, and learn its standard library well: sorting with a custom key, hash maps, heaps, deques. Switching languages mid-preparation costs more than it gains.
-
A fixed daily slot. About two hours on weekdays and three to four on weekend days is enough for this plan. A fixed time beats occasional long sessions.
-
A notebook or doc for mistakes. Every problem you fail and every concept question you can’t answer goes into it, with one line on what you missed. This list is what you revise in the final week.
How to use curated questions and answers (without memorising them)
Curated question banks are useful because they show you what interviewers actually ask, in one place, at the right depth. They are harmful if you use them as scripts. Interviewers follow up on anything that sounds memorised, and a recited answer has nothing behind it.
Use each question like this:
-
Read only the question. Cover the answer.
-
Answer out loud in about 30 seconds. That is the length of a strong first answer in an interview.
-
Compare with a short reference answer. Did you get the core idea, the right terms, and an example?
-
Read the full explanation for anything you missed, then try your short answer again.
-
Mark it as known or to revise, and come back to the “revise” ones after one day, then three, then seven.
This is retrieval practice plus spaced repetition, the two study methods with the strongest research behind them. Our guide to spaced repetition for interview prep explains why it works.
TestLab’s interview questions are built for this method: 12,000+ reviewed questions across about 190 technologies, each with a short answer to practise saying and a full answer for the follow-ups. They are grouped into CS fundamentals, data structures and algorithms, system design, web and mobile development, cloud and DevOps, machine learning, generative AI and behavioral questions. You can read a few full answers free. Full access, the day-by-day interview plan and the daily spaced review are part of the paid plan.
For coding practice you need a judge that runs your code, so use LeetCode, HackerRank or NeetCode’s problem lists alongside a concept bank. For system design, the free System Design Primer on GitHub is the standard starting point.
The 28-day plan
Each day has three blocks: coding (about 60 minutes), concepts (about 40 minutes, using the question method above) and spoken practice (about 20 minutes: behavioral answers, project stories or explaining a concept out loud). Weekend days add a longer review or a mock interview.
Week 1: Foundations
| Day | Coding | Concepts | Spoken practice |
|---|---|---|---|
| 1 | Arrays: two easy problems, then one medium | Big-O notation and complexity | Write your 60-second “tell me about yourself” |
| 2 | Strings and hashing | Arrays and hash tables (how they work inside) | Say your introduction out loud and record it |
| 3 | Two pointers | Your main language: memory, types, collections | Project 1: problem, your role, stack, result |
| 4 | Sliding window | Your main language: concurrency or async basics | Project 1: the hardest bug and how you fixed it |
| 5 | Stacks and queues | Operating systems: processes, threads, scheduling | Project 2: same structure as project 1 |
| 6 | Timed set: three problems in 90 minutes | Review every “revise” question from days 1–5 | Behavioral: a time you learned something fast |
| 7 | Redo every problem you failed this week | Rest, or light review only | Listen to your recordings and fix one habit |
Week 2: Core data structures
| Day | Coding | Concepts | Spoken practice |
|---|---|---|---|
| 8 | Linked lists | Operating systems: memory, paging, deadlock | Behavioral: a disagreement with a teammate |
| 9 | Binary trees: traversals | DBMS: keys, normalization, joins | Behavioral: a mistake you made and what changed |
| 10 | Binary search trees | DBMS: indexes, transactions, isolation | Explain “what is an index?” in 30 seconds |
| 11 | Heaps and priority queues | Computer networks: TCP vs UDP, DNS, HTTP | Explain “what happens when you type a URL?” |
| 12 | Binary search, including on answers | Networks: HTTPS, TLS, caching, CDNs | Behavioral: a time you had too much to do |
| 13 | Mock interview: one problem, out loud, 45 minutes | Review this week’s “revise” questions | Ask a friend for honest feedback |
| 14 | Redo failed problems | Rest, or light review | Update your mistake list |
Our DBMS and SQL interview guide covers days 9 and 10 in depth.
Week 3: Harder patterns and your stack
| Day | Coding | Concepts | Spoken practice |
|---|---|---|---|
| 15 | Graphs: BFS and DFS | Your framework (for example React, Spring, Django): lifecycle and data flow | Behavioral: leading something without authority |
| 16 | Graphs: topological sort, shortest path | Your framework: performance and common pitfalls | Project deep dive: draw its architecture |
| 17 | Backtracking | Testing: unit vs integration, mocking | Behavioral: a time you pushed back on a decision |
| 18 | Dynamic programming: 1D | Cloud or DevOps basics your role needs | Explain a trade-off in your project |
| 19 | Dynamic programming: 2D | Security basics: authentication, hashing, OWASP | Behavioral: your biggest impact |
| 20 | Mock interview with a peer or a mock platform | Review all “revise” questions so far | Get feedback on how you explain |
| 21 | Redo failed problems | Rest, or light review | Rewrite weak behavioral stories |
Week 4: System design, mocks and polish
| Day | Coding | Concepts | Spoken practice |
|---|---|---|---|
| 22 | Mixed medium problems, timed | System design: scaling, load balancing, caching | Design a URL shortener out loud |
| 23 | Mixed medium problems, timed | System design: databases, sharding, replication | Design a chat or messaging app |
| 24 | Your weakest pattern | System design: queues, consistency, rate limiting | Design a news feed or notification system |
| 25 | Full mock: coding round | Review the mistake list | Prepare three questions to ask the interviewer |
| 26 | Full mock: design or concepts round | Review all “revise” questions | Full behavioral mock |
| 27 | Two easy problems only, to stay sharp | Light review of your strongest topics | Re-record your introduction |
| 28 | Rest | Rest | Logistics: time, link or address, ID, setup |
If your role has no system design round, use week 4’s concept blocks for more of your own stack and more mocks. If you are a senior candidate, start system design in week 2 and give it a block every day.
The 7-day plan for short notice
When the interview is a week away, cut breadth and keep the method:
| Day | Focus |
|---|---|
| 1 | Read the job description. List the 5 topics most likely to come up. Write your introduction and two project stories. |
| 2 | Coding: arrays, strings, hashing (the most common round topics). Concepts: your main language. |
| 3 | Coding: trees and graphs. Concepts: the core subject closest to the role (databases for backend, networks for infrastructure, and so on). |
| 4 | Coding: one timed mock. Concepts: your framework. Spoken: four behavioral stories. |
| 5 | System design (if relevant) or more of your stack. Review every “revise” question so far. |
| 6 | Full mock interview with a friend. Fix the two biggest problems they noticed. |
| 7 | Light review of your mistake list and short answers only. Sleep early. |
How to practise talking, not just solving
Interviewers score communication explicitly. Practise these habits on every problem, even when practising alone:
-
Restate the problem and ask about input size, edge cases and constraints before writing code.
-
Say the brute-force solution first, with its complexity, then improve it. A working simple answer beats an unfinished clever one.
-
Think out loud. Silence for five minutes gives the interviewer nothing to score.
-
Test your own code with a small example and an edge case before saying you’re done.
-
For behavioral answers, use STAR (situation, task, action, result), keep it to about two minutes, and make sure the “action” part is about what you did.
Record yourself at least twice a week. Listening back is uncomfortable and very effective.
The day before and the day of
-
Don’t learn anything new the day before. Review your mistake list and short answers, then stop.
-
Check the setup: for remote interviews, test your camera, microphone, internet and the coding tool the company uses.
-
Keep water, a pen and paper nearby.
-
In the interview, it is fine to say “let me think about that for a moment”. It is better than starting to talk in the wrong direction.
-
If you get stuck, say what you are stuck on. Interviewers often give hints, and taking a hint well is a positive signal.
Common mistakes
-
Only grinding coding problems. Concept and behavioral rounds reject as many candidates as coding rounds.
-
Memorising answers. Learn the idea and practise explaining it in your own words. That survives follow-up questions.
-
Not revisiting old material. Without spaced review, what you learned in week 1 is mostly gone by week 4.
-
No mock interviews. Solving alone and solving while someone watches are different skills. Do at least three mocks.
-
Overstating your résumé. Anything you list is fair game. Be ready to go deep on every line.
Summary
Prepare for all four rounds, not just coding. Use a fixed daily slot with three blocks: coding, concepts and spoken practice. Use curated questions as retrieval practice, answering out loud before you look, and review them on a 1, 3, 7-day schedule. Do mock interviews. Spend the last days reviewing, not learning.
Start with TestLab’s free MCQ practice tests to check your fundamentals quickly, then work through the interview questions for your stack, one topic per day, alongside your coding practice.