What Questions to Ask a DJ Before You Book

Most clients don't ask enough questions before booking a DJ. They check availability, discuss price, skim the portfolio, and sign. This process is fine for low-stakes bookings. For anything significant — a product launch, an awards gala, a conference after-party, a milestone event — it's not sufficient.

The questions below aren't designed to trip anyone up. They're designed to create space for a professional to demonstrate genuine experience versus someone who has done the basics and is hoping the event is uncomplicated.

Questions That Reveal Real Experience

"Can you walk me through how you handled a set when something went wrong?"

This question does several things at once. It's open-ended, so it invites genuine storytelling rather than a prepared answer. It signals that you know events have problems. And it reveals, in the answer, how the DJ thinks about failure.

A weak answer is vague: "Oh, it went fine, we sorted it out." A good answer is specific: what went wrong, what the DJ did, how the event was affected (or wasn't), and what changed afterwards. Look for the specificity and the narrative confidence — someone who has been in that situation tells it differently from someone who is composing an answer on the fly.

"How do you prepare for an event you've never played before — a new venue, a new type of audience?"

Experienced DJs have a process. They research the venue's acoustics and power configuration. They do a site visit if the event is significant. They study the audience demographic and think about what that means for the playlist. They ask specific questions in the briefing rather than waiting for the event to reveal the answers.

Vague answers here — "I just feel it out," "I'm adaptable" — aren't red flags in isolation. But if the answer consistently lacks specifics about what they actually do, that's worth noting.

"What's your process between booking and event day?"

You're looking for evidence of structured preparation. A good answer might include: confirmation of details shortly after booking, a formal briefing call 2–4 weeks out, delivery of a proposed set structure or playlist draft for approval, final logistics check the week before, arrival protocol.

A weak answer is "I just show up on the day." That's not inherently wrong — simpler events require simpler processes — but for anything complex, it's a warning.

Questions About the Specifics of Your Event

"Have you played events like this before? What was different about them?"

The first part is straightforward. The second part is more revealing. A DJ who has played a hundred corporate events and can describe the specific differences — what makes a pharma conference different from a tech launch, what a 50-person dinner looks like compared to a 500-person gala — is demonstrating actual knowledge, not just claiming experience.

"What would you need from me to do this well?"

This question inverts the usual dynamic and gives the DJ an opportunity to demonstrate what they know. A professional knows exactly what they need: a detailed brief, a pre-event call, access to the event timeline, the floor plan, the name of the on-site contact, and clarity on what success looks like for the client.

If they can't articulate what they need, they either don't know, or they don't prepare enough to have formed an opinion. Both are useful information.

"What do you do if the timeline changes significantly on the day?"

Look for calm and specificity. The answer should describe a protocol — who they contact, how they adjust the music structure, how they communicate with the event manager. A good DJ has thought about this. A great one has a story about having done it.

Questions About Logistics and Contracts

"What happens if you're ill or can't make it?"

Any professional has an answer to this. It will typically involve a network of colleagues who can step in at equivalent quality, or a formal agreement with another provider. "That's never happened" is not an answer — it's a gap in thinking about risk.

"What do you bring as backup in case of equipment failure?"

You're not looking for a technical inventory. You're looking for the acknowledgement that failure is possible and that preparation has been made. A specific answer — "I carry a second controller, a laptop with the full library as backup, redundant audio cables, and I always check the venue power before doors open" — tells you something about how that professional thinks. A vague answer doesn't.

"How do you handle music requests on the night?"

This question has no universally right answer — it depends on the DJ and the event. But the answer should be consistent with the brief you've agreed to. If you've specified a controlled playlist and the DJ says "I always take whatever comes from the floor," that's a misalignment worth resolving before the event.

What Vague Answers Signal

Vague answers don't automatically mean a DJ is unprepared. Some very good DJs are poor at articulating their process in words. And some DJs who give polished, detailed answers turn out to be mediocre in practice.

What vague answers signal is a gap. Either the DJ hasn't done this type of event, in which case you need to know that. Or the DJ hasn't thought carefully about these questions, in which case that itself is information. Or the DJ is articulate about some things but not others — and the things they're not articulate about might be exactly what matters for your event.

Use the questions as a diagnostic, not a checklist. The point isn't to collect correct answers. It's to understand, as specifically as possible, who you're about to trust with a significant part of your event.

One last question worth asking yourself: after the conversation, do I feel more confident or less confident? If you feel more confident, that's usually because you've seen real competence. If you feel the same as before, it probably means the conversation revealed nothing. That, too, is a data point.