This plan is for freshers, campus placement candidates, career changers and working professionals preparing for an HR, technical or mixed interview. Each day takes 40 to 60 minutes. If your interview includes an assessment, coding task or group discussion, replace the relevant practice block with the format you will actually face.
You can do the exercises with your phone’s voice recorder, a colleague or an online mock interview. Walkin24’s interview practice includes self-introduction, HR, behavioural and technical categories, so you can select the closest category as the week progresses.
Your 7-day interview preparation timetable
| Day | Focus | Time | What you should finish with |
|---|---|---|---|
| 1 | Understand the role and set a baseline | 50 min | Requirements map and first recorded answer |
| 2 | Introduction and resume questions | 50 min | A concise introduction and 3 project explanations |
| 3 | Common HR questions | 55 min | Answers about motivation, strengths and difficult topics |
| 4 | Behavioural questions using real examples | 55 min | Four STAR stories and follow-up prompts |
| 5 | Role-specific knowledge and decisions | 60 min | Three explained answers and a gap list |
| 6 | Online mock interview and feedback | 50 min | One completed rehearsal and a correction log |
| 7 | Final rehearsal and interview-day checks | 40 min | A final run, two questions for the interviewer and a setup check |
Your 7-day interview preparation route
Six hours of focused work across the week
- 1Day 1 · Role + baseline50 min
- 2Day 2 · Intro + resume50 min
- 3Day 3 · HR questions55 min
- 4Day 4 · STAR examples55 min
- 5Day 5 · Role-specific tasks60 min
- 6Day 6 · Mock + review50 min
- 7Day 7 · Final rehearsal40 min
Save one useful correction after every session. The aim is clearer answers, not a perfect score.
The schedule totals 360 minutes, or six hours, across the week. This is a suggested practice budget, not a researched minimum. If you have less time, reduce the number of questions, not the time you spend reviewing a weak answer.
Day 1: read the job description like an interviewer
Time: 50 minutes. Spend 15 minutes identifying the work the role actually involves, 15 minutes matching those requirements to your experience and 20 minutes recording a first attempt at “Tell me about yourself.”
Take a job description and make three columns: requirement, evidence and questions the interviewer could ask. A customer support vacancy that mentions handling escalations could lead to “Tell me about a difficult customer.” A software vacancy that lists APIs could lead to “Describe an API you built or tested.”
| Job requirement | Your evidence | Likely interview question |
|---|---|---|
| Excel reporting | College sales analysis project | How did you check the accuracy of your report? |
| Working with others | Festival registration team | What did you do when a teammate missed a deadline? |
| Customer communication | Part-time retail work | How did you explain a problem to someone frustrated? |
Use evidence you genuinely have. If the role requires a skill you do not know, write that down as a gap rather than building an answer around invented experience.
Record your first introduction without stopping or re-recording it. You are establishing a baseline. Notice whether you answer the question, whether you give a relevant example, and whether the ending explains why you want this role. You do not need to sound polished on Day 1.
Day 2: prepare your introduction and defend your resume
Time: 50 minutes. Spend 15 minutes preparing an introduction, 20 minutes on three resume details and 15 minutes answering them aloud.
Use a simple progression: what you are doing now, one relevant experience, and why this opening interests you. Freshers can start with a degree and a project. Experienced candidates can start with their current responsibilities and a decision or result from their recent work.
“I am doing a BCom degree and did an Excel project comparing monthly sales for a sample retail data set. I enjoyed going through the inconsistent entries and explaining the report to my group. I like this operations role because it involves keeping accurate records and helping teams make decisions based on them.”
Avoid memorising every word. Practise giving the same information in a shorter way. Your interviewer may interrupt or ask for a particular project before you finish.
Next, choose three lines from your resume. For each, answer: What was the problem? What did I do? How do I know the work was finished? If you wrote “improved efficiency”, be ready to say what you measured. If you cannot support a percentage, explain the actual change without it.
Day 3: practise the HR questions you tend to avoid
Time: 55 minutes. Allow 15 minutes to draft key points, 25 minutes to answer aloud and 15 minutes to review.
Work through “Why this role?”, “Why this employer?”, “What are your strengths?”, “Tell me about a weakness” and one question that makes you uncomfortable. That could be a career gap, low marks, a job switch, a salary discussion or a delayed joining date.
Prepare answers from facts, not slogans. “I work well under pressure” is less useful than a short account of a deadline you handled. Saying “My weakness is that I work too hard” tells the interviewer little about your development.
“I took a break from full-time work for family responsibilities. Those arrangements are now in place, and I’m ready to return to a regular schedule. I have refreshed my spreadsheet skills and would like to apply my earlier operations experience in this role.”
Only use that wording if it is true for you. Do not share private details that are unrelated to the job. If you are currently employed, check the actual notice period in your contract before promising a joining date.
Finish by asking yourself: “Could I answer a follow-up about this?” If you cannot, you may need a more specific example rather than a better sentence.
Day 4: turn four experiences into behavioural answers
Time: 55 minutes. Spend 20 minutes choosing examples, 25 minutes speaking through them and 10 minutes refining one weak story.
Choose a teamwork example, a mistake or setback, a time you learned something, and a situation in which you solved a problem. Use the STAR structure when it helps: Situation, Task, Action, Result. The National Careers Service guide recommends short, conversational examples and preparation for follow-up questions. Here is a fictional college example:
A STAR story in four short steps
Fictional college example
Two versions of our event registration sheet showed different counts.
I was in charge of the final list.
I compared the entries against the original forms and clarified any doubtful records with the volunteers.
One verified list was at the registration desk. For the next event, we decided to edit one shared copy instead of keeping separate copies.
Explain your own action. Give an outcome you can support.
That answer gives a clear action. It also makes a follow-up possible: “How did you decide which records were correct?” Practise answering without claiming work done by other teammates.
A failed attempt can be a strong story. State what went wrong and what you changed. Do not force every story into a dramatic success.
Day 5: practise the work, not only the conversation
Time: 60 minutes. Choose three responsibilities from the vacancy. Spend about 15 minutes on each and use the remaining 15 minutes to review mistakes or look up a concept in a reliable source.
A technical role may need coding, SQL, debugging or architectural reasoning. A sales role may involve objection handling. A finance role may ask how you would reconcile different figures. A designer may need to explain a portfolio decision. Use the task that resembles the actual assessment rather than defaulting to generic HR questions.
For a software engineering role, say your approach before you code. State the input, constraints, possible edge cases and complexity. After writing a solution, test it with at least one ordinary case and one case that could break it.
For an operations role, use a scenario like this: “The weekly report shows fewer orders than last week. What’s your first check?” A good answer reviews the date range and data source, then suggests a possible business reason. It should not claim to know the cause before checking.
Keep a gap log with two columns: “Need to study” and “Need to explain better.” If you do not understand SQL joins, study them. If you understand them but ramble, practise giving a shorter explanation. Those problems need different fixes.
Day 6: take a mock interview online and review the recording
Time: 50 minutes. Set aside 10 minutes to prepare, 15 minutes for a practice round and 25 minutes for review and a second attempt at one answer. If your plan supports only a five-minute interview, use that session and spend the remaining time reviewing and practising on your own.
Select the category closest to your interview. A full practice sequence can include an introduction, two resume follow-ups, one behavioural question and one role-specific question. Do not chase a perfect automated score. Look for feedback that names a problem you can correct.
Walkin24 currently lists three five-minute AI interviews per month on its free plan, with basic feedback. Paid plans list longer sessions and detailed reports. The free allowance is a useful starting point for short rehearsals; check the live pricing page for current conditions.
You can use Walkin24 for interview preparation online and then keep your own correction log. Write the question, what you missed and the specific change you will make. Do not paste confidential employer information into a practice tool.
| Question | What happened? | Change for the next attempt |
|---|---|---|
| Tell me about your project. | I explained the team result but not my work. | Name the feature I owned and how I tested it. |
| Why this company? | I used generic praise. | Mention one verified product or responsibility linked to my interest. |
| How would you deal with a complaint? | I promised a refund too early. | First clarify the facts and approval process. |
Review one weak answer and say it again. Your improvement target is greater clarity or accuracy, not simply a higher number on the screen.
Day 7: rehearse the whole experience, then stop editing
Time: 40 minutes. Use 20 minutes for a final sequence of questions, 10 minutes to prepare questions for the interviewer and 10 minutes for logistics.
Practise moving from your introduction to a resume detail, then to a behavioural or role question. Leave room for the interviewer to interrupt. If you forget a point, recover by explaining what you do know instead of restarting from the beginning.
Prepare two questions you actually want answered, for example, “What would you expect the new hire to achieve in the first three months?” and “What are the main problems this team is working on?” Avoid asking questions the interviewer has already answered.
For an online interview, check the meeting link, microphone, camera (if required), power supply, quiet space and local time. For an on-campus or walk-in interview, check the venue, reporting time, ID and documents requested. The National Careers Service interview guidance recommends reviewing the vacancy, preparing examples and testing the online connection ahead of time.
Do not spend the last evening rewriting your entire introduction. Save your final notes and get enough rest to think clearly during the conversation.
How to measure progress without inventing an interview score
Use a small self-review rather than pretending one number predicts the hiring decision. After each important answer, give 0, 1 or 2 points for each of three checks:
| Check | 0 points | 1 point | 2 points |
|---|---|---|---|
| Relevance | I did not answer the question. | I answered part of it. | I answered the question directly. |
| Evidence | Only a claim or opinion. | An example with missing details. | A specific action I can explain. |
| Clarity | Difficult to follow. | Understandable but long or disordered. | Easy to follow without memorised wording. |
The total is out of six, and it is your rehearsal aid. It is not an ATS score, employer rating or prediction of selection. Compare the first and latest attempt at the same question. A score matters only when you can name the improvement behind it.
If you have only one day instead of seven
Spend 15 minutes reading the job description and marking your strongest evidence. Use 20 minutes to rehearse your introduction, project explanation and reason for applying. Spend another 20 minutes on the two questions you fear most, then take 15 minutes for logistics and questions to ask. Adapt the timing to your available hour or so.
If an online coding test comes first, shift more time to practising the task. If the interview is mainly HR, spend longer on truthful behavioural examples and availability questions. A focused plan that matches your actual round is more effective than seven days of unrelated questions.
Final interview preparation checklist
- I know the role title, interview format and scheduled local time.
- I have read the job description and the employer’s own website.
- My introduction explains my background and relevance to the role.
- I can discuss three specific details from my submitted resume.
- I have four truthful examples for behavioural questions.
- I have reviewed the role’s most important skills or tasks.
- I know my actual notice period, availability and relevant constraints.
- I have spoken answers aloud instead of only reading them.
- I have reviewed at least one recorded or mock answer.
- I have prepared two thoughtful questions for the interviewer.
- My technology, venue and required documents are ready.
Begin with one honest answer today
Open the job description and record a one-minute introduction. Keep that first recording. Six days later, answer the same question and compare whether you explained your experience more clearly.
When you are ready for a practice round, try Walkin24’s interview preparation online. Choose the interview category that fits your next round, review the feedback and improve one answer at a time.
Frequently asked questions
Is seven days enough for interview preparation?
Seven days can help you organise evidence, rehearse answers and find gaps. It may not be enough to learn a new programming language or master a technical topic from scratch. Adjust the plan to the interview format and the skills you already have.
How many questions should I practise every day?
Aim for a few useful questions with follow-ups rather than a long list you cannot explain. Three well-reviewed answers may teach you more than 30 memorised scripts.
Can freshers prepare for interviews online without work experience?
Yes. Use projects, internships, student activities, part-time work or volunteering. Explain the setting clearly and identify your contribution. Never rename coursework as full-time employment.
Should I memorise answers to HR interview questions?
Prepare a few points and examples, then practise explaining them in different words. A memorised paragraph can fail if the interviewer asks a follow-up or changes the wording.
What should I do if AI feedback seems wrong?
Compare it with the question and your actual facts. Check technical claims in a reliable source and ask a knowledgeable person when possible. Automated feedback is practice advice, not an employer’s decision.
Can I do the plan entirely on my phone?
You can read job descriptions, record answers and practise many questions by phone. For a coding test, spreadsheet task or presentation, practise in the appropriate environment too. Check your platform’s device requirements before the real round.
Practise before the real interview
Rehearse these questions with an AI interviewer
Answer out loud, get instant feedback and fix one thing at a time. 3 free interviews every month.
Start a free mock interview