Most candidates either overprepare (grinding LeetCode at 2am the night before) or underprepare (glancing at the company website 20 minutes before the call). The week before an interview has a right rhythm — here's exactly what to do each day.
Day 7: Deep Company Research
Goal: Understand the company, team, and role deeply enough to have a real conversation — not just recite facts.
What to do:
Research the company (45 min)
- Read the "About" page, recent press releases, and earnings reports (if public)
- Find the engineering blog — understand what they're building and how
- Search for recent news: fundraising, acquisitions, product launches, layoffs
- Note 2–3 things that genuinely interest you — you'll use these in "why this company?"
Research the team (20 min)
- Look up your interviewers on LinkedIn
- Note their backgrounds, tenure, and what they've worked on
- Not to prepare targeted answers — just to feel less nervous about who you're talking to
Understand the role (20 min)
- Re-read the job description carefully
- Identify the 3 must-have skills and 2 nice-to-haves
- List the interview topics this role is likely to test
Checklist:
- [ ] Read the engineering blog
- [ ] Know the company's primary product and business model
- [ ] Know 2–3 recent company news items
- [ ] Identified your interviewers on LinkedIn
Day 6: Review Your Resume Stories
Goal: Have 8–10 STAR stories ready that cover multiple interview dimensions.
What to do:
Pull out your resume and walk through every bullet point. For each major achievement, answer:
- What was the situation?
- What specifically did I do?
- What was the measurable outcome?
- What did I learn?
Map your stories to likely question categories:
- Leadership / ownership
- Conflict / disagreement
- Failure / learning
- Technical challenge
- Ambiguity / unclear requirements
- Cross-team collaboration
Write them down — not to memorize word-for-word, but to know the key points. A story you've written down once is twice as retrievable under pressure.
Checklist:
- [ ] 8–10 STAR stories documented
- [ ] Each story mapped to at least one behavioral dimension
- [ ] At least one failure story that shows genuine learning
- [ ] At least one leadership story (even without a title)
Day 5: Practice Hard Questions Out Loud
Goal: Get uncomfortable questions out of your system before the real thing.
What to do:
Practice these out loud — not in your head. Speaking is fundamentally different from thinking.
The hardest questions most candidates avoid:
- "What is your greatest weakness?"
- "Tell me about a time you failed."
- "Why are you leaving your current role?"
- "Where do you see yourself in 5 years?"
- "Why do you want to work here specifically?"
Set a timer. Answer each question as if the interview is happening. Record yourself if that helps — hearing your own answers exposes vague answers much faster than reading them.
Checklist:
- [ ] Practiced 5 hardest behavioral questions out loud
- [ ] Answer to "why this company" is specific (not generic)
- [ ] Answer to "greatest weakness" is genuine with evidence of improvement
Day 4: Do a Full Mock Interview
Goal: Experience real interview pressure before the real interview.
What to do:
Do one complete mock interview — not a practice session, a mock interview. This means:
- Set a timer
- Answer questions as if it's real (no pausing to look things up)
- Stay in character for the entire session
Options:
- CareerLift's AI mock interview for the role and company type
- A peer who'll ask the questions without helping you
- A paid mock interview service if the role is important enough
After the mock, note:
- Which questions you fumbled
- Which answers felt too long or too short
- One thing you'll change
Don't try to fix everything. Fix the one most important thing.
Checklist:
- [ ] Completed one full mock interview
- [ ] Identified top 1–2 things to improve
- [ ] Not doing another 4 hours of practice tonight — rest matters
Day 3: Logistics and Technology
Goal: Remove every logistical variable so interview day has zero surprises.
What to do:
If in-person:
- Map the route and do a test run if possible
- Find parking or transit options + backups
- Know the building entrance, floor, and who to ask for
- Plan to arrive 10–15 minutes early (not 30 — that creates awkward lobby waiting)
- Decide what you're wearing today (not the morning of)
If virtual:
- Test your camera, microphone, and internet connection
- Check the video platform (Zoom, Google Meet, Teams) — download any updates now
- Set up your background — clean wall or professional virtual background
- Charge your laptop and have a charger nearby
- Close unnecessary applications, disable notifications
Prepare what you're bringing:
- 3 printed copies of your resume (in-person)
- A notepad and pen
- A list of 3–5 questions to ask them
Checklist:
- [ ] Route/logistics confirmed
- [ ] Tech tested (camera, mic, platform)
- [ ] Interview outfit decided and ready
- [ ] Questions to ask them prepared
Day 2: Light Review and Sleep Priority
Goal: Stay sharp without burning out.
What to do:
Today is not the day for heavy preparation. Your brain needs consolidation time, not more new information.
Light review (60 min max):
- Re-read your story bank — not to memorize, just to refresh
- Review 3–5 technical concepts most likely to come up
- Re-read the job description one more time
No new material. Don't start learning a new framework, reading a new system design chapter, or cramming LeetCode problems you've never seen. New information the day before creates confusion, not confidence.
Sleep is your competitive advantage: Sleep deprivation reduces working memory, slows reaction time, and increases anxiety. Getting 8 hours tonight is worth more than 2 hours of additional preparation.
Checklist:
- [ ] Light review only — no new material
- [ ] In bed by 10:30pm
- [ ] Alarm set with a 30-minute buffer before you need to leave
Day 1 (Interview Day): The Morning Routine
Goal: Show up calm, prepared, and present.
What to do:
Morning (2 hours before):
- Eat a real breakfast — low blood sugar kills interview performance
- Review your story bank for 15 minutes maximum
- Review your 3 questions to ask them
- Do 5 minutes of light physical activity — even a walk around the block reduces cortisol
30 minutes before:
- For virtual: open the platform, test audio/video, close other tabs
- For in-person: arrive at the building (not the lobby yet) with 10 minutes to spare
- Take 3 slow deep breaths — this actually works physiologically (activates parasympathetic nervous system)
What to remember: You've done the work. The interview is the performance, not the preparation. Your job now is to show up present and conversational — not to be perfect.
Questions to Ask at the End
Always have questions ready. Not asking questions reads as disinterest. Bad questions ("what does the company do?") are worse than no questions.
Strong questions:
- "What does success look like for this role in the first 90 days?"
- "What's the most significant technical challenge the team is working through right now?"
- "How does the team handle disagreements on technical direction?"
- "What do people who do well here have in common?"
- "What would you want your new hire to know that isn't in the job description?"
Do a full mock interview before the real thing. CareerLift's AI mock interview lets you practice with an AI that asks role-specific questions, gives real-time feedback, and delivers a Hire / No Hire verdict — so you know exactly where you stand before it counts.