RailsConf 2025 planning is in full swing! With our program committee selected, a theme decided on, and preparations underway, we’re working hard to make the final RailsConf an unforgettable experience. But the heart of any great conference isn’t just the organizers—it’s you, the Ruby and Rails community.

That’s why the Call for Proposals (CFP) is so important. It’s a chance for community members to share fresh ideas, showcase their expertise, and contribute to the conversations shaping the future of Ruby and Rails. Talks at RailsConf and RubyConf reach hundreds—if not thousands—of engaged developers, both in person and through recorded sessions.

Speaking at a conference can feel like a big step, but it shouldn’t be intimidating. Whether you’re a first-time speaker or a seasoned presenter, this guide will walk you through crafting a compelling CFP submission that stands out to the program committee and that will resonate with attendees.

This guide includes takeaways from our CFP coaching sessions, led by previous speakers including Sage Griffin, Brandon Weaver, Joël Quenneville, Noel Rappin, Jade Dickinson, Mayra Lucia Navarro, Aji Slater, and Kevin Murphy.  

REMINDER: The deadline for RailsConf 2025 CFPs is February 28th. Don't miss out! Apply now.

Understanding the Review Process

One of the most important things to know is that the review process is mostly anonymous in the initial stages. This means:

  • Your name, profile image, and personal details are hidden from reviewers to keep things unbiased.
  • Avoid self-identifying details in your talk description, like your company name or a well-known project you've led.
  • Your speaker biography won’t be reviewed during selection but will be public-facing once accepted—so make it engaging!
  • If you want to change something after your proposal is accepted, don’t worry—you’ll have the chance to refine your title and description before the event.

Structuring Your Proposal in Sessionize

Each CFP submission has the following fields:

1. Title

  • Remember to keep it concise and engaging.
  • Make it clear what attendees will learn.

2. Description (Abstract)

The description is your public pitch—it should clearly explain what your talk is about and hook the audience and the program committee.

"If someone is in the hall at the conference and they look at the description, and then somebody else shouts, ‘Hey, what's that talk about?’ that person should be able to answer in a sentence after having read it." - Aji Slater

  • Start with a problem. What challenge does your talk address?
  • Explain the solution. How does your talk help solve the problem?
  • Highlight key takeaways. What will attendees walk away knowing?
  • Keep it easy to summarize—if someone read your abstract in the hallway, could they explain it in a sentence?

"By far, the biggest thing I'm always looking for [when reviewing proposals] is thought given to the audience takeaway." – Sage Griffin

3. Additional Notes (For Reviewers Only)

  • Explain why you’re the best person to present this talk.
  • Include a loose outline of what you plan to cover.
  • Provide extra details that wouldn’t fit in the abstract but will help reviewers understand your approach.

How to Craft a Strong Proposal

Know Your Audience

It’s crucial to define who your talk is for and their level.

"One of the big mistakes people make is saying their talk is for everyone. Be specific—are you speaking to beginners, intermediates, or advanced engineers?" – Brandon Weaver

  • Beginner: Newcomers to Ruby, juniors, or those exploring a topic for the first time.
  • Intermediate: Team leads, senior developers, or those with prior experience.
  • Advanced: Experienced Rubyists, framework/library authors, or engineers focused on performance.

Create a Compelling Abstract

  • Hook the reader early with a problem statement.
  • Tell a story—engage your audience and make them care.
  • Keep your focus clear so the committee and attendees know exactly what to expect.

"What is the problem you're trying to solve? [The structure of your abstract should] start with a problem (i.e., here's the thing that's going to be annoying for you) and then how you’re going to make the audience’s life better." – Joël Quenneville

Consider Your Positioning

  • What’s trending in the Ruby community? Look at past talks, what’s being talked about on social media and in forums, and, of course, the theme for this conference. 
  • Check talk descriptions from previous conferences—this can provide clues on what the organizers might want.

Common Mistakes to Avoid

  • Don't submit a vague or generic talk.
  • Don’t focus too much on what you will cover—instead, lean into why people should care.
  • Don’t write an abstract that’s too long or hard to skim.
  • Don’t forget to speak to your intended audience—clarity is key.

And if you’re on the fence, apply anyway! Don’t talk yourself out of submitting.

"If speaking at RailsConf [or another Ruby Central event] has ever been a goal for you, now is the time to do it!" – Kevin Murphy

Helpful Resources

Best of luck—we can’t wait to review your proposals!