How to prepare for an interview the night before

Your interview is tomorrow at eleven. You open a list of "200 questions for middle developers", get to number twenty, and realize you won't even finish reading it tonight.

And you don't have to. You can't learn a new technology in one evening anyway. What you can do is the part many people skip: figure out where you're going, prepare what to say about yourself, and say it all out loud. In the interview, that shows far more than one more article you've read.

Below is a three-hour plan. If you have less time, there's a short version at the end.

20 minutes: where you're going and who you'll meet

Open the invitation and your thread with the recruiter. Check how long the meeting is, who will be there, and what the stage is called. A conversation with your future manager, a live coding round, and a System Design interview each need different preparation.

If the format isn't clear, message the recruiter right now. That's completely normal:

Could you tell me what tomorrow's stage will look like: questions about the stack, a discussion of my experience, or a coding task? And who will be on the call?

Then look through real interview questions that candidates got at different companies. You can filter them by grade and interview type. Knowing in advance what people usually get asked makes you a lot less nervous.

And spend ten minutes on the company's product: visit the website, open the app. "Why do you want to work here?" comes up almost everywhere, and "interesting tasks" sounds weak. "I use your app, and I'm curious how the recommendations work" sounds much more genuine.

30 minutes: your intro and two stories

The first question in almost any interview is "Tell me about yourself". Prepare an answer of about two minutes: what you do, what you did yourself, and why you're looking at this role. We cover how to build it in “Tell me about yourself”: examples for developers.

Then think of two stories from work: one you're proud of, and one where something went wrong and you had to find a way out. For each, answer three things for yourself: what happened, what you personally did, and how it ended. You'll need the second story more often than you think: questions about a difficult situation or your own mistake come up all the time.

If you remember the numbers, use them. If you don't, "it got noticeably faster" is better than making up percentages on the spot.

35 minutes: run through common questions out loud

It's too late to learn new things, but warming up helps. Take six to eight of the most common questions for your stack from the question bank, for example the Python, Go, Java, or frontend sections, and answer them out loud without peeking.

Don't forget questions that aren't about code. Even in the Python section of our bank, the third most viewed question is: "Have you had situations in your previous work where you proposed or implemented improvements in team processes?" People also often get asked why they're leaving their current job, how they handle disagreements on the team, and what salary they expect. Better to think through your answers tonight than tomorrow with the interviewer watching.

For salary, prepare one sentence with a specific number or range. "Whatever you can offer" usually works against you.

10 minutes: break

Step away from the screen. Don't watch interview videos during the break: your brain needs a rest, not more input.

45 minutes: rehearsal

This is the most useful part of the evening. Ask a friend to play the interviewer or do a mock interview. In voice mode, the AI interviewer asks questions out loud and you answer out loud, just like on a real call.

Saying it out loud really matters. In your head, the answer always sounds smooth. Out loud, it suddenly turns out your intro takes six minutes, and when asked "why are you leaving?" you start making excuses.

If you have live coding tomorrow, solve one easy task and talk through everything you do. What to say along the way is covered in Live coding interview: what to say while you code. For System Design, the mock interview has a separate mode with a whiteboard.

After the rehearsal, pick the two moments that went worst and repeat only those.

20 minutes: questions for the company

Near the end, they almost always ask: "Do you have any questions for us?" Saying "No, everything's clear" sounds like you don't care. Write down three or four questions, for example:

• What will the team be working on over the next six months?
• What would my tasks be in the first month?
• How does code review work, and who makes technical decisions?
• Why did this position open up?

The answers will also help you decide whether you actually want to work there.

20 minutes: tech check and workspace

• Double-check the meeting time and time zone.
• Open the call link, test your camera, microphone, and headphones.
• If there's a coding task, set up your editor and turn off notifications.
• Put a glass of water nearby.
• If you use Sobes Copilot, launch it in advance, pick the context for this role, and use the compatibility check to make sure it isn't visible during screen sharing.

If you only have an hour

15 minutes on the format, the company, and real interview questions, 15 on your intro and one story, 20 on rehearsing out loud, 10 on questions for the company and the tech check.

In the morning

Don't learn anything new. Tell your intro out loud once to warm up your voice. Eat something. Join the call five minutes early, not at the last second.

And tonight, once all of this is done, go to bed. A well-rested person thinks better in an interview than someone who was reading about design patterns until 2 a.m.