Interview Cheat Sheet: One Page You Can Glance At

A good interview cheat sheet is an index, not a script. It should let you look down for two seconds, catch one cue, and look back up already speaking. That means keywords instead of sentences, a strip of your own numbers and outcomes, and your questions for the interviewer written out in full. It also means a hard cut list, because the page only works if everything on it earns its space.

Here is how to build that page, what to leave off, and how to rehearse with it so it never turns into something you read from.

What an interview cheat sheet is for, and what it is not

The job of the page is to jog your memory, not to hold your answers. You already know your work. What you lose under pressure is the order of things: which project proves which point, which number makes the story land, which question you meant to ask.

A script tells you what to say. A sheet reminds you what you already know. That difference decides every choice below. If an entry could be read aloud word for word, it is too long.

Keep it to one page or one screen. The limit is the point: it forces you to decide which four stories and which handful of numbers actually carry your case, instead of carrying everything and remembering nothing. If you want a fuller method for turning cues into natural speech, our guide on how to sound natural with talking points in a job interview goes deeper.

The five blocks that belong on the page

A working interview cheat sheet has the same five blocks every time. Build them in this order.

1. Talking points. For each likely question area — opening, a behavioural example or two, the role-specific one — write three or four keywords, not sentences.
2. Evidence strip. Six to eight numbers or outcomes from your own work, each with a one-word label: "churn down", "launch early", "team size". Use your real figures, whatever they are.
3. Your questions for them. Written as full sentences, because a half-remembered question comes out muddled.
4. Logistics. Interviewer names and roles, time zone, the meeting link or address, who calls whom.
5. Two lines on how you want to come across. For example: "Curious, specific, unhurried. Ask one clarifying question before answering."

Why this order? Blocks 1 and 2 do the work during answers; block 3 saves you at the end, when nerves often make people say "no, I think that's everything"; block 5 is the only part that steers your manner rather than your content.

What to leave off: the cut list

Most sheets fail because of what is on them, not what is missing. Remove these before you practise:

• Full-sentence answers and memorised openings. They invite reading, and reading sounds flat even when the words are good.
• Generic advice you already know. "Be confident." "Use STAR." It takes up the space your evidence needs and changes nothing in the moment.
• Anything you would not want the interviewer to see. If your screen might be shared, the page should be something you would be comfortable showing.
• Duplicate stories. Two cues for the same project crowd out a story you have not prepared.
• Salary research and company trivia. Useful in prep, distracting live. Keep them on a separate page you close before the call.

A simple test: read each line and ask whether it would change what you say in the next thirty seconds. If not, cut it.

A filled-in example: one candidate's page

Here is an illustrative sheet for a fictional mid-level operations candidate, block by block. It is an example, not a real person's notes.

TALKING POINTS Opening: ops background → process rebuild → why this team Conflict: two teams, one deadline / the trade-off I proposed Failure: missed handover / what I changed after Strength: calm under load / example: peak week

EVIDENCE churn down · launch early · team size · cost down · tickets down · onboarding faster

QUESTIONS FOR THEM What does success look like in the first 90 days? Which process is currently the biggest bottleneck for this team? How do decisions get made when operations and product disagree?

LOGISTICS Priya (Hiring Manager), Sam (Ops Lead). 14:00 GMT. Link in calendar.

HOW I WANT TO COME ACROSS Specific, calm, curious. One clarifying question first.

Notice that every entry is a cue. "Two teams, one deadline / the trade-off I proposed" is enough to rebuild a two-minute answer out loud, because the detail lives in your memory, not on the page. The evidence strip maps to likely questions: churn and cost fit "tell me about an improvement", team size fits "how do you lead", tickets and onboarding fit "how do you measure success".

Cut this sheet in half and you would keep the conflict cue, four numbers and two questions. Nothing important is lost; the page just gets faster to scan. That is the trade you are always making.

Weak versus stronger: rewriting three entries

The opening. Weak: a paragraph beginning "I'm an operations professional with seven years of experience across…" Stronger: ops background → process rebuild → why this team. The keywords let you build a fresh sentence each time, which sounds like speech; the paragraph sounds like recital.

