Working With the House Engineer

The house engineer is the most influential person in the room that your band has any control over. The booker decided you're playing; the audience decides if they care; but how you actually sound — the only part of the night strangers will remember — passes through the hands of someone you'll know for about four hours. Bands spend years upgrading pedals to improve their sound by degrees, then squander a bigger improvement by treating the person at the console as furniture or, worse, as an adversary.

Here is the thing to understand first: the engineer's incentives are already aligned with yours. Nobody stands behind a console hoping the band sounds bad — a bad mix reflects on them, in their room, in front of their regulars. When the relationship goes wrong it is almost never sabotage; it is a band that gave the engineer nothing to work with, no information, no respect, and thirty seconds of attention.

Before You Play: Information Is the Gift

An engineer meeting your band cold has to reverse-engineer everything: how many inputs, what's loud, who sings, what that laptop does. Every fact you hand over ahead of time is guesswork removed from your mix. This is the whole argument of Advancing a Show — the stage plot and input list exist for this person — but it compresses to something you can do on the night even with no documents: introduce yourselves, say how many inputs you have and what's unusual, and flag the things nobody can see by looking. The backing track that must never reach the house. The guitar amp that runs deliberately quiet. The singer who also plays a floor tom on two songs.

Ask what the engineer prefers, too — where to plug DIs, whether they want amps facing across the stage, what order they'd like to check channels. It costs nothing and it announces that you understand whose workspace you're in.

At Soundcheck: Speak in Nouns, Not Adjectives

Soundcheck breaks down when bands describe feelings and expect fader moves. "It sounds weird up here" gives an engineer nothing; "can I get more of the lead vocal in this wedge, and a bit less kick" is a sentence they can act on before you finish saying it. The formula is always the same: name the channel, name the direction, name where — more/less, of what, in which monitor. That's the entire language, and Monitors and Stage Sound explains why requests phrased that way work and "more me" spirals don't.

The other soundcheck disciplines are quick to list. Play at the volume you'll actually perform at, because a check run at polite volume is a fiction the first chorus destroys. When the engineer asks for the kick drum, play the kick drum — steadily, boringly, until asked to stop; noodling between channel checks is the fastest way to make a check run long. And when something's wrong, say so at soundcheck, not on stage mid-set with a scowl at the booth. The engineer cannot fix what they only learn about from your body language.

Two things are never yours to touch: the console, and the monitor EQ. If a wedge is ringing, report it — hunting feedback is the engineer's craft, with house tools, and Feedback: Why It Happens and How to Kill It is a longer story about why amateur help makes it worse.

During and After

On a multi-band bill you will often get a line check, not a soundcheck — inputs confirmed working, no mix rehearsal — and the etiquette compresses accordingly: be fast, be plugged in, answer channel calls immediately, and trust the engineer to build the mix during your first song. That trust is not optimism; a working engineer mixes unfamiliar bands every week, and the first ninety seconds of your set is them doing their job, not neglecting it.

Mid-set requests are fine when they're rare and specific — the same noun-based sentence, delivered between songs to the booth or through the vocal mic without theatre. What burns the relationship is the running commentary: the mimed complaints, the pointing at wedges, the sarcastic "if anyone can hear me out there." Every engineer in every city has a list of bands they'll never push a fader for again, and every band on it earned the spot in public.

Afterwards, thank them — by name, and if the night went well, in front of the booker. In some scenes a tip is customary for a genuinely above-and-beyond night; in all scenes the thank-you is. Engineers talk to bookers, bookers talk to each other, and "great band, total pros" is a review that books more shows than your recordings do. If you find yourselves wanting this person at every show, that instinct has a name, and When to Bring Your Own Engineer is the honest look at what that costs and buys.

What This Means for You

• Introduce yourselves and hand over information early. Every fact you volunteer is guesswork subtracted from your mix.
• Flag what can't be seen: click tracks, silent rigs, deliberately quiet amps, the singer's second instrument.
• Name the channel and the direction, never the adjective. "More vocal, less kick, in this wedge" is the entire language of monitor requests.
• Check at performance volume, play what's asked, report problems at soundcheck — not from the stage with a scowl.
• Never touch the console or chase feedback yourself. Report it; fixing it is their craft and their tools.
• Expect a line check on shared bills and trust the first song to be the mix rehearsal.
• Thank them by name, in front of the booker. The engineer's one-line review of your band travels further than you think.