Hire a Podcast Audio Engineer Who Hits -16 LUFS

Why does one podcast sound polished while another sounds like it was recorded in a parking garage? Usually it comes down to who edited it, not what microphone was used.

By the end of this, you’ll know what to check before you hire, where to actually find candidates, and what questions separate a real audio engineer from someone with a copy of Audacity and good intentions.

Prerequisites:

• A sample episode or raw recording to share with candidates
• A clear idea of your budget per episode or per hour
• Your target platforms (Apple Podcasts, Spotify, etc.)
• Basic familiarity with terms like LUFS, sample rate, and bit rate (we’ll cover these)

Define what “done” sounds like before you post a job

Start with the end result. What does a finished episode need to sound like?

Every platform has technical minimums. Apple’s own spec sheet lists requirements for podcast audio, including sample rates and bit resolutions for different file formats.

For MP3 stereo files, Apple’s minimum is a 44.1 kHz sample rate and 64 kbps bit rate. The recommended range is higher: 128 to 256 kbps.

Write these numbers down. An engineer who doesn’t already know them is a red flag.

Require your engineer to meet streaming loudness targets

Here’s a fact that trips up a lot of new podcasters: a track that peaks correctly can still sound too quiet or too loud next to other shows. Loudness and peak level aren’t the same thing.

Loudness normalization measures perceived loudness using K-weighted LUFS, not raw peak values. That weighting matters because human ears are more sensitive to some frequencies than others. A peak meter doesn’t know that. A LUFS meter does.

Streaming platforms typically target around -14 to -16 LUFS. Broadcast TV runs quieter, at -23 to -24 LUFS. Your engineer should know which target applies to your distribution channels.

This changes how you evaluate a candidate’s past work. Ask them to name the LUFS target they mix to. If they can’t answer without checking, that’s worth noting.

Loudness normalization doesn’t reshape your dynamics. It just moves the whole signal up or down by a fixed amount. That’s a separate job from compression or noise reduction, and a good engineer treats them as separate steps.

Decide which deliverable format you actually need

Apple’s spec table lays out requirements for WAV, FLAC, and MP3 files, each with different sample rate and bit depth minimums. A podcast mastered as a 16-bit, 44.1kHz WAV meets the baseline. Going higher, to 24-bit at 48kHz or beyond, is about headroom for future editing, not something most listeners will hear.

Smaller bit rates make smaller files that stream fast, but they can introduce artifacts that can’t be fixed later. Larger bit rates sound better but cost more bandwidth.

Ask your engineer which format and bit rate they’ll deliver. A clear answer, with a reason attached, tells you they’ve thought about trade-offs instead of just hitting export.

Write a job post that filters out generalists

A vague post attracts vague freelancers. Be specific about episode length, turnaround time, and what “editing” includes for you: noise reduction, leveling, music beds, chapter markers, show notes.

Mention your current pain point directly. If background hiss is your biggest complaint, say so. If your levels bounce between guests, say that too.

Specificity does two things. It filters out people without the right skill set, and it gives serious candidates something concrete to quote against.

Where can you recruit freelance podcast engineers?

Upwork organizes freelancers into categories, including Audio Post Production and separate listings for podcast-specific production work. That split matters more than it looks.

Audio post production freelancers often come from film, music, or broadcast backgrounds. They know loudness standards and noise reduction cold, but may not know podcast-specific habits like chapter markers or dynamic ad insertion points.

Podcast-category freelancers usually understand the full workflow: raw file to published RSS feed. They may be less deep on pure audio repair.

Which one you need depends on where your show currently falls short. Noisy recordings and inconsistent levels point toward an audio post specialist. Messy show notes, slow turnaround, or feed management headaches point toward someone who works in podcasting specifically.

Job boards and freelance marketplaces aren’t your only option. Specialist directories exist too, though vetting still falls on you either way.

Screen candidates with a short paid test, not a long interview

Talk is cheap. A 10-minute paid test on your actual raw audio tells you more than an hour of conversation.

