Most hosts hire their editor on a feeling, they look at a portfolio, they like the person on the call, the price sounds fine, and they say yes, and I am not against feelings at all, instinct is a real signal when you are choosing who to work with. The trouble is that the problems with podcast editors almost never show up in a portfolio or a friendly call, they show up in week seven, when an episode is late and nobody replies, or in month five, when you want to leave and suddenly the project files are complicated, and by then you have already built your publishing schedule around someone you never really questioned.
So I put together the interview script I would want a host to use on any editor, including us, because I run Pixel Samy Podcast and I would much rather be hired by someone who asked hard questions than by someone who will be disappointed later. For each question I will tell you what a good answer sounds like and what a worrying answer sounds like, and you can run the whole thing in about fifteen minutes, right, which is a very small price for a decision you will live with every single week.
Why does a short interview script beat a gut feeling?
Because a script makes every editor answer the same questions, so you compare how they actually work instead of comparing how charming they are on a call.
When you talk to three editors without a script, right, each conversation goes wherever the editor steers it, usually towards their best work, and you end up comparing three highlight reels. With a script, you hear three answers to the same question about late deliveries or file handoff, and the differences jump out very quickly. The broader framework is on the page about how to choose a podcast editor, and this script is basically the conversation version of it, the part you do out loud.
Write the answers down while you listen. It sounds fussy, but a week later you will not remember who said what, and the written notes are what let you make a calm decision.
Will a human listen to my whole episode, and what are the tools for?
A good answer is a clear yes, a person watches and listens to the full episode and makes every cut decision, while software handles mechanical jobs like syncing and noise cleanup.
That is the answer you want because the editing decisions are where a show is made or broken, what stays in, what goes, where a pause is honest and where it is dead air, and a tool cannot hear the difference. The worrying answer sounds like "an AI tool takes the silences out and then we check it", because in practice that tends to mean a detector made the decisions and a person skimmed whatever was left, and a show cut that way has a slightly breathless, stop start feel you can hear inside a minute. Another worrying answer is a vague one, where the editor talks about software brands for two minutes and never actually says who listens.
For context, that is the line we hold on our own team, a person hears every minute before deciding anything, the software is kept to syncing and cleaning, and no pause is ever taken out by a detector.
What exactly happens between my upload and the first cut?
A good answer walks you through the steps in order, how files reach the editor, how cameras and audio get synced, what gets cut, how colour and mix are handled and when graphics go in.
You are listening for a process that has been done hundreds of times and can be described without hesitation, right, because an editor who has a real workflow will lay it out the same way every time. The worrying answer is "it depends" with nothing after it, or a description that changes as they go, or a process where you are expected to export and compress your own files first, which costs you quality before the edit has even started.
Also ask about limits, file size limits on the upload, how many cameras they can handle, and how long an episode can be before the timing changes, because a good editor will tell you up front where their process stretches.
How long until I get the first cut, and what happens when you are late?
A good answer gives you a specific turnaround in hours or days and tells you plainly which situations take longer, along with how you will be told before a deadline slips, not after.
This is the question most hosts skip and the one that matters most once you publish on a schedule. "Usually pretty fast" is a worrying answer, because it means there is no number to hold anyone to. "Two days" is a good answer, and "two days, except that a very long recording or a four camera shoot needs one more, and you will hear that from us the day the files arrive" is a better one, because it tells you they have already mapped out where their own promise stretches.
Then ask the second half directly, what happens when you are late. The worrying answer is silence, or a joke, or "that never happens", because it always happens to somebody eventually, and an editor who has not thought about it will handle it badly. The good answer is a simple rule, they tell you as soon as they know, with a new time, and they do not wait for you to chase.
How do revisions work, and what do they cost?
A good answer tells you how many revision rounds are included, how you send notes, how fast revisions come back and exactly what, if anything, costs extra.
The worrying answer is "we can talk about that when it comes up", right, because that is how hosts end up with a surprise invoice for a third round of changes on an episode that was meant to be a fixed price. Ask how notes should be sent, one consolidated pass or a stream of messages, because a good editor will have a preference and a reason for it. I wrote about why one clean pass works best on the post about the revision round that actually works, and if an editor offers unlimited revisions, the post on what unlimited revisions really means explains where to look for the catch.
The answers that matter are the boring ones, so ask about late episodes and file handoff before you ask about style.
Who owns the raw files, project files and exports?
A good answer is that every file belongs to you, the original recordings, the editing projects and the finished episodes, and that leaving means the projects come with you so a new editor can open them and carry on.
This is the question where a worrying answer can cost you the most. If the editor says you get the final exports but the project files stay with them, right, then the day you leave, every episode is effectively locked, nobody can fix a typo in a lower third or recut an old episode into clips without starting from scratch. The post on who actually owns your podcast files goes into the contract side, and to be very honest, if this answer is anything other than a clear yes, I would treat it as a reason to keep looking, whatever the price.
What happens to my files if a drive fails or you disappear?
A good answer explains where your files live while the work is in progress, how they are protected against a single drive or laptop failing, and how you would get them back if the editor stopped working tomorrow.
You do not need a lecture on storage, right, you just need to hear that the editor has thought about it at all. The worrying answer is "everything is on my laptop", because one spilled coffee and your back catalogue is gone, or a shrug, which means the question has never come up. Whatever the editor says, keep your own copy of the raw recordings, always, because that is the one thing nobody else can replace for you, and the post on the file handoff that does not break has more on keeping the handoff clean in both directions.
How do we talk, and how fast do you reply?
A good answer names the channel, email, a shared folder, a project tool, and gives you a realistic reply window, plus who to contact if your usual person is away.
That last part is what separates a solo editor from a team, right, because with one person the honest answer to "who covers when you are sick" is often "nobody", and that is fine as long as you know it. The worrying answers are the extreme ones, "message me any time and I will reply instantly", which no human can keep up, or no clear answer at all. For an async workflow across time zones, what you want is predictability, not speed, you see the difference, a reply you can count on beats a fast reply you cannot.
Ask how they handle sponsor reads too, because sponsored segments come with disclosure expectations, and the FTC's guidance on endorsements and sponsorships is worth reading before you place one.
How I would answer these questions for Pixel Samy Podcast
Since I asked you to put every editor through this, it is only fair that I answer it myself, briefly, with the facts as they are.
On the human question, somebody on our team listens to every episode from the first second to the last, and the software never gets further than syncing angles and cleaning audio. On the process, the recordings go into a shared folder at whatever size the cameras produced, we take it from the sync through to the final mix, the first cut is with you two days later, and your one round of notes is turned around in a working day, with the order of all of it on the how it works page. On lateness, an episode that runs unusually long, carries heavy graphics or was shot on four cameras gets one extra day, and you hear that when the files land rather than on the deadline. On revisions, our 199 dollar single camera plan includes one round and the multi-cam plan has no cap at all, the details sit on the pricing section, and nothing ties you to us beyond the episode you paid for. On files, every one of them is yours, and the project files leave with you if you do. And on communication and cover, there are nearly fifty of us working together in Dubai, so your show is never at the mercy of one editor having a bad week.
If you want something to bring to every call, the podcast editing checklist is the list I run on every episode, and if you are still unsure whether to ask for a sample first, I wrote about free test edits separately. At the end of the day the script works on us exactly the way it works on anyone, so bring it to a 15 minute call, I will go through a recent episode of yours and price it while we talk, or put the questions in an email to samy@pixelsamy.com, and hold my answers to exactly the same standard as everyone else's. So yeah. That's my way of saying it.