Broadcast technician interview questions, and how to answer them

A broadcast technician interview is less about your resume and more about how you think when the air is at risk. Expect the chief engineer to hand you a fault and watch you work through it out loud. The good news: calm, methodical troubleshooting beats knowing every model number.

12 questions7 minute read

Part 1

1.A studio camera shows up on the router with no picture. Walk me through what you check.

Why they ask

This is the classic signal-flow test. They want to see whether you work the chain in order or start swapping gear at random.

How to answer

  • Confirm the problem: is it one destination or every destination, and does the camera look fine on its own CCU monitor
  • Check the router crosspoint and source assignment in the control panel or software
  • Move down the chain: CCU output, patch bay normals, the cable into the router input
  • Use a known good source or a patch cable to split the chain in half and narrow it down
  • Fix it, then write down what failed so the next shift knows

2.The main playout server fails in the middle of a commercial break. What do you do in the first minute?

Why they ask

Master control failures cost the station money and embarrassment. They're checking whether you protect the air before you diagnose.

How to answer

  • Get something clean on air first: switch to the backup playout chain or a standby slate
  • Tell master control and the operations manager what's happening in one sentence
  • Only then start diagnosing the main server, checking logs and storage
  • Note which spots missed air so traffic can arrange make-goods

3.How do you use a waveform monitor and vectorscope, and what are you looking for?

Why they ask

Plenty of applicants have seen the scopes. Fewer can use them to match cameras or catch an illegal signal.

How to answer

  • Waveform shows luminance levels, so you check black and white levels stay within legal limits
  • Vectorscope shows hue and saturation, so you check color bars land in their targets
  • Describe matching studio cameras before a show by shading to the same levels
  • Mention catching a problem, such as a clipped white level on a set light change
4.Explain genlock and why a studio needs a sync reference.

Why they ask

Timing problems cause glitches on every switch, and they're hard to find if you don't understand sync.

How to answer

  • Every source has to be locked to the same reference so the switcher can cut cleanly between them
  • A sync generator sends black burst or tri-level sync to cameras, frame syncs and switchers
  • Unlocked or mistimed sources cause rolls, flashes or frame drops on a cut
  • If they run IP video, mention PTP as the timing reference in that world
5.A reporter's live shot over bonded cellular keeps breaking up an hour before air. How do you handle it?

Why they ask

Field shots fail all the time. They want to know whether you can fix what's fixable and have a fallback ready for what isn't.

How to answer

  • Check the unit's dashboard for which modems are connected and how much bandwidth each has
  • Ask the photographer to move away from crowds, add a Wi-Fi or wired connection, or raise the delay
  • Lower the bitrate or raise the buffer if picture stability matters more than latency
  • Give the producer a fallback early: a phoner, a recorded package or a different location

Part 2

6.Audio is out of sync with video on one source only. Where do you look?

Why they ask

Lip sync problems are common and annoy viewers fast. The answer shows whether you understand where delay gets added.

How to answer

  • Since it's one source, look at what's unique to that path, not the whole plant
  • Check frame syncs, converters and any processing that adds video delay without matching audio delay
  • Check embedding and de-embedding points and any audio delay settings on the console
  • Measure with a sync test signal instead of guessing by eye
7.How do you handle EAS tests, and what goes in the station log?

Why they ask

The Emergency Alert System is a compliance item. Missed tests and sloppy logs create real trouble during an inspection.

How to answer

  • Describe checking that required tests were received and sent, and relayed where needed
  • Explain logging each test, and logging the reason when one wasn't received
  • Mention checking the encoder and decoder settings and monitoring sources
  • Say you'd confirm the station's own procedures, since requirements can differ
8.What experience do you have with IP video or audio networks?

Why they ask

Stations are moving from SDI and analog audio to networked systems. Technicians who understand both are scarce.

How to answer

  • Name what you've touched: Dante routing, NDI sources, SMPTE IP video, or network switches in a control room
  • Explain the basics: multicast, VLANs, and why timing matters on the network
  • Be honest about limits and describe how you'd learn the rest
  • Mention working with the IT team without stepping on their gear
9.Tell me about a time something went wrong on air because of you.

Why they ask

Everyone in broadcast has caused an on-air mistake. They want to know whether you own it and learn from it.

How to answer

  • Pick a real mistake with a real consequence
  • Say what you did in the moment to recover
  • Explain what you changed afterward, such as a checklist or a labeling fix
  • Keep it short and skip the excuses
10.The news director and the production manager both need you right now. What do you do?

Why they ask

Small engineering teams get pulled in several directions. They're checking your judgment about what protects the air.

How to answer

  • Anything affecting what's on air or about to go on air comes first
  • Tell both people where you're going and when you'll be back
  • Hand off the lower priority task if someone else can take it
  • Loop in your supervisor if the conflict keeps happening

Part 3

11.How do you document changes you make to the plant?

Why they ask

Undocumented patches are how stations end up with mystery cables nobody dares to pull.

How to answer

  • Label both ends of every cable you run
  • Update the drawings, the router database and the patch bay designations
  • Leave a note in the maintenance log or ticket system for the next shift
  • Give an example where good notes saved someone time
12.Why do you want this job, knowing the schedule?

Why they ask

Turnover on overnight and weekend shifts is high. They want someone who'll stay.

How to answer

  • Say plainly that you understand the shifts and on-call and how you'll manage them
  • Connect it to what you like: live pressure, fixing things, learning the whole plant
  • Mention where you want to grow, such as RF or systems work

Questions to ask them

Ask at least two. It shows you're picking them too.

  • How is on-call split, and how often does the phone actually ring overnight?
  • Is master control local, or has it been moved to a hub? What does that leave for the technicians here?
  • What's the biggest project engineering has planned, and would I work on it?
  • Who else is on the engineering team, and who do I call when I'm stuck on a transmitter problem?
  • What does the station pay for in training or SBE certification?