Skip to content
Tutorials Center
My learning

Topics

Lesson 75 of 77 ยท Interview Day

Interview Day Checklist and Common Mistakes

A practical checklist for the days before and during a tech interview: preparation, remote setup, whiteboard habits, common mistakes and follow-up emails.

You can know every algorithm and still lose an interview to a dead microphone, a rushed start or a silent ten minutes at the whiteboard. Interview day is partly logistics, and logistics are the easiest part of the process to get right because you control them completely.

This lesson is a working checklist. It covers what to do the week before, the night before and the hour before, how to set up a remote interview, how to behave at a whiteboard or shared editor, the mistakes interviewers see most often, and how to write a short follow-up email. The technology involved (video calls, shared editors) cannot run here, so everything is advice in plain text, plus two small stand-in tools you can run to build your own checklist and rehearse timing.

The timeline

Before the day

One week out Research the company and the role.
Three days out Run a timed mock interview.
Night before Pack, test, sleep.

Cramming new topics the night before helps less than sleep.

1 / 2

One week before

  • Research the company. Know what it sells, who its users are and roughly how it makes money. Read the job post twice and mark the three skills it stresses most.
  • Review the stack. If the post names a framework or database, refresh its basics. The language-specific lessons in this track are good for this.
  • Prepare your stories. Have three to five behavioral stories ready; see behavioral questions and the STAR method.
  • Prepare your questions. Take a list from Questions to Ask Your Interviewer.
  • Do a timed mock. A mock with a friend, or alone with a timer, finds problems that silent practice hides. Your study plan should already include one per week.
  • Confirm the logistics. Ask the recruiter for the format, the length, the names of interviewers, whether you may use your own editor and which language you may use.

The night before

  1. Pack or prepare everything: your resume (printed copies for on-site), a notebook, pens, a charger and your ID if the building needs it.
  2. Plan the route or test the link. For on-site, check travel time with a margin of fifteen minutes. For remote, open the meeting link and read the instructions.
  3. Choose clothes that are comfortable and suit the company. When in doubt, aim slightly above what the team wears.
  4. Review a one-page summary of key ideas instead of learning anything new.
  5. Sleep. Tired candidates make careless mistakes and forget names, which feels worse than not knowing an algorithm.

Remote setup checklist

Remote interviews fail for boring reasons. Test each of these the day before and again an hour ahead.

Item What to check
Internet Wired connection if possible; know where your backup is (phone hotspot)
Camera At eye level, face lit from the front, no bright window behind you
Audio A headset beats a laptop microphone; mute notifications
Screen sharing Close private tabs, chat apps and email; share a single window rather than the whole screen
Editor If you may use your own, set a readable font size and a plain theme; if not, try the interviewer's tool beforehand
Space Quiet room, door closed, water within reach
Paper A blank page and a pen for sketches

If your connection drops, reconnect, then say briefly what happened and where you were. Interviewers expect technical failure sometimes and judge how calmly you handle it.

Whiteboard and shared-editor habits

A coding interview scores how you work as much as the result. These habits show up in feedback forms:

  1. Repeat the problem in your own words and ask about inputs, sizes, edge cases and what to return.
  2. Work an example by hand before writing code. A small example often reveals the algorithm.
  3. State a plan and its complexity, then ask whether you should go ahead. Interviewers often steer you here, which saves time.
  4. Write clean, readable code with sensible names. Think of someone reviewing it later.
  5. Narrate what you are doing and why, as practiced in thinking out loud.
  6. Test your code with your example and one or two edge cases (empty input, one element, duplicates, large values). Trace the values by hand.
  7. Discuss the trade-offs and what you would improve with more time.

On a physical whiteboard, write top to bottom, leave space between lines for later edits, and draw boxes and arrows for data structures. In a shared editor, do not delete your first attempt silently; saying "that approach is too slow because..." is a good signal.

Common mistakes

Mistakes in the coding round

Coding too early Typing before the problem is clear.
Silence The interviewer cannot score thoughts.
No testing Declaring done without a trace.
Giving up Not asking for a hint when stuck.

All four are habits, so all four are fixable.

1 / 2

Two of these deserve more detail:

  • Bluffing. If you do not know something, say so and then reason: "I haven't used that, but I would expect it to work like X because..." Interviewers value honest uncertainty with structured thinking far above a confident wrong answer.
  • Rambling. Use the structure from a framework for answering any question: a short definition, an example, the trade-offs, then stop and let them ask more.

Smaller mistakes that add up: arriving late, checking your phone, interrupting, arguing with the interviewer instead of exploring their hint, and skipping a greeting for the receptionist or the person who walks you in. Everybody you meet may be asked for an opinion.

After the interview: the follow-up message

Send a short email within a day. It is not a magic trick, but it is polite and occasionally reminds a busy recruiter about you. Keep it to four or five sentences:

TEXT
Subject: Thank you - Backend Engineer interview

Hi Maya,

Thank you for the conversation today. I enjoyed learning how the team
handles releases, and the discussion about the billing migration made me
even more interested in the role.

One more thought on the caching question we discussed: I would add a
short expiry time and an explicit invalidation on writes. Happy to sketch
it if that is useful.

Thanks again, and I look forward to the next steps.

Best,
Sam

Rules for follow-ups: personalize each one with a real detail, send them to each interviewer if you have their address (or ask the recruiter to pass your thanks on), avoid pleading, and do not write a second email a day later because you have not heard back. If a deadline was promised and passes, a single polite check-in after a few working days is fine.

Build your own checklist

The next stand-in is a checklist that tracks what you have done and prints what is still open. It is the same idea as paper, only with code.

JS A checklist that shows what is left

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Rehearse your timing

Most coding rounds last 45 minutes. A rough split helps you notice when you are lagging. This stand-in prints a plan for any length and flags a checkpoint when you pass it.

JS Plan the minutes of a coding round

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The percentages are a rule of thumb, not a rule. Interviewers care more that you test and discuss than that you hit each minute.

Check your understanding

Quick check ยท 5 questions

of 5 answered You scored / 5 ยท perfect!

  1. 1. What is the best use of the night before an interview?

    New material rarely sticks overnight. Logistics and rest protect the knowledge you already have.
  2. 2. You get stuck halfway through a coding problem. What is the strongest move?

    Explaining your reasoning and asking for a hint shows collaboration. Interviewers usually give hints and score how you use them.
  3. 3. Which is NOT part of a good remote-interview setup?

    Sharing the whole screen with notifications and personal tabs exposes private information. Share a single window instead.
  4. 4. You do not know what a technical term in a question means. What should you do?

    Honesty plus structured reasoning is rated above a confident wrong answer.
  5. 5. When should a thank-you message go out?

    A short, specific message within a day is polite and timely. Repeated messages come across as pressure.

Summary

  • Interview day is mostly logistics, and logistics are fully under your control.
  • Spread preparation across the week: research, mock interview, stories, questions; the night before is for packing, testing and sleep.
  • For remote interviews test internet, camera, audio, screen sharing and your editor, and keep a backup connection.
  • In the coding round clarify, work an example, state a plan, write clean code, narrate, test and discuss trade-offs.
  • Avoid the common mistakes: coding too early, silence, no testing, bluffing, rambling and bad-mouthing.
  • Send a short, personal follow-up within a day.

Next, test your recall with Rapid-Fire Questions: 100 Short Answers.