To prepare for an interview in a week, give each day one job and about 60 to 90 minutes: research the company on Day 1, map the job description to your experience on Day 2, build a six-story bank on Days 3 and 4, prepare role-specific questions on Day 5, run a full mock interview on Day 6, and keep Day 7 for logistics and a light review. Spreading the work out lets you practice each answer out loud several times, which is what makes it sound natural on the day.
This is a daily schedule with a deliverable for each day. For a shorter timeline checklist, see how to prepare for an interview; if the interview is tomorrow, use the one-day plan.
How do you prepare for an interview in a week? The 7-day plan
Count back from the interview date: Day 7 is the day before. If you start with fewer than seven days, merge Days 1 and 2 and Days 3 and 4.
| Day | Focus | Time | Deliverable by the end of the day |
|---|---|---|---|
| Day 1 | Company and interviewer research | 60 min | "Why this company" in three sentences; five questions to ask |
| Day 2 | Job description mapping | 60 min | A table of the top 6 requirements, each with your evidence |
| Day 3 | Story bank, part 1 | 90 min | Three STAR stories in bullets, each said out loud once |
| Day 4 | Story bank, part 2 and your opener | 90 min | Six stories total; "tell me about yourself" at 60 to 90 seconds |
| Day 5 | Role-specific questions | 90 min | Answers to 5 to 8 questions typical for your role |
| Day 6 | Full mock interview | 60 to 90 min | One scored round, notes, and your two weakest answers redone |
| Day 7 | Logistics and light review | 45 min | One-page brief, tested setup or route, early night |
Days 1 and 2: research the company and map the job description
Day 1: research with an output in mind
Read the company's own site, recent announcements, the product or service the team works on, and your interviewers' public profiles if you have names. Glassdoor's company interview pages list anonymous, candidate-posted questions and reviews for many employers; check the dates and use them to guess the format, not to memorize answers. End the day with two things on paper: a three-sentence "why this company" answer and five questions to ask, of which you'll use two or three. Our guide to researching a company with AI has prompts and a checking routine.
Day 2: turn the job description into a requirements table
List the six requirements that appear first or most often in the posting. Next to each, write the strongest piece of evidence you have. Here's an example we wrote for a junior data analyst role:
| Requirement in the posting | Your evidence | Story to use |
|---|---|---|
| SQL for reporting | Built weekly sales reports from three tables | Report automation story |
| Dashboards for stakeholders | Created a dashboard the store managers used daily | Dashboard adoption story |
| Communicating findings | Presented a pricing finding to the regional manager | Pricing insight story |
| Attention to detail | Caught a duplicate-row error before a board report | Data error story |
Any requirement without evidence is a gap. Plan an honest answer for it ("I haven't used Tableau at work; I've built two dashboards in Power BI and the concepts carry over") rather than hoping it won't come up. The interview questions from job description tool turns the posting into likely questions you can check against your table.
Days 3 and 4: build a six-story bank
Behavioral questions rotate through a handful of themes, so six well-chosen stories can answer most of them. Aim for one story each on:
- A result you're proud of (accomplishment, going above and beyond)
- A conflict or disagreement (coworker, manager, stakeholder)
- A mistake or failure and what you changed afterward
- Leading or influencing without formal authority
- A tight deadline or competing priorities
- Learning something fast or handling ambiguity
Write each in STAR bullets: one line of situation, one of task, three or four lines of what you did, and one line of result with a number if you have one. Say each story out loud the day you write it and time it; about two minutes is a good target. Use the free STAR story builder for structure, and our story-bank method for behavioral interviews for a deeper version of this step.
On Day 4, also finish your opener. "Tell me about yourself" sets the tone for the whole interview, so draft it in a present, past, future shape and say it until it lands in 60 to 90 seconds.
Day 5: prepare the questions specific to your role
Every role adds its own question set on top of behavioral questions. Spend Day 5 answering five to eight of them out loud.
- Software engineering: explain two projects in depth, review core data structures, and talk through one problem out loud. If your loop includes a dedicated coding round, a week is tight; see the two-week coding plan for what to prioritize.
- Sales and customer-facing roles: prepare a short pitch of the company's product, a hard-customer story, and your numbers (quota, retention, satisfaction scores) if you have them.
- Analyst roles: be ready to walk through a dataset you worked with, the question you answered and how you checked your work.
- Managers: prepare a hiring story, a performance problem you handled, and how you set priorities for a team.
Our list of common interview questions and answers covers the general questions, including salary and "why are you leaving," that can come up in any role.
Day 6: run a full mock interview
Day 6 is a dress rehearsal. Sit where you'll interview, dress the part, and answer questions you haven't seen in that order. Two good options:
- A person: a friend, mentor or someone in your field reads 6 to 8 questions, including at least one follow-up per answer ("what would you do differently?"), and tells you which answer was least clear.
- An AI mock interview: in CoPilot Interview's AI mock interview, the desktop app builds the interview from your résumé and the job description. You choose the level, 3, 5 or 8 questions, and the mix (behavioral, technical, system design, coding). It reads each question aloud, scores your spoken answer out of 10 with what worked, what to fix and a model answer, and gives you a report card at the end. The browser version needs nothing installed.
After the round, redo your two weakest answers once with the fix applied. Don't run five more mock interviews on Day 6; one honest round and two fixes are worth more than repetition while tired. Our guide on how many mock interviews to do before a real interview helps if you're unsure whether you need more rounds.
Day 7: logistics, your one-page brief and rest
Keep the last day light. Write a one-page brief with your ranked requirements, six story headlines, your "why this company" answer and three questions to ask. Then handle the practical details:
- Confirm the time, time zone, format and interviewer names in the invitation.
- For video, join a test call and check your camera, microphone, lighting and internet. For in person, plan the route with extra time.
- Lay out your outfit, résumé copies and a notebook.
- Say your opener and one story out loud once, then stop for the day.
See what to bring to an interview for a full packing list.
What are the most common mistakes in a week of interview prep?
- Front-loading research. Spending four days reading leaves no time to practice. Research gets one day; speaking gets most of the rest.
- Writing scripts instead of bullets. Memorized paragraphs sound recited and break when the question is phrased differently.
- Never practicing follow-ups. Interviewers dig into your stories. Prepare one level deeper: why you chose that approach, what you'd change, what the numbers were.
- Skipping the mock round. The first full run-through always exposes something: an answer that runs four minutes, a story with no result, an opener that starts with your college major.
- Cramming on Day 7. New material the day before adds anxiety, not skill. Review and rest.
Run your Day 6 mock interview free
CoPilot Interview's Mock Interview builds questions from your résumé and the job description, reads them aloud and scores each spoken answer out of 10 with a model answer. The free plan includes 15 minutes a day with no account or credit card.
Try a free AI mock interviewFAQ
Is one week enough to prepare for an interview?
For most behavioral and role interviews, yes. At 60 to 90 minutes a day you can research the company, build six stories, prepare role questions and run a full mock round. For a dedicated coding interview where you need to relearn algorithms, give yourself two weeks or more if you can.
How many hours a day should I prepare for an interview?
About 60 to 90 minutes a day for a week is enough for most interviews. Short daily sessions work better than one long session because you practice each answer several times on different days.
How many stories should I prepare for a behavioral interview?
Six is a practical number: an accomplishment, a conflict, a mistake, leadership or influence, a tight deadline, and learning fast. Each one can be adapted to several questions, so six cover most behavioral rounds.
When should I do a mock interview in my week of prep?
On Day 6, after your stories and role answers exist. A mock round earlier in the week mostly shows that you haven't prepared yet; one the day before leaves no time to fix what it finds.
What should I do the day before the interview?
Keep it light: write a one-page brief, confirm the time and format, test your video setup or plan your route, say your opener and one story out loud once, then stop and get a full night of sleep.
Can I prepare for an interview in a week while working full time?
Yes. The plan is built around 60 to 90 minutes a day, which fits in an evening. If a day gets away from you, merge it with the next one rather than skipping the Day 6 mock interview.