To prepare for a technical interview, first find out the format (how many rounds, coding, system design, behavioural, take-home), then split your time across the rounds you will actually face, weighted toward the topics that are both likely and weak for you. Practise the way the interview works: out loud, against the clock, without autocomplete. Finish with at least two mock interviews with a real person and a couple of quiet days before the real one.
Three weeks is enough to sharpen what you already know and close a few gaps. It is not enough to learn a new field from scratch, so the plan below is about choosing what to leave out.
Step 1: find out the format
Ask the recruiter. It is a normal question and they usually answer it. You want to know:
- How many rounds, and what each one covers.
- Whether coding happens in a shared editor, on a whiteboard, or as a take-home.
- Which language you can use.
- Whether there is a system design round (common for mid-level and senior roles).
- Who interviews you in each round: engineers, a manager, someone from another team.
Everything else in your plan depends on these answers. A take-home assignment and a 45-minute live coding round need very different practice.
Step 2: turn the job description into a topic list
Copy the job description and mark every technology and responsibility. Then score each topic twice, from 1 to 3: how likely it is to come up, and how weak you are at it. Multiply the two and sort.
Topics with a high score get most of your time. Topics that are likely but strong get a quick review. Topics that are unlikely get nothing, however interesting they are.
Step 3: plan the three weeks
A common shape, adjusted for a backend role:
| Week | Focus | Daily practice |
|---|---|---|
| 1 | Fundamentals and patterns: arrays, strings, hash maps, two pointers, recursion, the stack named in the job description | 2–3 problems by pattern, one concept review |
| 2 | Harder patterns (trees, graphs, sorting and searching), SQL, system design basics if relevant | 2 timed problems, one design or SQL exercise |
| 3 | Mock interviews, behavioural stories, review of weak spots | 1 timed problem, 1 mock or story rehearsal |
For comparison, the Tech Interview Handbook's study plan recommends about three months at around 11 hours a week, with topics ordered by priority and mock interviews starting once you are about 60% through. Three weeks means cutting that down hard, which is why Step 2 matters.
Step 4: practise like the interview, not like homework
- Talk out loud. Interviewers grade your reasoning as much as your answer. Explain the brute-force approach first, then improve it.
- Use a timer. If the round is 45 minutes, solve in 30 to leave time for questions and edge cases.
- Write in a plain editor. No autocomplete, no running the code until you have traced it by hand.
- Answer from memory first. Before looking up a concept, write down what you think it is. Then check. Practice testing is one of the two study methods a large review of the research rated most useful (Dunlosky et al., 2013, via the Association for Psychological Science).
Step 5: prepare behavioural stories
Most technical loops include questions like "Tell me about a time you disagreed with a teammate" or "Describe a project that went wrong". Prepare five or six stories from your real work, each in the STAR shape: situation, task, action, result. One story can answer several questions, so pick ones with a conflict, a mistake, a deadline, a decision you owned and a result you can describe concretely.
Say them out loud until each fits in about two minutes.
Step 6: do mock interviews with a person
Practising alone hides the hardest part: thinking clearly while someone watches. Ask a colleague or friend who interviews engineers, or use a mock interview service such as interviewing.io (one of the platforms the Tech Interview Handbook links to). Two or three mocks in week 3 are worth more than another twenty solo problems.
Step 7: protect the last two days
Review your notes and the problems you got wrong. Don't start new topics. Sleep, check the time zone and the call link, and have your stories and questions for the interviewer written down.
Example: backend developer, three weeks out
The job description asks for Python, PostgreSQL, REST APIs and "experience with distributed systems". The recruiter says there are three rounds: a 45-minute coding round in a shared editor, a system design round, and a behavioural round with the hiring manager.
The scored list puts these at the top:
- Graphs and trees (likely in coding, weak for this candidate).
- SQL joins and indexing (likely, medium).
- System design basics: APIs, caching, queues, database choices (likely, weak).
- Behavioural stories (certain, not yet prepared).
Dynamic programming scores low on likelihood for this loop and gets one review session, not a week.
Where Quri fits, and where it doesn't
Quri can turn this plan into a structured course. You name the subject (for example "Backend interview preparation"), write your situation and deadline, say how familiar you already are and how deep to go, and Quri builds a course of units, lessons and steps around it. Each step ends with a short challenge, lessons and units have quizzes, and you can select anything in a lesson and ask the tutor to explain it differently; the tutor sees the course outline and the lesson you are on. If the recruiter tells you the format later, use "Adjust course" to refocus it, for example on system design.
Build my interview prep course
Quri does not run mock interviews, run or test your code, or time you. Use a coding practice site for timed problems and a person for mocks. Quri is useful for the concept side: understanding what you got wrong and building the knowledge the problems rely on.
Common mistakes
- Grinding random problems. Practise by pattern so each problem teaches you something reusable.
- Practising silently. You will be asked to explain yourself, so rehearse doing it.
- Memorising solutions. Interviewers change one detail and the memorised answer falls apart.
- Skipping system design for a senior role. For senior roles the design round often weighs as much as coding.
- Leaving behavioural prep to the night before. Stories need rehearsal, just like code.
- Learning a new topic the day before. Review instead.
FAQ
How long does it take to prepare for a technical interview?
It depends on your starting point. If you already code daily, two to four weeks of focused practice is common. If you are rusty or changing fields, plan for two to three months.
How many LeetCode problems should I solve?
Fewer than you think, if you practise by pattern and review the ones you got wrong. Solving and understanding a set of well-chosen problems beats skimming hundreds.
Can I prepare for a coding interview in one week?
You can improve, not transform. Spend the week on the format, the three or four most likely topics, your behavioural stories and one mock interview.
What if the interview is in a language I don't use every day?
Ask whether you can use the language you know best; many companies allow it. If not, spend week 1 on that language's syntax for collections, strings and sorting.
Can AI help me prepare for an interview?
Yes, for explaining concepts, generating practice questions and structuring a study plan. It cannot replace a mock interview with a person, and you should check its explanations of anything you are unsure about.