Call for speakers
11:59pm 06/06/2016 PDT.
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 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?
A few ideas are 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 PDT June 6, 2016.
New architectural styles
- Reactive and its variants
- Microservices, pros and cons
Effective techniques for existing architectures
- Single-page web applications
- Distributed systems
- Integration 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
You’ll be asked to include the following information for your proposal:
- Proposed title
- Overview and extended descriptions of the presentation: main idea, subtopics, conclusion
- Suggested track
- Speaker(s): expertise, summary biography, and hi-res (1400px min width) headshot
- Prerequisite knowledge and/or requirements needed by attendees
- Reimbursement needs for travel or other conference-related expenses (if you are self-employed, for example)
- Video (strongly encouraged)
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 a 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.
Some tips for writing a good proposal for a good talk:
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 presentations and supporting materials must be respectful, inclusive, and adhere to our Code of Conduct.
- 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. Clever or inappropriate titles make it harder to figure out what you’re really talking about.
- Include as much detail about the presentation as possible. Longer talks should provide more details.
- 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. 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.
- Context is important. If your talk is about something truly ground-breaking, it’ll be helpful if you describe it in terms of things that attendees might already know of.
- Limit the scope: in 50 or 90 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 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. If you speak at a lot of events, be sure to note why this presentation 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.
- Indicate in your proposal notes whether you can give all the talks you submitted.
- 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.
- We welcome sessions for attendees with a variety of skill levels. Indicate the experience and knowledge level of the audience that you are targeting: novice, intermediate, or expert.
Other resources to help write your proposals:
- Call for Participation closes: June 6, 2016
- Proposers notified: By June 2016
- Registration opens: June 2016
Code of Conduct
We expect all participants, including speakers, to 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