Engineering the Future of Software
Feb 25–26, 2018: Training
Feb 26–28, 2018: Tutorials & Conference
New York, NY

Call for Speakers

Call closed 11:59pm 09/12/2017 EDT.

From developer to architect

The software architect’s career path is not well defined in the tech industry. It’s hard to find resources to bridge the gap on the conceptual journey from developer to software architect.

We want to hear about real world experience, including the benefits and pitfalls, of architectural decisions. How do frameworks and other architectural underpinnings perform under the crucible of real-world challenges?

The O’Reilly Software Architecture Conference is one of the few events focusing on leadership and what it takes to be a leader in software architecture design, development, and deployment. We need your help amplifying the importance of this role in an organization and creating a wealth of information to move this discipline forward. What learning path did you take? How can we raise the visibility of our skills and share core concepts to help other developers do better in their roles?

We suggest a few ideas below, but feel free to go beyond them. We’re particularly seeking presentations that include real-world experience, innovative ideas, and/or ideas that challenge outdated dogma. However, all interesting ideas, presented in interesting ways, are welcome.

If you want to submit a great proposal, see our tips on how to submit a proposal. The deadline for submissions is 11:59pm ET on September 12.

New architectural styles

  • Reactive and its variants
  • Microservices architecture
  • Cloud native
  • Serverless

Effective techniques for existing architectures

  • Web
  • Single-page web applications
  • Distributed systems
  • Integration architecture
  • Enterprise architecture
  • Application architecture

Intersection of architecture and…

  • Devops, operations, deployment, Continuous Delivery
  • Security, both internal and external
  • User experience design
  • Caching, load balancing, optimization
  • Scale and performance
  • Business concerns

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 the presentation is for?
    • What will they be able to take away?
    • What prerequisite knowledge do they need?
  • 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 both 50 and 90 minute presentations as well as 3-hour tutorials. Fifty-minute sessions will be interspersed throughout the conference to introduce new concepts, a best practice, a view into the future while 90-minute sessions will dive deeper giving you information, techniques, and workflows you can bring back to work and begin using immediately. And, finally, we are looking for intense 3-hour tutorials that involve hands-on examples, working with other attendees, and frameworks and processes to implement for significant change in your current architecture.

Tips for submitting a successful proposal

Help us understand why your presentation is the right one for Software Architecture. Please keep in mind that this event is by and for professionals. All speakers must adhere to our Code of Conduct. Please be sure that your presentation, including all supporting materials and informal commentary, is welcoming and respectful to all participants, regardless of race, gender, gender identity and expression, age, sexual orientation, disability, physical appearance, national origin, ethnicity, religion, or political affiliation.

  • Pick the right topic for your talk to be sure it gets in front of the right program committee members.
  • Be authentic. Your peers need original ideas in real-world scenarios, relevant examples, and knowledge transfer.
  • Give your proposal a simple and straightforward title.
  • Include as much detail about the presentation as possible.
  • 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 and require that we can reach the suggested participant directly. Improve the proposal’s chances of being accepted by working 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.
  • Limit the scope: in 50 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 and what they’ll take away from it
  • 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.
  • Does your presentation 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.

Other resources to help write your proposals:

Important dates

  • Call for Participation closes on September 12, 2017
  • All proposers notified by October 2017
  • Registration opens in October 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. Please be sure that your presentation, including all supporting materials and informal commentary, is welcoming and respectful to all participants, regardless of race, gender, gender identity and expression, age, sexual orientation, disability, physical appearance, national origin, ethnicity, religion, or political affiliation. Read more »

Create a proposal