As the radio industry gathers in Vancouver for this week’s WABE convention, I’ve been thinking about how important engineering is in a radio station—and how easily its contribution can be overlooked.

One of the most important people in a radio station is often the one whose contribution everyone else in the building understands least.

Most radio staff understand what the salesperson does. They understand the morning show. They understand programming, promotions, news, traffic, reception.

Engineering is different.

When engineering is excellent, nobody notices.

The audio sounds good. The automation works. The studios work. The transmitter stays on. Remotes work. Phones work. Equipment gets replaced before it fails. Emergencies get solved.

Everything just…works.

And because everything works, it’s remarkably easy for the rest of the organization to underestimate why everything works.

Then something fails. Or worse, something just doesn’t sound right.

Engineering Speaks a Different Language

Communicating with an engineer is somewhat of an art.

Most people on the content side of the business—program directors, on-air talent, producers—approach problems from a creative or operational perspective. An engineer approaches the same problem from a technical, analytical perspective.

The two perspectives don’t always line up.

A PD hears an audio problem. An engineer hears a signal path.

An announcer hears something that “doesn’t sound right.” An engineer starts thinking about where in the chain the problem originates.

The best engineers I’ve worked with have another skill that doesn’t always get recognized: they can translate technical details into language the rest of the organization can understand.

I’ve watched innocent conversations between programmers and engineers quickly become adversarial simply because they weren’t speaking the same “language.” I’ve also seen the opposite: when an engineer can explain a technical solution in terms a programmer can understand, and a programmer can describe a problem in a way the engineer can diagnose, the tension often disappears.

The Job Has Changed

The role of the radio engineer has changed dramatically since I started in the business, particularly in the last decade or so.

The transmitter and audio chain are still there, of course. But today’s engineer is dealing with a much broader and more complicated technical environment.

IP networks. Automation systems. Studio computers. Streaming. Remote broadcasting. Cloud-based services. Audio processing. Cybersecurity. Redundancy and disaster recovery. Software integrations. And an ever-growing list of systems that have to work together for a modern radio station to stay on the air and feed several different delivery points.

In many smaller radio companies, and even some larger ones, a single engineer may handle all of it—across multiple stations in faraway markets.

And that changes the job.

The engineer isn’t simply the person who fixes things when they break anymore. They’re increasingly involved in how the business operates, what technology it invests in, how resilient it is, and how efficiently it can operate.

I Learned This by Building Stations

When I started in radio, I thought of engineering like everyone else: keep the station on the air, fix things when they break, and make sure everything works.

That understanding changed when I began building stations of my own.

Suddenly, engineering wasn’t just about keeping the station running. It was part of deciding how to build the station in the first place.

What technology should we use? How much redundancy do we need? Where should we spend money? How do we make a facility reliable enough to operate with a small staff?

That’s when I began to understand just how much engineering contributes to a radio company.

I’ve had the great fortune of working with several exceptional engineers throughout my career. They became mentors in ways they probably didn’t realize at the time. I learned from them not just about technology, but about how to think about technology—and how technical decisions can ultimately affect the entire business.

When you’re building a radio station, every technical decision has a business consequence.

Spend too little, and you may create reliability problems that cost far more later. Spend too much, and you’ve tied up capital that could have been used elsewhere. Choose the wrong technology, and you may create an infrastructure that becomes expensive or difficult to maintain.

They didn’t simply tell me what we could do technically. They helped me understand what we should do as a business.

More Than a Technical Resource

The irony is that the better the engineer is, the less most of the organization notices.

That’s not a failure of recognition. It’s often the clearest evidence that they’re doing their job exceptionally well.

But perhaps we should notice anyway.

We should involve engineers earlier. Listen to them when they’re making recommendations. Give them a seat at the table when we make any decisions about how the station operates.

A great engineer isn’t simply a technical resource. They’re one of the most valuable strategic partners a radio company can have.

Because when everything just works, it isn’t luck.

Someone made sure it would.