Give every candidate the same unedited clip. Ask for the same deliverable: cleaned audio, leveled to your target LUFS, exported in your chosen format.

Compare results side by side. Listen on headphones and on a phone speaker, since podcasts get consumed both ways.

Pay for the test. It’s a small cost that saves you from a bad multi-episode contract.

Ask about their noise reduction and leveling process

A real answer sounds like a process. A weak answer sounds like a tool name with no context.

Ask what they check first when a file comes in. Ask what they do when a guest’s mic is quieter than the host’s. Ask how they handle room echo that can’t be fully removed.

You’re listening for judgment, not jargon.

Confirm turnaround time and revision policy in writing

Verbal promises evaporate under deadline pressure. Get turnaround time, revision count, and rush fees written into your agreement before the first invoice.

Ask what happens if a file arrives with a problem the engineer didn’t cause, like a corrupted recording or a guest who recorded on a laptop mic. A clear, calm answer beats a vague one.

Revisions should have a defined limit. Unlimited revisions sound generous but usually mean slower turnaround for everyone.

Start with one episode before committing to a season

Don’t sign a 20-episode contract on day one. Run one episode first, review it against your checklist, then decide.

This protects you from a good test file followed by inconsistent ongoing work. It happens more than people expect.

If the first real episode meets your bar, scale up the relationship. If it doesn’t, you’ve lost one episode’s budget instead of a season’s.

Troubleshooting

The mix sounds fine on my laptop but off on headphones or in the car. Ask your engineer to check the mix on at least two playback systems before delivery. This is a basic step many skip.
Loudness is inconsistent between episodes. Confirm the engineer is normalizing to a fixed LUFS target every time, not eyeballing levels by ear alone.
Turnaround keeps slipping past the agreed date. Revisit your written agreement. If there’s no turnaround clause, add one before the next episode.
Background noise is reduced but voices now sound processed or robotic. This usually means noise reduction was pushed too hard. Ask for a lighter pass and compare both versions.

Frequently Asked Questions

How much does it cost to hire a podcast audio engineer?

Rates vary by scope and experience, from per-episode freelance pricing to monthly retainers for ongoing shows. Get quotes based on your specific episode length and deliverables rather than a flat industry number, since editing complexity changes the price more than runtime alone.

What’s the difference between an audio engineer and a podcast editor?

An audio engineer typically focuses on technical sound quality: noise reduction, EQ, loudness normalization, and mastering to platform specs. A podcast editor often handles that plus structural cuts, pacing, and sometimes show notes. Many freelancers do both, so ask directly what’s included.

Do I need to know audio terms before I hire someone?

You don’t need to be an expert, but knowing terms like LUFS, sample rate, and bit rate helps you evaluate candidates and catch vague answers. A few minutes with Apple’s own audio requirements page will get you far enough to ask good questions.

Should I hire per episode or on a monthly retainer?

Per-episode works well when your schedule is irregular or you’re still testing a new engineer. A retainer makes more sense once you have a consistent weekly or biweekly release schedule and trust the quality already.

What file format should I ask my engineer to deliver?

A 16-bit, 44.1kHz WAV file meets Apple’s minimum and gives you a clean master to re-export from later. Confirm your final distribution format too, since most hosting platforms convert to MP3 or AAC before publishing anyway.

---

Bad audio doesn’t just annoy listeners, it quietly pushes them toward the unsubscribe button before they ever hear your best material. Get the engineer right and that problem disappears for good.

If you want help finding growth and monetization opportunities once your sound is sorted, talk to our team at Big Pond Podcasts.

About the author

Tariq Basraoui

CEO

Tariq O’Keefe Basraoui, Co-Founder of Big Pond Podcasts, is a seasoned digital marketer and community builder with a track record of success at platforms like TikTok and Zencastr. Known for launching Zencastr’s Creator Network to over 15,000 members in 18 months, his expertise lies in growing user bases and enhancing brand engagement.

His strategic approach to growth and community engagement has established him as a leader in creating some of the fastest-growing media networks in podcasting.