Interview Tomorrow? A 24-Hour Preparation Plan
A job interview tomorrow: an hour-by-hour plan. Five questions you will get, three work stories, practising out loud, what to bring, and the follow-up.
7 min read · 11/5/2026
Practise this interview with a free question
Answer one real interview question and see how it lands with AI coach Maya. Your first question is free.
The email says ten o'clock tomorrow. The first instinct is to open a list of fifty common questions and read every sample answer. Skip it. Fifty borrowed answers in one evening leave you with other people's sentences in your head, and the first question that matches none of them is where you stall.
This plan assumes you have work or classes today, so four to six real hours. If you run short, cut from the end: the five questions, the three stories and saying them aloud matter most.
The plan in short
- You can't learn a new skill tonight; you can sharpen how you say what you know.
- Prepare bullet points, not scripts, for five questions you'll almost certainly get.
- Three real work stories cover most behavioural questions.
- Say answers aloud and record them. Silent reading hides where you stall.
- Sort documents and the route or video link tonight.
- Send a short thank-you the same day; follow up once.
What 24 hours can change, and what it can't
Be honest about the fixed part. Your experience, your second-language level and what you know about your field are the same tomorrow. If the ad lists software you've never opened, a night of tutorials won't survive one follow-up question.
What moves a lot in a day is delivery: a two-minute introduction instead of five, stories ready, a salary figure decided, arriving on time with your papers. Together they decide most of the first ten minutes.
So the rule for today: study nothing new. Organise what you have, say it aloud, close the practical gaps. Asked about something you don't know, say so and offer the nearest thing you do: "I haven't used SAP, but I ran month-end close on Oracle for two years" beats bluffing.
First hours: read the job and pin down five questions you will almost certainly be asked
Spend the first hour on the job ad. Underline every task and skill it names, and next to each write something specific you did that proves it. Any line you can't match is where the interviewer will push, so prepare one honest sentence for it.
Give the company ten minutes: what it sells or builds, who buys it, whether it's family-owned or part of a group. You need one true answer to "Why here?"
Then write bullet points, not paragraphs, for the five questions that almost never go missing:
- "Tell me about yourself": ninety seconds to two minutes. Where you work, what you actually do, why this role is next. Not where you grew up.
- "Why are you leaving?": one forward-looking reason, no complaints about your manager.
- "Why this job, and why us?": connect one line of the ad to one thing you've done.
- "What are your salary expectations?": decide the number or range tonight, and whether you'll quote base pay or the full package with allowances. Hesitating reads as not having thought about it.
- The technical question for your field: reconciliations for an accountant, a patient or doctor situation for a nurse, a site problem for an engineer, an angry caller for customer service.
Prepare three work stories: situation, action, result
"A difficult situation", "a mistake you made", "a disagreement with a colleague": three good stories cover most of these. Pick one problem you solved, one setback and what changed after it, and one difficult person.
Shape each in the four steps usually called STAR: situation, the task that was yours, the action you personally took, the result. The action is where people go soft, saying "we decided" and "the team handled it". The interviewer wants what you did.
One person's example, not an answer to memorise. A site engineer at a contracting company: "On a villa project, rebar arrived in different diameters from the drawings, two days before the pour. The first slab was mine. I stopped the fixing, sent photos to the technical office and the consultant that day, proposed a substitute from stock with the required steel area, and waited for written approval. The pour slipped three days instead of two, but nothing had to be stripped out, and deliveries are now checked against a list before unloading."
The result isn't perfect: it ran a day over. That's what makes it believable. Swap in your own project and dates, and keep each story to five lines.
Practise out loud, because reading silently isn't enough
Reading an answer in your head, your brain finishes the half-sentences and skips the word you can't recall. Spoken, three things show up: where you stop because you don't know the next sentence, how long it really takes (the one-minute introduction usually comes out at three), and which words trip you, especially in a second language.
Open your phone's voice recorder, read the question, answer without your notes, then listen. You'll hear more "um" than you expect. Do the same question twice more. The third take is almost always shorter and clearer.
If someone's home, have them ask in random order and interrupt once: "And what was the result in numbers?"
Memorise the points and their order, not the wording. A scripted answer sounds scripted, and if one line goes missing the rest follows it.
If the interview may switch languages, rehearse in both. Many interviews start in Arabic and move to English. Engineers are often given a technical question in English, since drawings, specifications and consultant letters are in English.
In customer service and call-centre hiring, the first stage may be an English assessment, often reported against CEFR levels such as B1 or B2. You can't move a level overnight, but you can rehearse your self-introduction in English, usually the first thing they ask for.
Keep one line ready: "Sorry, could you repeat the last part?" It's normal, and better than answering a question you didn't catch. Say technical terms the way you say them at work.
Logistics: getting there, documents and the connection
Most interview-day problems aren't about questions. Close those gaps tonight.
In person: find the building and floor, and check the route at rush hour. Aim to arrive about fifteen minutes early. Some business parks register visitors at the gate or ask for ID; ask in your confirmation reply if unsure.
On video: open the link tonight, install the app (Teams, Zoom or Google Meet), and set your display name to your full name. Test camera and mic, face the light, and keep mobile data as a backup.
On the phone: everything is in your voice. Find a quiet room and keep your expected salary, notice period and start date on a sheet in front of you. Stand if you can.
Requirements vary by employer. Carry a folder with what you may be asked for:
- Two or three printed copies of the CV you sent.
- Your national ID, residence permit or passport.
- Copies of degree and experience certificates, with originals if requested. Some employers may ask for attested copies; if the invitation mentions them, bring them.
- A passport photo, if they still use paper forms.
- A pen and notebook for the names of the people you meet.
Tonight: what to do and what to leave alone
After dinner, preparation is over. What you haven't learned by now you won't learn at midnight, and a late night costs more clarity than an extra hour of reading adds.
- Do: run through the five questions and three stories once, quietly, then put the notes away.
- Do: put clothes, folder, charger and keys in one place, and set two alarms.
- Do: write two or three questions of your own for the end, about the first three months or the team.
- Leave: "100 hardest questions" lists and model-answer videos. They blur your answers into someone else's.
- Leave: late coffee, and scrolling every employee's profile until 2 a.m.
After the interview: a short message, and when to follow up
The same day, send a short thank-you to whoever arranged the interview, on whatever channel they used. Mention one specific thing from the conversation. Don't repeat your CV or ask about the outcome yet.
An example after an accountant interview: "Dear Mr Khalid, thank you for your time today on the General Accountant role. Your point about moving month-end close onto the new system stayed with me; it's close to work I've done in my current company. Happy to send any documents you need. Best regards, Ahmad."
If they said "within a week", wait until the week is up plus one or two working days, then send one polite note asking about the timeline. No date given? Wait about a week. One follow-up is enough; after that, keep your other applications moving.
FAQ
Practise this interview with a free question
Answer one real interview question and see how it lands with AI coach Maya. Your first question is free.