A behavioural example. Weak: the full STAR story written out, six lines long. Stronger: migration deadline / two teams / trade-off I proposed. You still answer in STAR order when you speak — situation, task, action, result — but the page only holds the skeleton. For a fuller worked version of one story, see our guide to the greatest achievement interview answer.

A question to ask. Weak: "What's the culture like?" Stronger: "What does success look like in the first 90 days, and who decides?" The second one gets a real answer, signals that you are thinking about the work, and gives you something to respond to. If questions about how you communicate come up, our piece on communication interview questions has usable structures.

How to lay it out so you can actually glance at it

Format for the glance, not for the read.

• One screen or one side of a page. If it scrolls, it is too long.
• Large text and wide margins. Small dense text makes you lean in and squint, which reads as uncertainty on camera.
• Bold labels, no paragraphs. Your eye should land on EVIDENCE or QUESTIONS without searching.
• Place the evidence strip and your questions where your eyes naturally fall. Usually the middle and lower half of the screen.
• Keep it out of the camera's view. Tilt the screen or move the window so you are looking down briefly, not off to the side for seconds.

Digital or printed both work; pick whichever lets you look and return fastest. A printed page beside the laptop is often easier to glance at than a second monitor, because the movement is smaller.

Practising with the sheet so it doesn't become a crutch

Run three rounds, out loud, in this order.

1. Full sheet. Answer six likely questions with the page in front of you, glancing as needed. Notice which cues you actually use.
2. Keywords only. Cover the evidence strip and questions; keep just the talking points visible. Answer the same six questions again.
3. No sheet. Answer from memory, then check what you forgot. Whatever you missed is what belongs on the page; whatever you never needed can go.

Then rehearse the habit itself: look, take one cue, look back up and speak. Do it slowly at first. The point is to break the loop where your eyes stay down while your mouth runs, which is the thing interviewers notice.

If a question arrives that is not on your sheet, say so plainly and think aloud: "I haven't prepared that one — let me think for a second." Then use the nearest cue you do have. A short, honest pause reads as composure; a scramble through notes does not.

The three mistakes that ruin a good cheat sheet

Overfilling. Treating the page as a security blanket rather than an index. The fix: if a line has not been used in two practice rounds, delete it.

Writing answers instead of cues. Full sentences invite reading, and reading flattens your voice. The fix: rewrite every entry as three to five words and say it out loud to check it still triggers the full story.

Never rehearsing with it. The first glance should not happen live. The fix: run the three rounds above at least once before the call, ideally the day before and again on the morning.

Before you walk in

One page, five blocks, cues not sentences. That is the whole method, and it works because it trusts your memory instead of replacing it. Your next step: open a blank document, set it to one screen, and write the evidence strip first — six numbers or outcomes from your own work. The rest of the sheet gets easier once the proof is in front of you.

Frequently asked questions

Is it okay to look at notes during a video interview?

Brief, occasional glances usually go unnoticed and are normal. What stands out is sustained reading: eyes down for several seconds while you talk. Keep the sheet to one screen, place it close to the camera, and practise the look-take one cue-look up rhythm so each glance lasts a second or two.

How many talking points should one question area have?

Three or four keywords is the useful range. Fewer and you may not have enough to rebuild the story; more and you start scanning instead of speaking. If an area needs five or more cues, it is probably two separate stories that deserve their own line.

Should I write my cheat sheet by hand or type it?

Either works; choose the one you will actually glance at. Handwriting tends to slow you down, which naturally shortens entries, while typing makes it easy to overfill. If you type it, set a strict one-screen limit and cut until it fits without scrolling.

How is this different from just re-reading my CV before the call?

A CV lists what you did for a reader who is screening you. A cheat sheet is written for you mid-answer: cues that trigger stories, numbers you can say aloud, and questions to ask. Re-reading the CV reminds you of dates; the sheet reminds you of the two minutes you want to spend on each story.

What if the interviewer asks something that isn't on my sheet?

Say you want a moment, then think aloud and borrow the nearest cue you have. Most unlisted questions still connect to a story you prepared, just from a different angle. A short honest pause sounds composed; flipping through pages in silence does not.

Rehearse your cues out loud with our blog guides.