How to prepare for a job interview: a calm, concrete checklist

Good interview prep does one thing: it lets you walk in calm and talk like yourself. Not a memorized pitch, not a panic the night before, just a steady conversation where you can reach for the right example without straining. That comes from a few hours of focused work, spread across the days before, not from talent or nerve. Here is the order I would do it in.

Research the company and the role

Start with the posting you already have. Read it again as the source of truth for what this team is hiring for, then go one layer deeper than the average candidate, which is not very deep at all.

Spend twenty minutes on each of these:

• The company's own pages. What they sell, who buys it, how they describe their own work. The "about" and product pages tell you the words they use, which become the words you use back to them.
• Recent news. A funding round, a launch, a new market. One current detail in your answers signals you did the work without you having to announce it.
• The role in context. Why does this job exist now? A new team, a backlog, a person who left. The posting often hints at it. Knowing the problem you would be hired to solve sharpens every answer you give.

You are not memorizing trivia for a quiz. You are collecting two or three real details you can fold into answers naturally, so the conversation sounds like you already half-belong there.

Map your stories to likely questions

Most interview questions are variations on a few themes: a time you solved a hard problem, handled conflict, led without authority, failed and recovered, or made a call under pressure. You do not need a script for each. You need a small set of real stories you can aim at whatever they ask.

Pick five or six things you actually did and write each as a short STAR note:

• Situation. The context, in one line.
• Task. What you specifically had to do.
• Action. The steps you took, in your own words.
• Result. What came of it, and what you would prove if asked.

Keep these as bullet points, not a paragraph you recite. The goal is to know the shape of each story so well that you can tell it conversationally, adjusting the emphasis to the question. A story about untangling a broken release can answer "tell me about a hard problem" or "tell me about a conflict," depending on which part you lead with.

Do not invent results. If you cannot prove a number, describe the outcome in plain terms. "We shipped two weeks late but caught the data bug before customers did" is honest and memorable. A made-up metric falls apart the moment someone asks how you measured it.

Prepare questions to ask them

The "any questions for us?" moment is not a formality, it is part of the evaluation, and a flat "no, I think you covered everything" reads as low interest. Bring three or four real ones.

Good questions come from your research and show you are picturing the actual job:

• "What does the first ninety days look like for this role?"
• "What is the hardest part of this job that the posting does not mention?"
• "How does the team decide what to work on next?"
• "What would make you glad you hired for this role a year from now?"

Skip anything you could answer with thirty seconds on their site, and save salary and logistics for when there is an offer in motion or they raise it first. The point here is to learn whether you want the job, which also happens to be what makes you look like someone who does.

Sort out the logistics before the day

Nothing rattles a good candidate like a technical scramble two minutes before the call. Remove that risk in advance so your attention is free for the conversation.

For a remote interview:

• Test the actual tools. Open the meeting link, check your camera and mic, and if there is a shared coding or whiteboard tool, log into it once beforehand.
• Fix the basics. A quiet room, a plain background, a light source in front of you rather than behind. Phone on silent, notifications off.
• Keep notes in reach. Your STAR bullets and your questions on a page beside you, glanceable, not a screen you read from.

For an onsite interview, confirm the address, the time, who you are meeting, and how long it will run. Plan to arrive with a buffer. Either way, write down the name of your contact so a delay or a wrong link has a person to reach, not a silent panic.

Run a steady day-of routine

By the morning of, the work is done. The day-of job is to stay regulated, not to cram. Cramming new material in the last hour mostly adds anxiety and crowds out what you already know.

A routine that holds up:

• Skim your STAR bullets and your questions once, early. Do not re-read them ten times.
• Eat something, get outside for a few minutes, and start the setup early enough that a glitch is not a crisis.
• Have a glass of water in reach and a notepad for anything you want to follow up on.
• Treat the first question as a warm-up, not a verdict. A shaky opening line is normal and forgotten by the third answer.

Afterward, jot down what they asked and how you answered while it is fresh. Win or lose, that note makes your next interview easier, and a short thank-you message that references something specific you discussed is a small, honest edge.

Where JobScalr fits

The slow part of prep is turning a posting into something you can practice against. JobScalr is a mobile app that builds a study deck from the actual job posting, the topics and questions this specific role is likely to probe, and then has you practice answering in your own words rather than reading you a script. It does not write your stories for you and it does not invent experience. It just gives the research and question-mapping above a head start, so the hours you spend preparing land where this interview will.