The 48-Hour Technical Interview Checklist

Your interview is in two days. Maybe you’ve been preparing for weeks and want a final sanity check. Maybe you just got the calendar invite and you’re in controlled-panic mode. Either way, this checklist covers everything you need to do in the next 48 hours.

I’ve done this dance enough times — on both sides of the table — to know what actually moves the needle at this point. It’s not cramming another fifty LeetCode problems. It’s making sure you’re not blindsided by something preventable.

Print this out. Check things off. Walk into that interview knowing you’ve covered your bases.

48 Hours Before: Research & Strategy

Company Research

• Read the job description again. Highlight the three most important requirements.
• Visit the company’s engineering blog. Read the two most recent posts. Note any technologies mentioned.
• Check the company’s tech stack on StackShare, Glassdoor, or their careers page.
• Search for recent news about the company (funding rounds, product launches, acquisitions).
• Look up your interviewer(s) on LinkedIn. Note their role, tenure, and any shared connections or interests.

Interview Format Intel

• Confirm the exact interview format. How many rounds? How long each? (Ask your recruiter if unclear.)
• Identify which rounds are coding, system design, behavioral, or team fit.
• Check Glassdoor and Blind for recent interview experiences at this company.
• Prepare clarifying questions for each interview type.

Your Story

• Prepare your 2-minute self-introduction. Practice it out loud three times.
• Prepare three project stories using the STAR format (Situation, Task, Action, Result). Each story should demonstrate a different strength.
• Prepare your answer to “Why this company?” — and make it specific, not generic.
• Prepare your answer to “Why are you leaving your current role?” — keep it positive and forward-looking.

36 Hours Before: Technical Warm-Up

Coding (if applicable)

• Solve 3-5 medium-difficulty problems in your interview language. Focus on patterns, not new problems:
  • One array/string manipulation problem
  • One tree/graph traversal problem
  • One dynamic programming or greedy problem
  • One problem involving hash maps
• Practice talking through your solution process out loud. Explain what you’re doing and why as you code.
• Review Big-O complexity for common operations (array access, hash lookup, tree traversal, sorting).
• Review the standard library of your interview language: sorting, string methods, collection operations.

System Design (if applicable)

• Review the URDGE framework or your preferred system design approach.
• Practice one full system design question end-to-end in 35 minutes:
  • Spend 5 minutes on requirements and scope
  • Spend 15 minutes on high-level design
  • Spend 10 minutes on deep dives
  • Spend 5 minutes on trade-offs and alternatives
• Review these commonly-tested concepts:
  • Load balancing strategies
  • Caching (CDN, application cache, database cache)
  • Database choices (SQL vs NoSQL, when to use each)
  • Message queues and async processing
  • Consistency vs availability trade-offs (CAP theorem basics)

Behavioral Preparation

• For each of your three STAR stories, rehearse the key numbers and outcomes.
• Prepare an example of a technical disagreement and how you resolved it.
• Prepare an example of a time you failed or made a mistake, and what you learned.
• Prepare an example of working under pressure or tight deadlines.
• Prepare 3-5 thoughtful questions to ask at the end of each round.

24 Hours Before: Logistics & Environment

If Remote/Video Interview

• Test your camera and microphone. Record a 30-second video of yourself and watch it back.
• Test your internet connection. If unreliable, identify a backup location (library, coffee shop, friend’s house).
• Check the video platform (Zoom, Teams, Google Meet). Update the app. Test screen sharing.
• If there’s a coding platform (CoderPad, HackerRank), log in and familiarize yourself with the interface.
• Set up your environment: clean background, good lighting (face a window if possible), camera at eye level.
• Close unnecessary browser tabs and notifications. Turn off Slack/Discord/email popups.
• Have a glass of water within reach.

If On-Site Interview

• Confirm the address and plan your route. Add 30 minutes buffer for unexpected delays.
• Decide your outfit. Lay it out tonight. Match the company’s dress code (when in doubt, business casual).
• Pack: ID, phone charger, notebook, pen, printed copies of your resume, water bottle.
• If whiteboarding: practice writing code on paper or a whiteboard. Your handwriting matters less than your structure.

Mental Preparation

• Set an alarm with plenty of buffer time. Being rushed increases anxiety.
• Plan what you’ll eat beforehand. Light meal, avoid heavy carbs that cause energy crashes.
• Do NOT stay up late cramming. Sleep is more valuable than one more LeetCode problem. Seriously.

Day Of: Pre-Interview Routine

2 Hours Before

• Light review only. Skim your STAR stories and key technical concepts. No new problems.
• Review the company research notes you prepared.
• Review your list of questions to ask the interviewers.

30 Minutes Before

• Stop studying. Close all study materials.
• Do a 5-minute breathing exercise: inhale 4 seconds, hold 4 seconds, exhale 6 seconds.
• Remind yourself: they already liked your resume enough to interview you. You belong in this room.
• Open the video call link or leave for the office.

During the Interview

• Take a breath before answering each question. A 3-second pause looks thoughtful, not unprepared.
• For coding: clarify the problem, discuss your approach, then code. Don’t jump straight into typing.
• For system design: start with requirements. Always. The interviewer is watching your process, not just your answer.
• If you’re stuck: say so. “I’m going to think about this for a moment” is better than silent flailing. Knowing how to handle being stuck is a skill interviewers respect.
• Ask your prepared questions. Good questions demonstrate genuine interest and critical thinking.

Post-Interview

• Send a brief thank-you email within 24 hours. Reference something specific from the conversation.
• Write down every question you were asked while it’s fresh. This helps you prepare for future rounds or other interviews.
• Note what went well and what felt shaky. No judgment — just data for next time.
• If you made a mistake on a coding problem, solve it properly now. The learning compounds.

Emergency Quick Reference

If you blank on a coding problem:

1. Restate the problem in your own words
2. Work through a small example by hand
3. Identify the brute force solution first
4. Optimize from there

If you blank on a system design question:

1. “Let me start by clarifying the requirements”
2. Draw boxes for the major components (client, API, database)
3. Pick one component and go deep
4. Discuss trade-offs of your choices

If you blank on a behavioral question:

1. “That’s a great question. Let me think of the best example…”
2. Pick ANY relevant project, even if it’s not perfect
3. Focus on what YOU did, not the team
4. Always end with the result and what you learned

You’ve got this. The fact that you’re preparing methodically already puts you ahead of most candidates. Go demonstrate what you know.