Most of the shows I see coming out of the online learning world are not really talk shows at all, right, they are lessons wearing a podcast costume, with a host who has a learning objective in their head, a guest who is there to demonstrate or explain something, and a listener who genuinely wants to walk away able to do a thing they could not do an hour earlier. That changes how an episode should be edited far more than people expect, and it is the reason I wanted to write something specific for the people in Tempe who build learning for a living, the instructional designers, the online program teams and the edtech founders who started a show because their product teaches and a podcast felt like the most natural way to prove it.
Tempe is a good place to think about this, because Arizona State University has its main campus there, and ASU is one of the largest universities in the United States with a very large online program attached to it, so a lot of the people around that city spend their working week designing for learners they will never meet in a room. That is basically the exact situation of a podcast audience, and it is also the situation we work in every day at Pixel Samy Podcast, where the editors sit in Dubai and the shows arrive from everywhere.
Why do lesson-shaped episodes need a different edit?
Because a learner is following a sequence, and an edit that trims for entertainment pacing can quietly remove the one step that made the next five minutes make sense. On a lesson episode the order of ideas is the product, so the editor has to protect that order first and tighten second.
Here is what that looks like in practice. On a typical interview show, if the guest wanders for ninety seconds before reaching the point, we tighten it and nobody misses anything, but on a learning show those ninety seconds sometimes hold the definition, or the worked example, or the moment where the host says this is where most students get stuck, which an instructional designer would have flagged in the outline as essential. So the first thing our editors do on a show like this is work out the shape of the lesson, what the host is trying to teach, where the examples sit, where the recap lands, and then they cut around that shape rather than through it, which is a really really different instinct from the one you build cutting comedy or founder interviews.
The second thing is that learners rewind, right, they scrub back to hear an explanation a second time and they jump forward to the part they came for, so the episode needs clean edges between sections that make it easy to land in the spot they wanted. And the third thing is the pause. In a normal conversation we might take out a beat after a question, but when a host asks the audience to think about something before giving the answer, that silence is doing teaching work, so it stays. I wrote about the classroom side of this in podcast editing for teachers and educators, and the version where the episode becomes part of a paid program lives on the page about podcast editing for course creators, so here I will stick to what is different about the edtech and online program crowd.
What Tempe's online learning teams already know about remote production
The people who build online programs already understand that learning does not need a shared room, and the same thing is true of editing a show, because the work lives in the files and in the notes rather than in who sits next to whom.
If you work on an online program at a big university, you have probably spent years shipping course video to students spread across every time zone, reviewing assets asynchronously, leaving comments against timestamps and approving modules without ever meeting the person who produced them, so a remote editor is not a leap for you, it is just how your week already runs.
What that crowd usually worries about is something else entirely, which is whether the editor understands learners, whether captions will be accurate on technical vocabulary, whether chapters will match the outline, and whether the show will still sound like the institution or the brand once a stranger has touched it. Those are fair questions and I will get to each of them, but notice that the editor being in Tempe is not really on that list once you think about it for a minute, and I suspect you had already spotted that before I said it, right.
Does an edtech team in Tempe have to hire someone local?
For the editing itself, no, because nothing in a learning episode requires the editor to share a city with you, and the handoff between your recording and our edit happens through a shared folder whether we sit in Arizona or in Dubai. Local matters for the recording day, if you want someone in person to light a room, place cameras or run sound.
So if you are recording in a campus studio, in a meeting room with a decent camera, or remotely with guests on a recording platform, you already have the part that needs to be local, and the editing can sit wherever the best people for it happen to be. I made the longer version of that argument in why distance matters less than people assume when hiring an editor, and the mechanics of how a remote edit runs day to day, the folder, the notes, the delivery, are on the page about remote podcast editing that works in any timezone. If your show is a few miles south with a recruiting or engineering focus, the same reasoning holds, and I wrote that one separately as Chandler podcast editing for semiconductor engineers.
The honest exception is a team that wants an editor physically present during recording, coaching the host, adjusting framing and making calls on the spot, because that is a production job and nobody can do it from the other side of the world. For that, a local crew is the better hire, and you can still send the finished files to someone else for the edit afterwards.
How does the 11 hour gap between Arizona and Dubai play out?
Dubai is 11 hours ahead of Tempe every single day of the year, so an upload you finish at 7 pm in Arizona lands at 6 am in Dubai, and work on your episode starts while you are asleep. Because Arizona stays on standard time all year and Dubai never changes its clocks either, that gap does not move.
That last detail sounds small, right, but it turns out to be very convenient, because teams in most other US states have to remember twice a year that their overlap with Dubai has shifted by an hour, and Arizona simply does not have the problem, so the clock difference you learn in the first week is the one you keep. A world clock set to Dubai confirms it in a second.
In practice the rhythm goes like this: you record during your day, upload in the evening, and the first cut is sitting in your folder about two days after the upload, which for a weekly show leaves plenty of room for your notes, one round of revisions and a scheduled publish without anyone working late on either side.
Captions, chapters and the learner who comes back for one section
Learning shows lean on captions and chapters more than almost any other category I edit, because the audience uses the episode the way they would use a course module, dipping in, going back, searching for the bit they need.
Captions for a learning audience have to get the technical vocabulary right, the name of the framework, the acronym, the software, because a wrong caption on a key term does more harm than no caption at all for someone trying to learn that term. The W3C guidance on captions is a useful reference if your institution has accessibility requirements, and most online programs do, and our page on podcast captions and subtitles covers how we check them against the audio.
Chapters work in a similar way, they turn a forty minute episode into a set of sections a learner can move between, and YouTube explains how video chapters are built from timestamps. For instance, if your episode follows a structure like problem, concept, example, common mistake and recap, those five beats become your chapters almost automatically, and the editor who cut the episode knows where each one starts because they protected those edges in the first place. That is why I prefer chapters written by the person who edited the episode, and there is more on that in show notes and chapters written by your editor.
What does a lesson-length episode cost per episode?
Most lesson episodes from online learning teams run somewhere around twenty to thirty minutes, and on our Starter plan an episode up to 30 minutes is 150 dollars, a fixed price with a human listening through every minute of it. Longer runs, more cameras and 4K sit on the Studio plan.
The full breakdown is in the pricing section, but for a single camera lesson show with one host and perhaps a guest, 150 dollars is usually where it lands, and you pay per episode with no retainer, so if the show pauses for a semester or a product launch you are not paying for empty months. The thing I would tell an edtech founder comparing this with doing it internally is to count the hours honestly, because a person who edits a thirty minute lesson properly, listening through, cutting, levelling, captioning and exporting, is giving up a good part of a day for it, usually from someone with a product or a course to ship.
When a different kind of editor is the better hire
There are teams in Tempe who should not hire us, and I would rather say so plainly than pretend every show fits.
If your institution already has an instructional media group with an editor on staff who knows the brand guidelines and has room in their week, use them, right, because nobody will know your house style better and the work stays inside the building. If the show is a single run of six episodes attached to one course and then it ends, a freelancer you brief once may be simpler than setting up an ongoing relationship with any team. And if your episodes are mostly screen recordings of software with a voiceover on top, that is closer to tutorial production than podcast editing, and the built-in editor in your recording tool, or the person who recorded it, may honestly be enough.
Where we fit well is the recurring show, weekly or every other week, where the team wants the same standard every time without hiring for it, and where the episodes are real conversations or lessons that benefit from someone with judgment listening to the whole thing.
What should a Tempe team send before the first episode?
Send a couple of your latest episodes, or if the show is brand new, your brand assets and any style guide, plus the outline you recorded from, because the outline tells our editors exactly where each section of the lesson starts and ends. A glossary of technical terms helps the captions too.
If you already have an intro, lower thirds and a colour look your learners recognise, we rebuild them to match so the switch is invisible to the people watching, and if you have nothing yet, we build a simple package that fits the institution or the product. The project files stay yours throughout, so if the program changes vendors next year, your media team can open everything and carry on from where we stopped. If you want a second opinion first, mail samy@pixelsamy.com with a link to the lesson episode you are proudest of, and I will reply with the two or three things I would protect and the price for your format.
Where the lesson actually lives
The thing I keep coming back to with education shows is that the lesson lives in the structure, in the order of the steps and the space around the hard parts, and not in how tight the pacing feels on a first watch.
On a learning show, the edit's first job is to keep the lesson in the right order, and only then to make it shorter.
So when someone in Tempe asks me what they are really paying an editor for, my answer is that they are paying for a person who understands that the learner on the other end is trying to follow along, and who cuts with that learner in mind, every episode, at the same standard. So yeah. That's my way of saying it.