← Blog

A 30-minute interview prep routine

· 4 min read

Your interview starts in half an hour. You have the job description open, a few notes from your research, and the urge to read one more list of questions. Give that time a narrower job: get your own experience clear enough to explain out loud.

This routine is a final warm-up. It does not replace learning the material or practising for the round. Use it to bring what you already know within reach, then give yourself a few quiet minutes before joining.

Minutes 0–5: choose what matters for this role

Read the job description once and pick three responsibilities you could discuss through your own work. For each, write a project or experience beside it. Keep the notes short: the problem, your contribution, and what changed.

If a requirement is new to you, mark it honestly. Prepare to explain the closest relevant experience you have and what you would need to learn. Do not turn a tool you have only read about into one you claim to have used in production.

Minutes 5–15: outline three real stories

Choose a result you are proud of, a difficult decision or disagreement, and something that went wrong. For each story, use four prompts:

Write bullets, not a script. Spend most of the detail on your actions and decisions. If you say the team improved something, explain which part was yours. Use numbers you can stand behind; if you do not have a measured result, describe an observable outcome without inventing a percentage.

These stories are starting points for behavioral interview questions. Listen to the actual question before choosing one. A story about a tight deadline is not automatically a story about resolving a disagreement.

Minutes 15–22: say two answers out loud

Practise a short introduction, then answer one question using a story from your notes. Try to finish each answer in about ninety seconds for this rehearsal. That is a practice constraint, not a rule for every answer in the interview.

Notice where you lose the thread. Did the background take over? Did you skip the decision you made? Did you reach an outcome? Trim one thing and try again. Keep the second attempt conversational instead of memorising every sentence.

For a technical round, use the second answer to explain a familiar solution: state the assumptions, describe your approach, name a trade-off, and say how you would test it. Save an unfamiliar problem for a longer practice session.

Minutes 22–27: check your setup

Open the meeting link and check the time zone. Test your microphone, headphones, and camera in the meeting app. Plug in your laptop, close unrelated windows, and silence notifications. If you expect to share your screen, check what will be visible.

Confirm which notes and tools the interviewer permits. If you plan to use PiriPiri AI, try it in a practice call ahead of time so the controls are familiar. Use AI assistance during the interview only when it is allowed, and get permission before recording or transcribing anyone else. If the rules are unclear, ask before the call.

Minutes 27–30: choose two questions and stop

Write down two things you genuinely want to know about the role. For example: what would a useful first three months look like, and which problem is the team hoping this hire will help solve? Adjust them to what you already learned during the hiring process.

Then stop adding material. Keep your three story outlines nearby if notes are allowed, get some water, and join on time. You can ask for clarification or take a moment to think before answering. You do not need to fill every pause.

After the interview, keep one useful note

Once the call ends, write down a question that caught you off guard and one answer you would change. Pick a specific improvement for your next practice session, such as explaining your contribution more clearly or reviewing a concept you could not explain. That gives your next round of preparation somewhere concrete to start.

Preparing for a technical round? Explore our technical interview guide, or check current PiriPiri AI pricing before trying it in a practice session.

Start free — 3 sessionsMore from the blog