An interview prep plan for your exact role
Name the position and get a checklist in five blocks: what to revise, which problems to work through, which stories to prepare and what to learn about the company. Every item is an action, not «prepare for questions».
How it works
Three steps and a clear to-do list for the evening before.
Name the position
«Python developer», «product analyst», «mobile team lead» — the sharper the wording, the more specific the items.
Get the blocks
Technical knowledge, practical problems, behavioural questions, market and company research, soft skills — each with its own list.
Work through it
Tick things off and see what's left. Items are phrased as actions: revise, work through, prepare an example.
Why this beats «just revise everything»
The hard part of preparing isn't finding material — it's knowing what to grab two days before the call.
Tied to the role
Items name the technologies and tools of your position instead of a generic «algorithms, databases, networking».
Actions, not topics
«Work through PostgreSQL indexes and explain out loud when they don't help» instead of «revise databases».
Behavioural part included
A separate block for stories from your experience — where technically strong candidates most often stumble.
What to learn about the company
Items about the product, the market and the questions worth asking back — an interview runs both ways.
Pairs with practice
Once you're through the checklist, run a mock interview and hear how it sounds out loud under pressure.
A new checklist per job
A different role or level gets its own list — the previous one stays where it was.
A generic question list versus a plan for your role
«100 interview questions» lists work as reference, but they don't answer «what do I do tonight».
| — | Generic list | Checklist for the role |
|---|---|---|
| Scope | Everything anyone asks in tech, from recursion to Kubernetes. | What gets asked at your position and your level. |
| Phrasing | Topics: «algorithms», «databases», «behavioural questions». | Actions: work through, revise, prepare an example, say it out loud. |
| Beyond the technical | The behavioural part is a separate list, when it exists at all. | Stories from experience and questions for them, inside the same plan. |
| Progress | No sense of how much is left or what's already covered. | Items get ticked off: what's done and what's left for tonight. |
Scope
Generic list:Everything anyone asks in tech, from recursion to Kubernetes.
Checklist for the role:What gets asked at your position and your level.
Phrasing
Generic list:Topics: «algorithms», «databases», «behavioural questions».
Checklist for the role:Actions: work through, revise, prepare an example, say it out loud.
Beyond the technical
Generic list:The behavioural part is a separate list, when it exists at all.
Checklist for the role:Stories from experience and questions for them, inside the same plan.
Progress
Generic list:No sense of how much is left or what's already covered.
Checklist for the role:Items get ticked off: what's done and what's left for tonight.
Where preparation fits
The checklist is the middle of the path, not the start.
Skim the questions
A bank of real questions by stack and seniority makes the gaps obvious fast.
Question bankBuild the plan
Five preparation blocks for your exact role. You are here.
Test it out loud
A mock interview shows which of the revised material actually comes out when spoken.
Mock interviewChecklist FAQ
Nothing here? Ping @Jobpath_help.
