Video editor interviews converge on four question types - workflow mechanics, craft judgment, process ownership, and practicalities - and the answers that move you forward are specific: not "I use proxies when needed" but "here is the proxy recipe I ran on the last multi-camera doc, and here is what it saved." This guide walks the questions that actually get asked at each type, what the interviewer is listening for underneath them, and the questions you should be asking back - because the review process on the other side of the table matters as much as your reel.
Workflow questions: can you run a pipeline?
These test whether you can be handed footage and trusted with everything between ingest and delivery. Expect some mix of: "Walk me through your ingest and org process" - they are listening for a repeatable structure (folder conventions, proxies, backups), not improv; the organizational backbone is in how to organize video project files. "How do you handle multicam sync?" - a specific answer (your sync method, your verification pass) beats a menu of options. "What are your export settings for client review vs delivery?" - the strong answer names two different files with different settings, because that distinction is the whole review-vs-delivery split (the export guide is the reference). "How do you name and manage versions?" - vague answers here are the loudest red flag in the interview, because version chaos is the most expensive failure an editor can import into a team; the standard they are comparing you against is in the versioning guide. "Explain proxies and when you would skip them." - a definition-plus-judgment answer (the proxy guide gives you both halves).
Craft questions: can you make decisions?
These test judgment, and they are almost always anchored in your reel. "Walk me through a piece on your portfolio" - the strong version is problem-shaped: the constraint you faced, the choice you made, the tradeoff you accepted; the weak version is a feature tour. Structure every reel story that way (the portfolio guide's context-per-piece rule is in the portfolio guide). "Tell me about feedback that stung and what you did with it." - they are testing coachability and note-taking maturity, so the honest answer includes what you changed in your process, not just your feelings. "How do you decide when a cut is done?" - the mature answer names an external gate (approval on the version, round count, delivery spec) rather than a feeling; editors who ship on vibes create the endless-round problems teams fear.
Process questions: can you own the review loop?
The question type most candidates fumble, and the one teams increasingly weight. "How do you handle conflicting notes from multiple stakeholders?" - the working answer is structural: one decision owner per round, conflicting notes reconciled before they reach the timeline (the etiquette that makes that work is in client feedback etiquette). "How many revision rounds did your last project run, and what kept it there?" - a specific number with a mechanism (contracted rounds, consolidated notes) signals you have run real projects; the norm and the contract clause are in how many revision rounds. "What do you do with a note that is a preference, not a fix?" - naming the distinction is itself the qualification; the note-quality standard is in the review checklist. "Have you worked with a review tool? Walk me through your loop." - describe versions, frame-accurate comments, and the approval record concretely; if you have only ever reviewed via emailed files, say so honestly and describe what you would change.
Practical questions: the boring ones that decide offers
NLE honesty: claim depth only where you can survive a follow-up - "daily driver Premiere, competent Resolve, aware of FCP" beats a resume claiming all three equally. Take-home tests: a scoped exercise (a few hours on provided material) is normal; anything approaching unpaid spec work on their content deserves a scope conversation - "happy to do a focused edit on provided footage; for anything using your brand assets, let's scope it properly" is a professional line, not a risk. Timeline: have a real answer for turnaround expectations (same-day social cuts vs week-long docs are different jobs) - the vertical/social variant expectations are in the vertical review guide.
The questions you should ask them
The interview is also your diligence pass, and these four questions surface the things that make editor jobs good or miserable. "How do review rounds run here - tool, rounds per project, who signs off?" (an honest answer exists; a shrug means the chaos is real). "Who consolidates client notes before they reach the editor?" (the difference between an editor job and a note-archaeology job). "What does the delivery spec process look like - who owns it?" "What happened on the last project that ran long, and what caused it?" - the answer tells you more about the team's process health than any perks list. Their answers, plus your references, are the real job description.
FAQ
What questions do they ask in a video editor interview?
Four types: workflow mechanics (ingest, proxies, versions, exports), craft judgment (portfolio walk-throughs, done-ness), process ownership (rounds, conflicting notes, review tools), and practicalities (NLE honesty, take-homes, turnaround). Preparing one specific story per type beats rehearsing generic answers.
How do I talk about my portfolio in an interview?
Problem-shaped, not feature-shaped: for each piece, the constraint, the choice, and the tradeoff. Two or three pieces told deeply beat seven pieces toured - and keep the reel itself tight; the structure advice is in the portfolio guide.
Should I do a free test edit for a job interview?
A short, scoped exercise on provided material is a normal part of the process. Unpaid work on the company's real brand content is not an exercise, it is spec work - it is reasonable to offer the scoped version and ask to scope anything larger. How you hold that line is itself an interview answer: editors who manage scope well manage client rounds well.
What questions should I ask at the end of an editor interview?
The process-health four: how review rounds run (tool, count, sign-off), who consolidates notes before the editor sees them, who owns delivery specs, and what went wrong on the last project that ran long. You are interviewing their review process as hard as they are interviewing your cutting - the loop you are joining is in the approval workflow guide.