The interview invitation arrives, your calendar shows two days, and suddenly every article about "30-day interview mastery plans" is useless. Here's the realistic version: how to prepare for an interview when you have 48 hours, structured as a countdown checklist that tells you what to do when — and, just as importantly, when to stop. One caveat before we start: interview formats vary widely by company and level. A recruiter phone screen, a panel with four engineers, and a case-study round need different emphases, so treat this as the universal base layer and adjust once you know the format. (If you don't know the format, asking the recruiter is itself a professional move.)
48 hours out: research that goes beyond the About page
Budget 60–90 minutes. The goal is not to become a company historian; it's to collect four or five specifics you can deploy naturally.
The 15-minute core:
- The company's actual product or service — try it if you can. Sign up for the free tier, walk into the store, read a sample of their work.
- How they make money, in one sentence. (Surprisingly many candidates can't answer this.)
- One recent event: funding, launch, leadership change, expansion. Their press page, LinkedIn posts, or a news search gets you there.
The 30-minute layer:
- Your interviewers, if you have names. Their LinkedIn tells you their tenure, path, and what they post about. You're not stalking; you're learning what they care about.
- The team's context: is this a new role (growth) or a backfill (someone left)? The recruiter will usually tell you if asked.
- Two or three employee reviews on ratings sites — read skeptically, looking for repeated themes rather than individual rants.
What to write down: four bullet points you could mention naturally. "I tried the app and noticed X" is worth more than an hour of memorized history. This research also powers your answer to "why do you want to work here" — the question where lazy research is most obvious.
Re-reading the job posting like an answer key
The posting is the closest thing to a leaked exam. Spend 20 minutes on this:
- Highlight every requirement — skills, experience, traits.
- Rank them. The first three bullets and anything repeated are the real priorities; the bottom of the list is often HR boilerplate.
- Match each priority to your evidence. For each of the top five requirements, note one story or accomplishment that proves you have it. This matrix is your interview strategy — most questions are just those requirements rephrased.
- Flag your gaps. If they want a skill you lack, prepare one honest sentence: acknowledgment plus adjacent evidence plus willingness to learn. Rehearsed gap answers land fine; improvised ones ramble.
24 hours out: your story bank and the answers you must have ready
This is answer day. Budget two hours, ideally in two sessions.
Session one (about 60 minutes): the big five.
- "Tell me about yourself" — write it, say it out loud three times, keep it under 90 seconds.
- "Why this company / this role" — built from yesterday's research.
- "Why are you leaving / why now" — one forward-looking sentence, rehearsed until neutral.
- Your weakness answer — real weakness, active fix, visible progress.
- Your salary range — researched, with exact phrasing ready. Scripts are in our salary expectations guide.
Session two (about 60 minutes): the story bank.
Prepare eight stories in STAR format — a win, a failure, a conflict, a deadline, a persuasion, a fast learning curve, a process improvement, a team moment. Four bullets each, not scripts. These eight cover the vast majority of the most common interview questions you'll actually face.
If you want pressure-testing, AI practice tools can play interviewer and throw follow-ups at your stories — our guide to AI interview prep covers what these tools do well and where they mislead.
Preparing your own questions — the ones that also impress
Prepare five to seven questions, expecting to ask three or four (some will get answered along the way). The best ones do double duty: they get you real information and signal you think like someone already doing the job. A few examples by target:
- For the hiring manager: "What would the first 90 days need to look like for you to consider this hire a success?"
- About the team: "What does the team's workload look like right now — and is this role meant to relieve that?"
- About the role's history: "Is this a new position or a backfill? If a backfill, what's the person who left doing now?"
Write them down and bring them — a notebook reads as prepared, not scripted. We keep a full list, organized by interviewer type and round, in our questions to ask in an interview guide.
Day of: logistics, materials, and the pre-interview routine
Materials:
- Three printed copies of your resume (in-person) or the file open on your desktop (virtual). Make sure it's the exact version you applied with.
- Your notebook with: the four research bullets, your questions, your story bank keywords, and the interviewer names.
- For portfolio-based roles: your work, loaded and tested.
Logistics:
- In-person: route planned, buffer of 20–30 minutes, arrive at the building early but walk in about ten minutes before your slot. Know the parking situation and who to ask for.
- Contact number for the recruiter in your phone, in case something goes sideways.
The pre-interview hour:
- Eat something. Interviews on an empty stomach are measurably worse experiences.
- Review your notebook once — the keywords, not full rehearsals.
- Say your opener out loud one time to warm up your voice.
- Stop reviewing 15 minutes before. Walk, breathe, or do anything mildly distracting. Arriving mentally fresh beats arriving crammed.
Virtual vs in-person prep differences
The content is identical; the logistics diverge:
- Virtual: test your camera, microphone, and the specific platform (Zoom, Teams, and Meet all behave differently) the day before, at the same hour as the interview so you see the actual lighting. Close notification-generating apps. Position notes near your camera line. Our video interview tips cover the full 10-minute setup, including one-way recorded formats.
- In-person: plan clothing the night before (one level above the company's daily dress code is a safe default), and physically pack your bag — the morning is for calm, not for hunting for a stapler-mangled resume copy.
- Phone screens are their own animal — shorter, faster, and mostly about logistics and communication. Compress every answer and keep your notes sheet within reach; the format allows it.
The night-before rule: stop preparing, start resting
Here's the counterintuitive part of any honest answer to how to prepare for an interview: the last hours before bed are for rest, not repetition. By the night before, additional cramming mostly adds anxiety, and anxiety costs you more points than any marginal fact gains you. Interviews reward presence — listening well, pausing before answering, reacting to what's actually asked — and presence comes from sleep.
The rule: after dinner the night before, you may review your one-page notebook summary once. Then close it. Lay out clothes, set two alarms, and do something unrelated. If your brain insists on rehearsing at midnight, keep a notepad by the bed and write the thought down — externalizing it usually quiets it.
The complete checklist, compressed
- 48h: research company (60–90 min), decode job posting (20 min)
- 24h: big five answers (60 min), eight STAR stories (60 min), questions for them (15 min), tech test if virtual (10 min)
- Night before: clothes, bag, alarms, one notebook review, rest
- Day of: eat, arrive early, one warm-up read, stop 15 minutes out
Frequently asked questions
What if I only have 24 hours, not 48?
Compress, don't skip. Do the 15-minute research core, the job-posting decode, the big five answers, and four stories instead of eight (win, failure, conflict, deadline). That's about two and a half hours and covers most of what matters. Skip the deep interviewer research before skipping answer prep.
Should I prepare differently for a panel interview?
Mostly no — the same answers work. Two additions: get the panelists' names and roles in advance if possible, and practice distributing eye contact instead of locking onto the person who asked. Panels also repeat questions across rounds, so consistency matters more than novelty.
How much should I rehearse out loud?
Each core answer, three times out loud, spaced out. The first telling is always rough; the third is usually natural. Past five or six repetitions you start memorizing exact phrasing, which makes you brittle when the question comes in a slightly different form.
Is it okay to bring notes into the interview?
In-person: a notebook with your questions and a few keywords is normal and reads as organized — just don't read answers from it. Virtual: brief notes are fine, but keep them minimal and near the camera; visible reading is more obvious on video than people think.
Ready before the interview even exists
Half of interview prep is really resume prep — the stories you rehearse should already be visible in the document that got you the call. Paste yours into Workplacea's free resume checker and see whether your strongest evidence is actually coming through, or tighten it directly in the editor before your next application.