A 4-Week Interview Prep Plan for Senior Engineers

You have a full-time job, perhaps a family, and a recruiter who wants to book a loop "in the next few weeks". The interview prep plans you find online assume a student's calendar: three hundred problems, four hours a day, three months. A senior engineer does not have that time and does not need most of it. You need a four-week interview prep plan that fits around work and spends its hours where senior loops are decided.
Those places are not where most people put the effort. Senior candidates over-invest in coding problems, because progress there is easy to count, and under-invest in stories and design, which is where level is set. This plan reverses the order: stories first, design second, timed coding third, full rehearsal last.
Who this plan is for and the time it assumes
The plan is written for an engineer with roughly six or more years of experience, employed, aiming at senior roles at companies that run a structured loop: one or two coding rounds, a system design round and a behavioural round. Staff candidates can use it with the changes noted near the end.
It assumes eight to ten hours a week: about an hour on four weekday evenings or early mornings, and four to five hours across the weekend. Less than six hours a week and four weeks will not be enough; use the eight-week version below. More than twelve tends to come out of sleep, and tired candidates interview badly.
Before week 1, do three things, which take one evening:
- Ask each recruiter for the list of rounds, their length, the language options, whether AI tools are allowed in coding rounds and whether any round is in person. Formats have shifted in the past two years, as the guides to AI in coding interviews and in-person interviews describe.
- Put the sessions in your calendar as meetings. Prep that waits for a free evening does not happen.
- Schedule your interviews in the right order: a company you care about less in week 4 or 5, the one you want most after it. If a recruiter pushes for an earlier date, "I can do the week of the 14th" is a complete answer.
The four weeks at a glance
| Week | Focus | Weekday sessions (4 x 1h) | Weekend (4 to 5h) | Done when |
|---|---|---|---|---|
| 1 | Stories and baseline | Write notes for eight stories; opening answer | One cold coding problem, one cold design; tell stories aloud | Eight stories told aloud once; you know your weakest area |
| 2 | System design | One design prompt per session, timed | Two full 45-minute designs; one with a partner | You open every prompt the same way without notes |
| 3 | Coding under time | Two timed problems per session, aloud | A 90-minute mixed set; review error log | Medium problems done in 25 minutes while talking |
| 4 | Full mocks, logistics | Light drills; company research; questions to ask | One full mock loop; setup check; rest | One complete mock per round type, feedback applied |
Week 1: stories and a baseline
Stories come first for two reasons. They take calendar time to mature, since a story told once on Tuesday is better on Saturday without any further work. And they pay off in every round: the same eight stories feed the behavioural round, the recruiter screen and the first five minutes of every other interview.
Weekdays. List the projects of your last four or five years and pick eight situations that between them cover: a hard technical decision, a conflict with a peer, a disagreement with a manager, a failure that was yours, a project with no clear requirements, influencing another team, helping someone grow, and a result you are proud of with a number attached. For each, write six lines of notes, not a script: situation, your role, the decision, what you did, the result, what you would change. The method is set out in the guide to building your story bank, and the STAR method gives the two-minute shape. Use the last weekday session for your opening answer to "tell me about yourself", which gets its own guide: answers for software engineers.
Weekend. Take a baseline, cold, before any revision. One medium coding problem with a 30-minute timer, talking aloud. One design prompt ("design a notification service") with 40 minutes and a blank page. Both will go worse than you expect. Write down what specifically went wrong: froze on the approach, ran out of time, forgot to ask about scale, could not estimate storage. That list decides the emphasis of weeks 2 and 3. Then tell each of the eight stories aloud once, timed. Most will run to four minutes; note which ones.
By Sunday you should have eight stories you have spoken once and an honest note of your weakest area.
Week 2: system design
Design is the round where experience helps most and where senior candidates still fail, usually through lack of structure and rarely through lack of knowledge. You know how to build these systems over six months with a team. The round asks for it in 45 minutes, alone, aloud.
Weekdays. One prompt per session. Spend the first two sessions only on openings: for each of four or five prompts, do the first ten minutes (who uses it, what it must do, how much traffic and data, what matters most) and stop. The opening is the part that most reliably goes wrong and the easiest to make automatic. In the other two sessions do complete designs, timed, and afterwards compare your answer with a written one. Good prompt types to cover over the week: a feed or timeline, a messaging system, a rate limiter or other infrastructure component, something with payments or inventory where correctness matters, and one system from your own domain. The guide to system design interview questions by level lists prompts and shows what a senior answer adds to a mid-level one.
Weekend. Two full 45-minute designs. Do at least one with another person asking questions, because the interruptions are the round: "what happens if that queue backs up?", "why not a relational database?". Alone, you only practise the half of the round you control. Afterwards fill the gaps the week exposed: if you could not explain how you would partition the data or what consistency the users need, spend an hour on that topic only.
Keep the stories alive with ten minutes at the end of two sessions: two stories each time, aloud, aiming for two minutes.
Week 3: coding under time
Senior engineers rarely fail coding rounds for lack of algorithms. They fail on time and on silence: twenty minutes into a problem they could solve in forty, saying nothing. So the week is about speed and narration; coverage matters less.
Weekdays. Two problems per session at 25 minutes each, medium difficulty, in the language you will interview in, in a plain editor without autocomplete unless you know the real round allows more. Talk from the first second: restate the problem, give an example, say the brute-force approach and its cost, then the better one, then code. When the timer ends, stop, read a solution, and write one line in an error log: "missed that the input could be empty", "reached for a heap too late". Pick topics by frequency and by your baseline: arrays and strings with hash maps, two pointers and sliding windows, trees and graphs with breadth-first and depth-first search, intervals, heaps, binary search. Leave dynamic programming to the end unless a target company is known for it. Around sixteen to twenty problems over the week is plenty if every one is timed and reviewed.
Weekend. One 90-minute session that imitates a real round twice over: two problems back to back, 45 minutes each including discussion of tests and complexity. Then read the week's error log. The same three or four mistakes will account for most lines, and those are the ones to fix.
One design prompt and four stories on Sunday keep the earlier weeks from fading. If a target company runs a practical or AI-assisted coding round, replace two weekday sessions with that format.
Week 4: full mocks and logistics
The last week is rehearsal and recovery. Learning new material this late costs more in confidence than it returns in knowledge.
Mocks. Do one full mock for each round type, at real length, with a person: a coding round, a design round and a behavioural round. Spread them over the week with a day between, so that you can apply the feedback from each. This is the point where a peer who is kind to you stops being enough. You need someone who will hold the timer, interrupt and tell you afterwards what they would have written in the feedback form. An ex-colleague who interviews regularly can do it; so can a paid session with one of the mock interview coaches, which has the advantage that the person across the call has no friendship to protect. The guide to mock interviews explains how to brief the interviewer and what to ask for afterwards.
Company work. One session per company: read the engineering blog and the job description again, adjust the closing of your opening answer, pick the two stories that fit their stated values and prepare five questions for the interviewers.
Logistics. Test the camera, microphone and the coding tool the company uses. Decide where you will sit. If a round is in an office, plan the journey. Block the calendar for an hour before each interview.
Rest. Nothing new in the last two days. A short warm-up problem on the morning of a coding round is fine, and so is reading your story notes once.
Adapting the plan to two weeks or eight
Two weeks. Keep the order and halve everything except the mocks. Days 1 to 3: six stories and the baseline. Days 4 to 7: design openings daily and two full designs. Days 8 to 11: timed coding, two problems a day. Days 12 to 14: one mock per round type, logistics, rest. Cut topic coverage, not rehearsal. If you can only do two things, do the stories and one design mock, since those two rounds carry most of the evidence for level.
Eight weeks. Do not stretch each week to two. Run the four-week plan at five to six hours a week over the first six weeks, giving design and coding two weeks each at the lighter load, and keep the final two weeks as mocks and interviews with lower-priority companies. Longer plans fail through drift, so set a checkpoint every second Sunday: re-run the baseline and compare.
Returning after years away, or after a layoff. Add a week zero for materials and direction before week 1, and expect the coding baseline to be lower than you would like. The guide to interviewing after a layoff covers that first fortnight and the order of applications.
Aiming at staff. Shift two coding sessions in week 3 to stories and design, prepare stories about cross-team decisions, and read the bank of staff engineer behavioral interview questions in week 1 so that you choose stories at the right scope.
The free practice round and a paid mock
They do different jobs, and the plan uses both.
The free practice round is for repetition. On techinterview.coach the practice interview is a voice interview with an AI interviewer on the round you choose (behavioural, system design, coding talk-through or salary negotiation), optionally based on a job ad you paste in, followed by a written recap of what worked and what to drill. It is free; sign in to start. Its place in the plan is the weekday sessions of weeks 1 to 3: saying stories aloud to something that asks a follow-up, and talking through a design opening at eleven at night when no person is available.
A paid mock is for judgement. A person who has run real loops can tell you whether an answer would pass at your target level, and that depends on calibration, which only comes from having made hiring decisions. Its place is the end of week 2 for design, when there is still time to act on what you hear, and week 4 for the full rehearsal. One early and one late is a sensible minimum; a mock taken the night before the real loop is too late to change anything.
Where coaching fits
Mock interviews are among the most widely offered sessions on techinterview.coach: 34 of the 40 coaches offer one as of November 2026, and 36 offer a shorter intro call if you want to check the fit first. The mock interview page lists them with their backgrounds, so you can choose a coach who has interviewed for the kind of role and round you are preparing, and book the week 2 and week 4 slots of this plan in advance. Each coach sets their own price.
Related guides
- Mock interviews: how to get useful feedback from the week 4 rehearsals.
- System design interview questions by level: prompts for week 2 and what a senior answer includes.
- STAR method: the shape for the eight stories of week 1.
- Tell me about yourself: the opening answer, with worked examples.
- Interviewing after a layoff: the wider plan if you are searching without a job.
- Staff engineer behavioral interview questions: 35 questions by signal if you are aiming a level up.