ā† Guide index

Part 1 of 8 in A Guide to Speaking at Technology Conferences.

No two conferences are quite alike. Before deciding where to submit, learn what kind of event you are looking at and what its audience expects.

Topic and depth

Some conferences focus tightly on one practice, tool, or community. A specialist testing event might spend an entire day on exploratory testing, performance engineering, accessibility, security, or test automation. These events let you go deep because much of the audience already shares the vocabulary and context.

Broader technology conferences may cover development, operations, product, design, data, leadership, and quality. A talk at one of these events usually needs a little more context and a clear explanation of why the subject matters beyond your immediate specialty.

Tracks and formats

A single-track conference puts every attendee in the same room. Your potential audience is larger, but not everyone will have chosen your subject. A multi-track conference lets attendees select the most relevant session, which can produce a smaller but more engaged room.

Events may offer several formats:

  • Lightning talks of five to fifteen minutes
  • Experience reports or case studies
  • Standard sessions of thirty to sixty minutes
  • Panels or facilitated discussions
  • Hands-on workshops lasting several hours
  • Keynotes intended for the whole conference

Choose a format that fits both the idea and your experience. A focused lightning talk is often a better first step than stretching one lesson into a forty-five-minute session. A workshop needs exercises, facilitation, and enough time for attendees to practice; it is not simply a longer talk.

Audience and scale

An event may be a local meetup with a few dozen people, a regional conference with several hundred, or an international gathering with thousands. Size affects the atmosphere, not necessarily the value. Small events can make conversation and connection easier. Large events may offer more topics and people but can feel less personal.

Look beyond attendance numbers. Ask who comes to the event, what experience levels it serves, and whether attendees are mostly individual contributors, leaders, consultants, academics, tool builders, or a mixture.

Organizers and incentives

Conferences can be community-run, nonprofit, commercial, or organized by a vendor. Each model can produce an excellent event, but its goals influence the program. A vendor event may favor its ecosystem. A volunteer event may have limited money and staff. A commercial conference may have stronger production support while expecting content that helps sell tickets.

Read the code of conduct, speaker agreement, refund policy, and sponsor information. Find out whether speakers receive travel, lodging, an honorarium, a free ticket, or no financial support. None of these arrangements is automatically right or wrong, but you should understand the exchange before committing.

Why attend before speaking?

Attending helps you learn how a community talks about its problems. You can discover techniques, meet collaborators, find future employers or employees, and see different presentation styles. You will also notice what makes an event welcomingā€”or difficultā€”to navigate.

You do not have to attend conferences before you are qualified to speak. Your practical experience can be valuable now. Attending simply gives you more context for choosing the right event and designing a useful session.

ā† Guide index Ā· Part 2: Decide Why You Want to Speak ā†’