Step 1: The technical setup — do this before anything else
Most video interview preparation guides start with what to say. This one starts with how you look and sound, because technical problems are visible before you say a word and they persist for the entire call regardless of how strong your answers are.
Camera height — the highest-impact change.
The default laptop position puts the camera at chest height or below. This creates two problems: a looking-down angle that reads as disengagement, and a setup that requires you to look down to see the screen, which means looking away from the camera every time you check your notes or watch the interviewer's reactions.
Raise your laptop or webcam until the camera is at eye level or one to two inches above. A stack of books, a shoebox, a laptop stand — anything stable that raises the screen until the camera is level with your eyes. Now looking at the screen and looking at the camera are the same direction. This single change improves the visual impression more than any other technical adjustment.
Light — in front of you, not behind.
A window behind you creates a silhouette. Your face is underexposed, your expressions are unclear, and the high-contrast background draws the interviewer's visual attention away from you.
If you have a window, face it rather than sitting with your back to it. Position a desk lamp in front of you and above your camera so your face is evenly lit. The light source should be in roughly the same direction as the camera — if both are in front of you, the light hits your face and the camera captures it clearly.
Background — simple and controlled.
A cluttered background divides attention. Books, posters, open doors with activity behind them, visible laundry — each element competes with your face for the interviewer's visual attention.
Clear the area behind your chair to a visually simple background. A plain wall is ideal. A tidy bookshelf is acceptable. A Zoom virtual background is fine if your internet connection is stable — unstable connections cause virtual backgrounds to glitch at the edges, which is more distracting than a plain background.
Audio — the variable most candidates underestimate.
Laptop microphones in a hard-floored room produce echo and ambient noise that makes you sound distant and unprofessional. Any earbuds with a microphone — including the basic ones that came with your phone — significantly improve audio quality. Test your audio before the interview by recording a 30-second clip and listening back. If you hear echo, find a room with soft furnishings or use earbuds.
Internet connection.
Use a wired connection if possible. If wifi is your only option, sit as close to the router as the room allows. Close every other application and browser tab before the interview starts — video calls consume significant bandwidth and competing traffic causes frame drops and audio lag.
Step 2: Research — what to know and where to find it
Research serves two purposes in a video interview. It produces the specific examples and references that make your answers feel tailored rather than generic. And it gives you material for the questions you ask at the end — the section most candidates underprepare and that interviewers weight heavily.
Tier 1: The company.
Start with the obvious sources — company website, recent press releases, LinkedIn company page — and work toward less obvious ones.
The less obvious sources are where you find the specific details that distinguish your preparation: recent earnings calls or investor reports if the company is public, Glassdoor reviews for cultural signals, recent news articles for strategic priorities, the company blog for product direction and team communication style.
What you are looking for: the specific challenge or opportunity the company is currently focused on, the language they use to describe their product and market, any recent news (funding, product launch, leadership change, acquisition) that might come up in conversation.
Tier 2: The role.
Read the job description three times. First to understand the role. Second to identify the three or four skills and experiences they are most clearly prioritising. Third to find the specific language they use — words and phrases from the job description that you can mirror in your answers to signal fit.
For each priority skill, identify the specific story from your experience that best demonstrates it. These stories are the raw material for your behavioural answers.
Tier 3: The interviewer.
Find your interviewer on LinkedIn before the call. Look at their background, their tenure at the company, their previous roles, any content they have published. This serves two purposes: it gives you context for how they are likely to approach the interview (a technical lead interviews differently from an HR generalist), and it occasionally surfaces a genuine connection — shared background, shared interest, shared previous employer — that creates rapport.
Step 3: Preparing your answers — the STAR framework and why specifics win
The majority of video interview questions fall into one of three categories: tell me about yourself (structured narrative), why do you want this role (motivation and fit), and behavioural questions ('tell me about a time when...'). Each category has a proven structure.
Tell me about yourself — script this verbatim.
This is the first question in almost every interview. It is also the question where first impressions are formed and where nerves are highest. A well-prepared, confident 90-second answer that covers who you are, what you have done, and why you are here sets the tone for everything that follows.
The structure: current role and key responsibility (two sentences), most relevant previous experience (two to three sentences), specific achievement that demonstrates your value for this role (one to two sentences), why you are here now (one sentence). Under 90 seconds total.
Write this out completely. Practise it with voice scroll until it sounds like you are saying it for the first time, not reciting it.
Why do you want this role — prepare three specific reasons.
Generic answers ('I am excited about the growth opportunity') are the most common failure in this question. Specific answers ('I have been following your expansion into the enterprise segment since the Series B announcement and I want to be part of building the sales infrastructure that makes that work') are the ones that land.
Prepare three specific reasons. Each should reference something concrete — a product decision, a strategic priority, a company value — that you found through research. Generic enthusiasm signals you did not research. Specific enthusiasm signals you did.
Behavioural questions — the STAR framework.
Situation: the specific context. Not 'at my previous company' but 'at [Company], in Q3 last year, when we were six weeks from a product launch and the lead engineer resigned.'
Task: your specific responsibility in that situation. Not 'I was responsible for the project' but 'I had to rebuild the technical team and maintain the launch timeline simultaneously.'
Action: the specific things you did. Three to four concrete actions, not a general description of your approach. Use 'I' not 'we' — the interviewer is assessing your contribution, not your team's.
Result: a specific outcome with a number where possible. Not 'the launch was successful' but 'we launched on schedule, hit 140% of our Q4 target, and retained the client for a three-year contract.'
Specificity is credibility. Vague stories — 'I faced a difficult situation and found a way through it' — generate follow-up questions because they are unconvincing. Specific stories with real numbers and real consequences stand on their own.
Prepare five to seven STAR stories covering the key competencies in the job description. Most interview questions, however they are phrased, can be answered with one of these stories.
Step 4: The delivery challenge — eye contact and recall simultaneously
Video interview delivery has two variables that do not exist in physical interviews and that are harder to manage simultaneously than most candidates anticipate.
Eye contact with the camera.
In a physical interview, eye contact is forgiving — you look at the interviewer, glance away to think, return naturally. In a video interview there is one camera and one correct gaze direction. Looking at the interviewer's face in the Zoom window means looking slightly below the camera. Looking at your notes means looking visibly away. Both break the eye contact signal that interviewers associate with confidence and engagement.
Script recall under pressure.
You have prepared strong answers. You know your STAR stories. But under interview pressure — with an interviewer watching, a question asked differently than you expected, adrenaline affecting recall — the carefully prepared answer becomes harder to access in real time. Filler words fill the gap. Sentences trail off. The story you prepared confidently in your bedroom comes out disjointed on the call.
These are connected problems with one solution.
Zoom background overlay positions your script in direct camera line of sight. Your notes are on the screen. The camera is on the screen. Looking at the notes and looking at the camera are the same action.
The overlay is invisible to the interviewer — they see your face and your background, not the script. Their experience of the call is a candidate who maintains confident eye contact throughout and delivers clear, well-structured answers.
Your experience is a candidate who has their preparation visible in the same direction as the camera, available to glance at without breaking eye contact, scrolling naturally with voice scroll as you speak.
The setup: open SyncedCue, load your interview script, enable Zoom background mode, set the virtual camera in Zoom. Under ten minutes. Invisible to the interviewer.
Step 5: What to put in your interview teleprompter
The worst use of a teleprompter for a job interview is scripting every answer word for word. Verbatim answers to every question produce delivery that sounds rehearsed even when the delivery is technically clean — too smooth, no variation, no response to the specific phrasing of the question.
The right approach uses different script density for different sections:
Opening 90 seconds — script verbatim. Write out the complete answer to 'tell me about yourself.' This is the section where nerves are highest and first impressions are formed. A clean, confident, well-paced 90-second opening that has been practised with voice scroll sounds natural under pressure because the language is already familiar.
STAR stories — structure only, not verbatim. For each prepared story write a four-line prompt: - Situation: [specific context in eight words or fewer] - Task: [your specific responsibility] - Action: [three bullet points — the specific things you did] - Result: [specific outcome with the number]
Glance at the structure, speak the story in your own words. The prompt gives you the skeleton — you provide the flesh in real time. This produces delivery that sounds natural because it is natural, supported by a structure that ensures you hit every key point.
Why this role — three bullet points. Not a scripted answer — three specific reasons you found through research, each in six words or fewer. 'Enterprise expansion since Series B', 'Engineering culture matches how I work', 'Product direction aligns with my background.' Glance, speak naturally.
Questions for the interviewer — script these exactly. Prepare three specific questions based on your research. Keep them at the bottom of your script. The end of every interview ends with 'do you have any questions for us?' — a scripted, specific question here signals genuine engagement and makes a strong final impression.
Notes section — bullet points only. Key company facts, relevant numbers from research, specific product or strategic details that might come up. Not scripted answers — reference material for unexpected questions.
Close — script verbatim. A brief, direct close: 'Based on everything we have discussed, I am genuinely excited about this role. I believe my background in [specific relevant area] would let me [specific contribution]. I hope to continue the conversation.' Clean, confident, specific. Under 30 seconds.
Step 6: How to handle unexpected questions
No interview script covers every question. Interviewers ask follow-ups, probe your answers, go off the standard question list. Here is the approach that handles unexpected questions well without disrupting the overall delivery.
Pause before answering.
When an unexpected question comes, pause. A brief pause before responding signals that you are thinking about the specific question rather than retrieving a pre-formed answer. Interviewers who interview frequently read this as genuine engagement. The instinct to fill silence immediately — with an um, with a half-formed sentence — is what sounds unconfident, not the pause.
Check your notes section.
If the question touches an area covered in your notes — company research, role details, specific technical knowledge — glance at the relevant bullet point before answering. With the overlay active, this glance is invisible to the interviewer. You look at your notes and look at the camera simultaneously.
Answer briefly and specifically.
For a question you have not specifically prepared for, a brief and specific answer beats a long and general one. Two or three sentences that answer the actual question directly are more impressive than a paragraph that circles around it. If you genuinely do not know something, say so directly and explain what you would do to find out — 'I have not worked with that specific framework, but I have built similar systems in [X] and would expect the learning curve to be [Y].'
Bridge back to prepared material where relevant.
A follow-up question often connects to one of your prepared stories. 'That actually connects to a situation I dealt with at [Company]...' bridges from the unexpected question to the prepared answer naturally — and it signals that your experience is relevant to the question even when the question was not anticipated.
Step 7: The day before and the day of — what to do and when to stop
Preparation has diminishing returns. There is a point beyond which additional rehearsal produces worse delivery rather than better — the language becomes over-familiar, the delivery becomes mechanical, and the freshness that makes prepared answers sound natural disappears.
Here is the schedule that maximises preparation without crossing into over-rehearsal:
Two days before: Complete your research. Write your full interview script — opening, STAR story prompts, questions for the interviewer, close. Read through it once and rewrite any sentence that does not sound like you.
The day before: Morning: run the full script once with voice scroll and built-in recording. Not to memorise — to calibrate. Check that voice scroll sensitivity is right, that the opening lands cleanly, that the STAR story prompts give you enough to speak naturally from.
Afternoon: watch the recorded take. Identify two specific things to improve — not a full rewrite, two targeted changes. Make those changes to the script.
Evening: one final run with voice scroll. Then close the script and stop. Sleep.
The morning of the interview: Confirm the technical setup: camera height, light direction, background clear, audio working, internet stable. Open SyncedCue, check the Zoom camera source is set correctly, speak the first three sentences of your opening to confirm voice scroll is active.
Then close your preparation materials. Do not read through the script again. Do not do another full practice run. The preparation is done — additional exposure to the material at this point makes it feel stale rather than fresh.
Five minutes before the call: Open the interview platform, check your video and audio are working, have a glass of water nearby. When the call starts, the preparation is in the script on screen and in the familiarity you built over the previous 48 hours. Trust it.
The questions to prepare — and the ones to prepare for
These are the questions that appear most frequently in video interviews across industries and roles. Prepare a specific answer for each one before any interview:
Tell me about yourself. Structure: current role → key achievement → relevant previous experience → why you are here. Under 90 seconds. Script verbatim.
Why do you want this role? Structure: three specific reasons, each referencing something concrete from your research. Not generic enthusiasm — specific enthusiasm.
Why are you leaving your current role? Structure: one positive reason you are moving toward (growth, challenge, alignment with long-term direction), not one negative reason you are moving away from. Keep it brief.
Tell me about a time you faced a difficult situation. STAR structure. Specific situation, specific action, specific result with a number.
Tell me about a time you failed. STAR structure with an added element: what you learned and how you applied it. The failure itself is less important than the self-awareness and adaptation that followed.
Tell me about a time you led a team. STAR structure. Emphasise the specific things you did to enable others, not your individual contribution.
Tell me about a time you disagreed with a colleague or manager. STAR structure. Show that you can hold a position under pressure and change it when evidence warrants — not that you always win arguments or always defer.
What are your strengths? Three specific strengths, each with a one-sentence concrete example. Not 'I am hardworking' — 'I consistently deliver projects ahead of deadline — in my last role I delivered three consecutive releases early by [specific method].'
What are your weaknesses? One genuine weakness with a genuine improvement effort. Not a strength disguised as a weakness. Not a weakness so significant it disqualifies you. Something real that you are actively working on.
Where do you see yourself in five years? Align the answer with the logical career progression from this role. Not a specific title — a direction that shows ambition and connection to the company's likely trajectory.
What do you know about our company? The specific research you did in Step 2. Reference something concrete — a recent product decision, a strategic priority — not generic praise.
Do you have any questions for us? Three specific prepared questions from your research. This is not optional — candidates who say 'I think you have covered everything' signal that they have not thought seriously about the role.