Building a Better Web
June 19–20, 2017: Training
June 20–22, 2017: Tutorials & Conference
San Jose, CA

Call for Speakers

Call closed 11:59pm 01/11/2017 PST.

Speak at O’Reilly Fluent 2017

O’Reilly Fluent is an annual conference dedicated to sharing knowledge on web technologies and showcasing how these technologies are transforming our industry. Do you have expertise and experiences to share in frontend, design, backend, performance, or security? We encourage you to send us a proposal to speak at Fluent 2017!

We’re interested in what it takes to build great projects for the web. The topics below are guidelines and suggestions—but we love to be surprised. You can also take a look at our program committee to get a sense of the people and projects that intrigue and inspire us.

See our tips for submitting a successful proposal. The deadline for submissions is 11:59pm PST on January 11, 2017.

Remember, what’s old to you may be new to someone else. While we do want the latest and greatest research and techniques, powerful explanations and stories about how to make the web work better will appeal to a broad audience.

New to the speaking circuit? We want to hear from you! We’re actively seeking new voices and off-the-beaten-path topics. Any ideas, best practices, challenges, etc. that you’ve encountered and conquered are fair game. If it’s important to you, chances are it’s important to others as well.

Core web platform technologies

Web platform foundations

  • JavaScript/ES6
  • HTML5
  • CSS3

Frontend frameworks and libraries

  • JavaScript frameworks and libraries (Angular, React, Ember, Vue, etc.)
  • UI frameworks and libraries
  • Case studies and comparisons

Fullstack development

  • Node.js
  • Backend tools (Rails, Python, PHP)
  • Maintaining sites and applications

Tools to help build the modern web

Cross-platform and mobile

  • Native and hybrid mobile apps
  • Progressive web apps
  • Desktop apps

Web services and APIs

  • RESTful web
  • Microservices
  • Tools

Frontend tools

  • Browser tools
  • Dependency management
  • Build and automation
  • Testing

People and teams

  • Collaboration tools
  • Engineering culture
  • Building great teams

Building performant and resilient apps and sites

Performance matters

  • Monitoring, measurement, and metrics
  • UX optimization
  • Designing for performance
  • Scalability
  • Automation
  • Data science and analytics
  • HTTP/2
  • Performance culture
  • Third parties
  • Mobile

Modern web essentials

  • Security
  • Accessibility
  • Responsive web design
  • Privacy

The expanding web

Future JS & functional

  • Future of JavaScript (ES7, ES8, WebAssembly, etc.)
  • Functional Programming (Elm, ClojureScript, Erlang)

The web everywhere

  • Hardware and the web
  • Smarter web (AI, Bots, Virtual Reality, Gaming)
  • Monetization of the web

The deadline for proposals is 11:59pm PST on January 11, 2017.

Required information

You’ll be asked to include the following information for your proposal:

  • Proposed title
  • Description of the presentation
  • Suggested main topic
  • Audience information
    • Who is the presentation is for?
    • What will they be able to take away?
    • What prerequisite knowledge do they need
  • Is this a session (40 minutes) or a tutorial (3 hours)?
  • For tutorial proposals: hardware installation, materials, and/or downloads attendees will need in advance
  • Speaker(s): biography and hi-res headshot (minimum 1400 pixels wide; required)
  • A video of the speaker
  • Reimbursement needs for travel or other conference-related expenses (if you are self-employed, for example)

Proposals will be considered for the following types of presentations:

  • 40-minute sessions
  • 3-hour tutorials

Starting in 2017, 40-minute sessions will be the core of the conference. Because past attendees have asked for more interactivity, we’ve expanded session times so that you can discuss your topic at a deeper level. We’re looking for rich, focused talks that make the most of each 40 minutes.

Tips for submitting a successful proposal

Help us understand why your presentation is the right one for O’Reilly Fluent. Please keep in mind that this event is by and for professionals. All presentations and supporting materials must be respectful, inclusive, and adhere to our Code of Conduct.

  • Be authentic! Your peers need original session ideas that focus on real-world scenarios, relevant examples, and knowledge transfer.
  • Give your proposal a simple and straightforward title. Clever or inappropriate titles make it harder for people to figure out what you’re really talking about.
  • Include as much detail about the planned session as possible. The longer the talk you’re proposing, the more detail you should provide.
  • If you are proposing a panel, tell us who else would be on it.
  • Keep proposals free of marketing and sales.
  • If you are not the speaker, provide the contact information of the person you’re suggesting. We tend to ignore proposals submitted by PR agencies unless we can reach the suggested participant directly. To improve the proposal’s chances of being accepted, work closely with the presenter(s) to write a jargon-free proposal that contains clear value for attendees.
  • Keep the audience in mind; they’re professional and already pretty smart.
  • Context is important. If your session is about something truly ground-breaking, it will be helpful to the reviewers if you describe it in terms that attendees might already be familiar with.
  • Limit the scope of the talk; in 40 minutes, you won’t be able to cover Everything about Framework X. Instead, pick a useful aspect, or a particular technique, or walk through a simple program.
  • Explain why people will want to attend. Is your topic gaining traction? Is it critical to modern business? Will attendees learn how to use it, program it, or just what it is?
  • Repeated talks from the conference circuit are less likely to be appealing. The conference has a limited number of slots. If attendees can see the same talk somewhere else, why should they come see you at this one? If you speak at a lot of events, be sure to note why this session is different.
  • Don’t assume that your company’s name buys you credibility. If you’re talking about something important that you have specific knowledge of because of what your company does, spell that out in the description.
  • If you submit more than one proposal, let us know in your proposal notes whether you can give all the talks you submitted proposals for.
  • Does your session have the participation of a woman, person of color, or member of another group often underrepresented at tech conferences? Diversity is one of the factors we seriously consider when reviewing proposals, as we seek to broaden our speaker roster.
  • We welcome sessions for attendees with a variety of skill levels. Consider proposing a number of different skill-level sessions, and please indicate the experience and knowledge level of the audience that you are targeting: non-technical, beginner, intermediate, or expert.

Other resources to help write your proposals

Important dates:

  • Call for Participation closes: January 11
  • All proposers notified: By February 2017
  • Registration opens: February 2017

Code of conduct

All participants, including speakers, must follow our Code of Conduct, the core of which is this: an O’Reilly conference should be a safe and productive environment for everyone. Read more »

Create a proposal