How to Find Speaking Opportunities

Conferences announce speaking opportunities in specific places. You need to check these places regularly, as deadlines are often short. The primary sources are dedicated call for paper platforms and curated lists.

Confs.tech is a public, community-updated list of technology conferences. It shows event dates, locations, and links to the official call for papers page. It does not show deadlines unless the conference site publishes them. You must click through to the conference's own website for submission details.

PaperCall.io is a platform where organisers manage speaker submissions. Creating a speaker profile here lets you see open calls, submit proposals, and track their status. Many tech events use it. The platform shows submission deadlines clearly.

Industry-specific associations and publications often have a 'events' or 'speak at our conference' page. For example, a marketing publication might list opportunities for the annual marketing summit they run. These are found by searching '[your industry] association conference call for speakers'.

General event listing sites like Lanyrd or Sessionize can be useful, but their coverage is inconsistent. They should be treated as secondary sources to cross-reference, not primary databases.

Not every conference is a good use of your time. Applying to irrelevant events wastes effort and hurts your credibility. Filter using concrete criteria before you write a proposal.

First, match the audience. A conference for senior engineers is wrong for a talk about beginner coding basics. Read the previous year's agenda and speaker list. Look at the attendee job titles the conference promotes. If you cannot clearly state why your talk matters to that specific crowd, skip it.

Second, assess the format. A 45-minute keynote requires a different structure and depth than a 15-minute lightning talk. Some events only accept panel discussions. Ensure you can deliver what they ask for.

Third, consider the cost and location. Some events cover travel and accommodation for speakers, many do not. Calculate the total expense and time commitment before submitting. A local event with no fee is a lower-risk starting point.

Fourth, check for disqualifiers. Some calls are only open to members of a certain organisation, or to people from a specific region. Others require you to use proprietary slide templates or present in a language you are not fluent in. Read the fine print on the submission page.

A conference proposal is not a resume. It is a pitch for a specific session that solves a problem for the organiser's audience. It typically has three parts: a title, an abstract, and speaker bio.

The title must be clear and intriguing. 'Leveraging Synergies for Cloud-Native Transformation' is vague. 'How We Cut AWS Costs by 40% Without Rewriting the App' is specific. It tells the audience exactly what they will learn.

The abstract is a short paragraph, often 150 to 300 words. It should state the audience's starting point, the problem you will address, the key takeaways, and why you are qualified to speak on this. For example: 'Attendees managing legacy systems will learn three practical techniques for incremental cloud migration, drawn from our 18-month project that reduced downtime by 70%.'

The speaker bio should be brief and relevant. Instead of listing every job you have ever had, focus on the experience that directly relates to the talk. 'Jane Doe is the CTO at ExampleCorp, where she led the migration of 500 servers to Kubernetes. She has spoken about DevOps at three industry events.'

Always follow the submission form's instructions exactly. If they ask for a 100-word bio, do not send 200 words. If they require three learning objectives, provide three. Ignoring guidelines is the fastest way to get rejected.

You will submit to many conferences. You need a system to track them, or you will forget what you sent where. A simple spreadsheet works. Columns should include Conference Name, Submission URL, Date Submitted, Proposal Title, Decision Deadline, Status, and Notes.

Statuses might be Submitted, Under Review, Accepted, Rejected, or Withdrawn. Notes can record details like 'follow up two weeks before decision date if no reply' or 'travel not covered, budget required'.

Most conferences will email a confirmation upon submission. If you do not receive one within 24 hours, check your spam folder, then consider submitting again or contacting the organiser to confirm receipt. A missing confirmation can mean your proposal was never received.

If the conference publishes a decision date, note it in your tracker. Do not email before that date asking for a status update. If the date passes with no communication, a single polite follow-up email is acceptable. Ask if decisions have been made and reiterate your enthusiasm. If there is still no reply after a week, mark it as a silent rejection and move on.

A realistic response rate for cold submissions is low, especially for large, well-known conferences. For a newcomer, 5 to 10 acceptances per 100 submissions is a plausible range. This improves as you build a speaking portfolio and get referrals.

If you submit many proposals and receive only rejections or silence, diagnose the problem systematically. The issue is usually in the proposal, the target selection, or both.

First, review your abstracts. Are they selling a product or service? Conference organisers reject sales pitches. Are they too theoretical without practical takeaways? Rewrite them to focus on actionable advice. Ask a colleague in your field to read them and tell you what the attendee would actually learn.

Second, re-examine your target events. Are you applying only to the largest, most competitive conferences? Start smaller. Local meetups, niche workshops, and company-internal conferences are easier to break into and build credibility.

Third, consider your topic. Is it oversubscribed? Ten other people may be proposing a talk on 'Introduction to AI'. Find a more specific angle based on a recent project or a less common technology.

Fourth, improve your visible credibility. A speaker bio with no past speaking experience can be a hurdle. Consider writing detailed blog posts on your topic first, then cite them in your bio as 'published work'. Offer to give a free talk to a relevant online community or podcast to get a recording for your portfolio.

This process is manual and time-consuming. Some tools can help with the discovery step. For example, Mentionry scans sources like confs.tech and PaperCall for speaking opportunities relevant to a business's domain. It presents each find as a row with the conference name, date, and a link to the CFP page, but it cannot tell you if the deadline has passed. You still must visit the site, judge the fit, and write the proposal yourself. The tool only finds the page, it does not apply.

Getting accepted is the beginning of the work. Your first communication with the organiser should confirm logistics. Ask about the schedule slot length, audience size and background, available audio-visual equipment, and rehearsal times.

Start preparing your talk immediately. A good rule is to spend one hour of preparation for every minute of speaking time. A 30-minute talk deserves 30 hours of work: outlining, drafting slides, writing notes, and practicing.

Practice the talk out loud, multiple times. Time yourself. Record a video and watch it to see your pacing and body language. Get feedback from a trusted peer. Remove any content that does not directly serve the key learning objectives you promised in your abstract.

Confirm travel and accommodation arrangements well in advance. If the event is covering costs, get the reimbursement policy in writing. Keep all receipts.

After the event, send a thank-you email to the organiser and the attendees who provided feedback. Update your speaker bio and portfolio with the recording or slides from the talk. This becomes material for your next round of submissions, making each application slightly easier than the last.