Video editor interview questions: the eight they ask, and what each one is checking

On 16 October 2026 I typed "video editor interview" into Google, and the third suggestion it offered was "questions and answers pdf".

YouTube's search box suggested "video editor interview tips" for the same phrase.

So people want an answer key. A file you can read the night before and repeat.

Here is the complication. That file will hurt you.

Short-form editing interviews are rarely a quiz. The person across the call wants to hear you think about a cut, and a memorised answer sounds memorised by the second sentence.

So this post gives you the eight questions that keep coming back, and what each one is checking. Not the words to say.

One honest limit before we start. Nobody publishes a standard question list for this job. These come from paying editors across the VALORAE group, which makes them a pattern, not a law.

Question 1: "Walk me through one of your edits"

This is the question the rest of the interview hangs on.

What it checks: can you explain a decision. Why the clip opens where it does, why that caption sits there, why you cut the pause at that frame.

Pick one edit before the call. Short, recent, yours.

Then be ready to go through it cut by cut. "I started on the answer instead of the question because the question took four seconds to land" is a real answer. "I wanted it to feel engaging" is not.

If you are new and nobody has paid you yet, use practice work. Footage you are allowed to cut is fine, and our post on podcast clips for editing practice lists where to find some.

Question 2: "What would you change in this video?"

Sometimes it is one of their videos. Sometimes it is one of yours.

Both versions check the same thing: taste under pressure, and whether you can criticise without either flattering or trashing.

Don't redesign the whole channel.

Name one or two specific moments. The first second, a dead stretch in the middle, a caption that covers a face. Say what you would do instead and why.

If it is their video, be direct but kind. They made it, and somebody in the room may have approved it.

Question 3: "How do you take notes?"

This is the question most candidates rush, and it is the one hirers care about most.

The hiring guide on tgsidd.com tells people to judge the revision, not the first cut, and spends a whole section on it in how to hire a video editor, in eight steps. Read it before your interview. It is the other side of this exact conversation.

What they want to hear is a process. You read every note before touching the timeline. You fix what was asked without breaking something else. You ask one question when a note is vague, instead of guessing.

So say that, and give one example of a note you once disagreed with and what you did about it.

Question 4: "How do you think about retention?"

For short-form, this question is the job.

It checks whether you edit for the viewer or for yourself.

Bring the platform's own language. YouTube's help page on the key moments for audience retention report, read on 16 October 2026, breaks a video into intros, top moments, spikes and dips. It describes dips as moments that were "either skipped or moments where viewers stopped watching."

So answer like an editor who has opened that report. Which dip you go after first. What you would cut, move or tighten to close it.

Do not quote a retention number you cannot source. Talking about how you would read the report is stronger than a figure you half remember from a video.

Question 5: "How do you hand off files?"

This sounds like admin. It is a trust question.

The person asking has been burned by an editor who vanished and left a project nobody else could open. Missing fonts, offline media, a folder called "final final 2".

So answer with how you package a project. In Premiere that is the Project Manager, which can collect a sequence and its media into one folder. In DaVinci Resolve it is Media Management. Name whichever one you use and say you would do it on every delivery.

Then mention naming. A file named the way the brief asked is the smallest proof that you read the brief.

Question 6: "How fast are you?"

Careful here. This is where editors talk themselves into a deadline they cannot hit.

What it checks is honesty, more than speed.

Give a range for a specific kind of edit, and say what moves it. Clean footage with a clear brief is one number. Raw recordings with no brief and three rounds of notes is another.

Then stop. Do not promise a turnaround to win the room. The first missed deadline costs you more than the slower answer would have.

Question 7: "What is your rate?"

The worst answer is a number with nothing attached to it.

What it checks is whether you know what you are pricing. Volume, turnaround, how many revision rounds, who supplies captions, music and thumbnails.

Our post on what to charge as a short-form editor goes through those terms. Have your answers ready before the call so the number you say has a scope beside it.

If they ask about clipping experience and what clipping pays, give the real terms of a campaign you know. In VALORAE Cast, campaign clips pay starting from $0.80 per 1,000 views, and that number means nothing until the minimum and cap are read with it.

Question 8: "Would you do a quick test?"

This is the last question, and it decides whether the interview was worth it.

A test is normal. A free test is not.

Say yes to a test and no to free in the same sentence. Ask for it to be paid, short, scoped in writing with one revision round and a deadline, and watermarked until payment clears.

That is the same shape the hiring guide above asks hirers to offer. So you are not asking for anything strange. You are quoting their own side's advice back to them.

If they refuse every one of those terms, you have learned what working for them would be like, and you learned it before doing any work. The full script for that conversation is in our post on free trial edits.

I will be honest about the risk. Some hirers will pass on you for asking. That one stings. But the ones who stay are the ones who pay on time later.

The short version

• Skip the answers PDF and prepare one edit you can explain cut by cut.
• Criticise one or two specific moments, never the whole channel.
• Describe how you take notes, with one real example.
• Talk retention in the platform's own terms, and quote no number you cannot source.
• Package every project so someone else can open it.
• Give speed as a range with conditions, and price with a scope attached.
• Agree to a test only when it is paid, short and scoped in writing.

Editors who want to rehearse these with people doing the same work are in the VALORAE Cast Discord at discord.gg/valoraecast.