How to Prepare for Interviews With a Full-Time Job
Alex Chen
Senior Engineer
Most interview preparation advice is written for people with free evenings and no dependents. If you have a full-time job, the honest constraint is somewhere between forty and sixty minutes a day, four or five days a week, and any plan that ignores that is a plan you will abandon in week two and feel guilty about in week three.
The arithmetic that changes the plan
Say you have six weeks and five hours a week. That is thirty hours total. A problem solved properly, with review, is twenty-five minutes. If you spend all thirty hours solving, you get roughly seventy problems and zero spoken practice, which is a worse allocation than half as many problems and ten mock interviews.
| Allocation of 30 hours | Problems | Mocks | Likely weak spot on the day |
|---|---|---|---|
| All solving | ~70 | 0 | Freezing, narrating, handling follow-ups |
| Half and half | ~35 | ~15 | The occasional unfamiliar pattern |
| All mocks | 0 | ~30 | Technique gaps you keep rediscovering |
The middle row wins for almost everyone, and the reason is that the two activities train different things and neither substitutes for the other. The mistake is not choosing wrongly between them; it is not noticing there was a choice.
A week that survives a real job
| Day | Time | What |
|---|---|---|
| Mon | 45 min | Two problems from one pattern, spoken aloud |
| Tue | 45 min | One full mock interview |
| Wed | 30 min | Read yesterday's transcript, note the two worst moments |
| Thu | 45 min | One full mock, deliberately fixing one of those moments |
| Fri | - | Nothing, on purpose |
| Sat | 90 min | Longer session: system design or behavioural stories |
| Sun | - | Nothing |
Two rest days are in the schedule deliberately, not as an admission of weakness. A plan with seven working days has no slack, so the first bad week at work breaks it entirely and the breakage feels like failure. A plan with two empty days absorbs a late meeting without collapsing.
"Adding manpower to a late software project makes it later."
- Fred Brooks, The Mythical Man-Month (1975)
Brooks's law has an equivalent here. Adding hours to a preparation plan that is already behind mostly produces worse hours. Two focused sessions beat five distracted ones, and the version of you that studies at eleven at night after a hard day is learning very little.
Consistency beats intensity, measurably
The gap is not about willpower. Spoken performance is a motor skill more than a knowledge one, and motor skills consolidate between sessions rather than during them. Four contacts a week with the material produce four consolidations; one long session produces one.
Where the time actually comes from
๐ The commute and the lunch break
Two things need no editor: rehearsing behavioural stories, and explaining a solved problem out loud. Both are the neglected half of preparation and both fit in a walk or a train journey. That is often two extra hours a week found at no cost to your evenings.
The real blocker is not time
Ask someone why they have not done a mock interview and the answer is usually scheduling. Push once and it is more often that booking a slot with a stranger, on a specific evening, while underprepared, is an unpleasant thing to arrange. That is entirely reasonable and it is the actual reason spoken practice gets skipped.
Which is why the practical fix is to make the friction near zero rather than to try harder. A session you can start at nine at night, badly, with nobody watching, is the one that will actually happen four times a week for six weeks. That is the whole trick, and it beats a better plan you do not follow.
