You've never done a technical interview before. You have one in 7 days. You're freaking out.

Take a breath. This is doable. Here's the exact day-by-day plan that gets you walking into that interview with realistic confidence - not fake hype, but actual readiness.

What this guide assumes

You can already write code. You've built things, even if they're small. You know your way around at least one programming language. You've worked with Git, used a debugger, written some tests.

What you're missing is interview-specific preparation: solving algorithm problems under pressure, talking through your thinking out loud, handling questions you don't immediately know how to solve.

This guide turns "competent programmer" into "passable interview candidate" in 7 days of focused work.

The five things interviews actually test

Before the daily plan, understand what you're being evaluated on. Most candidates think interviews test "can you solve LeetCode hard problems." That's wrong.

Interviews test:

  1. Can you communicate your thinking - even when wrong
  2. Can you ask good clarifying questions - not jump to solutions
  3. Can you write working code - even if not optimal
  4. Can you handle being stuck - without panicking
  5. Are you pleasant to work with - collaborative, not defensive

Notice "be a coding genius" isn't on the list. Most companies hire candidates who solve problems methodically and communicate well over candidates who speed-solve in silence.

Day 1: Foundation and self-assessment

Morning (2 hours): Watch one full mock interview from start to finish. Interviewing.io has free recordings. Find one for a role similar to yours. Watch how the interviewer asks questions, how the candidate responds, what gets asked when they're stuck.

Don't take notes. Just watch. Notice the rhythm of the conversation.

Afternoon (3 hours): Solve 3 LeetCode easy problems. Use the language you're most comfortable with. Don't optimize. Just get them working.

For each problem, talk out loud as you solve it. Even alone in your room. The skill of narrating your thought process is the highest-value thing you'll practice this week.

Evening: Write down the topics that scared you most when watching the mock interview. Recursion? Trees? System design? These are your priorities for the rest of the week.

Day 2: Algorithm patterns (the only ones that matter)

You don't need to memorize 500 LeetCode problems. You need to recognize 8 patterns. They cover 80% of all interview problems.

The 8 patterns:

  1. Two pointers - sorted arrays, palindromes, target sums
  2. Sliding window - substrings, subarrays with conditions
  3. Hash map for lookups - "have I seen this before" problems
  4. BFS / DFS on trees and graphs - traversal, path finding
  5. Recursion + memoization - overlapping subproblems
  6. Binary search - sorted arrays, "find the value where X is true"
  7. Heap / priority queue - top K problems
  8. Dynamic programming - optimization problems with subproblems

Today's task: Pick the 4 patterns you're most comfortable with. Solve 1 LeetCode easy and 1 medium for each. That's 8 problems total. Don't move on if you're stuck - read the solution, understand it deeply, then re-solve from scratch tomorrow without looking.

Use NeetCode 150 as your problem source. It's curated specifically around these patterns.

Day 3: The other 4 patterns

Same as yesterday - 1 easy + 1 medium for each of the remaining 4 patterns.

By end of today you should have solved 16 problems across all 8 patterns. You'll be slow. Some will frustrate you. That's normal. The goal isn't speed yet - it's recognition. When you see a new problem, you should be able to say "this looks like a sliding window problem" within 30 seconds.

Evening: Re-solve the 8 problems from yesterday without looking at solutions. The ones you struggle with are your weak patterns. Mark them.

Day 4: Communication practice

Today is not about solving more problems. It's about solving them out loud while explaining your thinking.

The exercise: Pick 5 medium problems you've never seen. For each one:

  1. Read the problem out loud.
  2. Restate it in your own words.
  3. Ask "clarifying questions" out loud (even though you're alone).
  4. Talk through your initial approach before writing any code.
  5. Code it while continuing to narrate.
  6. When you finish, walk through your code explaining each line.

Record yourself doing this. Yes, really. Watch the recording.

You'll notice things you wouldn't otherwise: long silences, unclear explanations, jumping to code without thinking, missing edge cases. This is the skill that separates passing candidates from failing ones.

Day 5: Behavioral preparation

Half your interview will be behavioral questions. Most candidates wing this. Don't.

Prepare a specific story for each of these 8 questions:

  1. Tell me about yourself.
  2. Why do you want this role / company?
  3. Tell me about a challenging project.
  4. Tell me about a time you disagreed with a coworker.
  5. Tell me about a mistake you made.
  6. Tell me about a time you had to learn something quickly.
  7. What's a strength of yours? A weakness?
  8. Why are you leaving your current role / Why this company?

Use the STAR format (Situation, Task, Action, Result) but make it sound natural. Practice each story out loud. Time yourself - 90 seconds to 2 minutes per story is the sweet spot.

For more on making behavioral answers sound human, read this post.

Day 6: Mock interview

Find someone to do a mock interview with. Options:

  1. Interviewing.io - free practice rounds with engineers from real companies
  2. Pramp - peer-to-peer, free
  3. A friend who interviews - even better, ask them to be tough
  4. Yourself + AI - open ChatGPT, ask it to play interviewer, do a full 45-minute round

Don't skip this step because it's uncomfortable. The discomfort is the point. The first time you do a mock, your brain will lock up and you'll forget everything you practiced. That's what you want - better to lock up in a mock than in the real thing.

Get feedback. Ask specifically: "what did I do that hurt my chances? what should I do more of?"

Day 7: Interview day prep

Today is for logistics and confidence, not new learning.

Morning:

Afternoon:

Evening:

The day of the interview

Morning:

During the interview:

What if you're using AI assistance during the interview?

If you've decided to use a tool like Acemode for your first interview, the prep above still applies - maybe more so. Here's why:

AI tools work best when you bring real understanding to them. If you can't talk through the AI's answer, you'll get caught. The week of preparation isn't wasted because you have AI - it's the foundation that lets the AI help you instead of replacing you.

Specifically:

AI is a force multiplier. Multiplying zero is zero. Make sure you have something to multiply.

What to do if you bomb it

You might bomb the interview. First-time candidates often do. This is okay.

Most people get their first job offer after their 3rd-5th interview, not their first. The first one is essentially a real-world mock that you happened to take the consequences for.

If you bomb:

  1. Take 24 hours to feel bad. It's allowed.
  2. Write down everything you remember being asked.
  3. Review what specifically tripped you up.
  4. Add those topics to your prep.
  5. Apply to the next 5 companies.

Interview skill is built through interview reps. The first 1-3 are tuition. The 4th and beyond is when you start landing offers.

The honest expectations check

One week of prep won't make you elite. You won't crush a Google interview after 7 days of LeetCode. That's fine - most companies aren't Google.

What 7 days of focused prep WILL do:

Calibrate expectations. Aim for "I tried, I learned a lot, regardless of outcome I'll come out better." That mindset converts dramatically more often than "I must get this offer."

Good luck. You're more prepared than you feel.