How to practise for a job interview on your own

Last updated · By LogicWiz Team

Short answer: Pick 10 to 15 questions you are likely to be asked, answer each one out loud while recording yourself, then play it back and check it against a short checklist (did you answer the question, give one specific example, and stop within about two minutes). Fix one thing, answer again, and once your answers are steady, practise with an AI mock interviewer or a friend so you get follow-up questions you did not prepare for.

Most people prepare for interviews by reading answers. That helps you know what to say, but it does not help you say it, and in an interview you are judged on what comes out of your mouth under a little pressure. Practising alone works if you make yourself speak, listen back and repeat. Here is a method that needs nothing more than a phone.

Step 1: choose the questions you will actually be asked

Build a list of 10 to 15 questions from three places:

  1. The questions every interviewer asks. "Tell me about yourself", "why this company", "strengths and weaknesses", "tell me about a challenge". The HR interview questions for freshers guide lists the common ones with sample answers.
  2. The job description. Every skill it names is a likely question. If it says "SQL", expect "write a query that..." or "what is a join?". If you paste the job description into the free JD test on LogicWiz Exams, you also get a short screening test on those skills.
  3. Your own resume. Anything on it is fair game. For each project, prepare: what problem it solved, what you built, one decision you made and why, and what went wrong.

Write the list down. Practising the same list several times is what makes answers steady.

Step 2: write bullet points, not scripts

For each question, write three to five bullet points, not a paragraph. A memorised script sounds memorised and falls apart when the interviewer interrupts. Bullet points keep the structure and let you speak naturally.

For behavioural questions ("tell me about a time..."), use the STAR structure: Situation, Task, Action, Result, with most of the time on Action. STAR method examples for software engineers has worked examples.

Step 3: answer out loud and record it

Put your phone on the table, start a voice or video recording, read the question aloud and answer it as if someone were sitting opposite you. Do not stop to restart. If you get stuck, recover the way you would in a real interview ("let me think about that for a second").

Video is better than audio if you can bear it, because it shows eye contact, posture and fidgeting. Audio alone still shows most of what matters.

Step 4: play it back and check it against a checklist

Listen to each answer once, with this checklist:

  • Did I answer the question that was asked? A common miss is answering "why this company" with reasons you want any job.
  • Did I give one specific example? "I am a good team player" is a claim; "in our final-year project I split the work and ran a weekly check-in" is evidence.
  • How long was it? For most questions, aim for about one to two minutes. If you are past three, cut.
  • Filler words. Count the "basically", "like" and "actually". You do not need zero; you need fewer.
  • The ending. Did you finish cleanly, or trail off? End with one sentence that links back to the job.

Pick the single biggest problem and fix only that on the next attempt. Fixing one thing at a time is faster than trying to fix everything.

Step 5: repeat until it is steady, then stop

Answer the same question two or three times in a session. When an answer is clear and the right length twice in a row, move on. Over-practising one answer makes it sound rehearsed.

A realistic schedule is three or four questions a day for a week, then a full run through the list on the last two days.

Step 6: practise follow-up questions

Recording yourself has one gap: nobody asks "why?" or "what would you do differently?". Real interviewers do, and follow-ups are where unprepared answers break. Two ways to fill the gap:

  • A friend or classmate. Give them your list and ask them to follow every answer with one "why" or "give me an example". Swap roles afterwards; asking questions teaches you what a good answer sounds like.
  • An AI mock interviewer. It asks a question, listens to your answer and asks a follow-up based on what you said, as many times as you want and at any hour.

How to use an AI mock interviewer well

An AI interviewer is a practice partner, not a judge of whether you will get the job. Used well, it gives you unlimited follow-ups and consistent feedback. To get the most from it:

  1. Set it up for the real job. Choose the role or paste the job description, so the questions match what you will face.
  2. Answer the way you would in the interview. Use the spoken mode if your interview is spoken. Typing lets you edit, which you cannot do in a real interview.
  3. Read the feedback for patterns, not scores. If three reports say your answers lack examples, that is the thing to fix.
  4. Check anything technical it tells you. AI feedback can be wrong. If it says your answer about a database index was incorrect, look it up before you change it.
  5. Ask about privacy first. Find out whether your recordings or transcripts are stored and who can see them. How to prepare for an AI interview lists the questions worth asking.

On LogicWiz Interviews, Aria is the AI interviewer. The free Spark plan includes 1 typed and 1 spoken mock interview a week with no card. Aria asks and adapts follow-up questions, every session ends with a scored report, and practice is private and never shared with an employer. There is also a spot-the-mistake mode, where Aria gives a confident answer with one planted error and you find it, which is good practice for technical rounds. For other free options, see free AI mock interview platforms compared.

For technical interviews: practise thinking aloud

In a coding or technical round, interviewers listen to how you think as much as whether you reach the answer. Practise solving a problem while saying each step out loud: restate the problem, give a simple approach first, then improve it, and test it on a small example. The free DSA problems on LogicWiz let you run your code in the browser while you practise explaining it. For the newer round where you review an AI-written answer, see how to practise spotting a wrong line in an AI answer.

The day before

  • Run through your full list once, out loud, and then stop.
  • Prepare two questions to ask the interviewer, about the work or the team.
  • For an online interview, test your camera, microphone and internet, and sit somewhere quiet with light in front of you.

Frequently asked questions

Can I really prepare for an interview by myself?

Yes, for most of it. Answering out loud, recording and reviewing yourself fixes structure, length, filler words and vague answers. What practising alone cannot give you is follow-up questions, so add a friend or an AI mock interviewer once your answers are steady.

How long should an interview answer be?

For most questions, aim for about one to two minutes. "Tell me about yourself" can be slightly longer. If an answer goes past three minutes, it usually has too much background and not enough of what you did.

Should I memorise my interview answers?

Memorise the structure, not the words. Keep three to five bullet points per question. Word-for-word scripts sound rehearsed and break when the interviewer interrupts.

Are AI mock interviews useful?

They are useful for practising follow-up questions and getting consistent feedback whenever you want. They do not predict whether you will get a job, and their technical feedback can be wrong, so check anything that surprises you.

Is there a free AI mock interview for freshers?

Yes. LogicWiz Interviews gives 1 typed and 1 spoken AI mock interview a week on the free Spark plan, with no card. Several other tools also have free tiers, though some offer only one trial session.

How many days before the interview should I start practising?

A week of daily practice is enough for most freshers to make their answers clear and steady. Start earlier if you have never spoken about your projects out loud.