Checklist
Technical interview prep checklist
This is for anyone returning to technical interviews after a gap, or whose skills are fine but whose practice has been scattered. It breaks prep into small loops you can tick off over several days. Plan on roughly 30 to 60 minutes per loop, and more loops if the interview is a few weeks away.
Your ticks are saved only in this browser, on this device. Nothing is sent anywhere.
Why small loops
Cramming everything at once tends to produce familiarity rather than fluency: you recognize an answer when you see it but cannot produce it unprompted. Short loops of review, attempt, explain and review again make the gaps visible while there is still time to fix them. Practicing in the likely format matters because the format changes what is hard. Timed exercises test pace, and talking through trade-offs tests explanation, which many technical interviews weigh as much as the final answer.
The checklist does not tell you which topics your role needs. That comes from the posting and from the recruiter, and from your own honest rating of what is rusty. It also cannot replace role-specific preparation materials. If the role is highly specialized or the stakes are high, consider practice that mirrors the real format, and see the guide to practice options linked below.
Where this comes from
The loop structure follows this site's guide to preparing for a technical interview when you are rusty, and the advice to practice in the real format and to explain your reasoning aloud reflects common guidance from university career centres. The suggested session lengths are rough, not measured.