|
| 1 | +--- |
| 2 | +date: "2026-10-06" |
| 3 | +title: "The TokioConf 2027 Call For Talk Proposals is now open" |
| 4 | +description: "October 6, 2026" |
| 5 | +--- |
| 6 | + |
| 7 | +We are excited to announce that the Call for Speakers for TokioConf 2027 is |
| 8 | +officially open! |
| 9 | + |
| 10 | +[Submit a talk proposal here][sessionize]. |
| 11 | + |
| 12 | +TokioConf 2027 is happening next April in Portland, OR. |
| 13 | + |
| 14 | +Where: **The Armory, Portland, Oregon**<br/> |
| 15 | +When: **April 26–27, 2027**<br/> |
| 16 | +Website: **[tokioconf.com]** |
| 17 | + |
| 18 | +We had a great inaugural conference this year (you can watch the recordings |
| 19 | +[here][videos]) and are gearing up to do it again! Similar to last year, the |
| 20 | +conference will focus on the practical side of building with Rust. We are |
| 21 | +looking for talks across all technical levels covering: |
| 22 | + |
| 23 | +<ins>Building with Rust:</ins><br> |
| 24 | +Lessons from real-world experience using Rust & Tokio to build and ship |
| 25 | +products. Rust can be a good fit for web, robotics, AI, infrastructure, mobile, |
| 26 | +connected devices, real-time collaboration, and more. Share how using Rust |
| 27 | +helped deliver higher-quality software. |
| 28 | + |
| 29 | +<ins>Design and Architecture:</ins><br> |
| 30 | +How do you structure code to make it easy to understand, extend, and maintain? How |
| 31 | +have you evolved new patterns as you adopt AI tools? |
| 32 | + |
| 33 | +<ins>Testing and Verification:</ins><br> |
| 34 | +How can we use integration testing, property-based testing, fuzzing, [simulation][turmoil], |
| 35 | +[model checking][loom], formal verification, and AI reviews to maintain the highest |
| 36 | +quality standards? |
| 37 | + |
| 38 | +<ins>Performance:</ins><br> |
| 39 | +We all like fast software. Share the tricks and tips you’ve learned to speed |
| 40 | +things up, reduce memory, or improve quality. |
| 41 | + |
| 42 | +<ins>AI with Rust:</ins><br> |
| 43 | +What role does Rust play in AI applications? How is AI changing Rust |
| 44 | +development? Topics include agents, inference, on-device models, integrating AI |
| 45 | +into applications, and using AI to write Rust code while maintaining high |
| 46 | +standards. |
| 47 | + |
| 48 | +<ins>Cool stuff:</ins><br> |
| 49 | +Let’s nerd out. Show us something interesting and fun you made with Rust. |
| 50 | +Anything goes. There does not need to be any practical application; just did it |
| 51 | +for fun. Side projects, unfinished experiments, and ideas that didn’t work out |
| 52 | +are all welcome too. |
| 53 | + |
| 54 | +This year, we are asking for submissions on how you all are using AI to increase |
| 55 | +productivity **and** the reliability of the software you ship. The fact is, at |
| 56 | +this point, AI agents are writing most new production code. This will bring new |
| 57 | +questions and challenges that we all need to address. Please submit talks to |
| 58 | +share your experience leveraging these new tools and capabilities. |
| 59 | + |
| 60 | +## How to Submit |
| 61 | + |
| 62 | +Have something the community should hear about? We’re accepting submissions |
| 63 | +through November 30, 2026, 11:59 PM Pacific. Submit your proposal at |
| 64 | +[https://sessionize.com/tokioconf-2027][sessionize]. |
| 65 | + |
| 66 | +If you have any questions, please email us at [hello@tokioconf.com]. You can |
| 67 | +also ping us on [Discord] in the #tokioconf channel. |
| 68 | + |
| 69 | +<div style="text-align:right">— the Tokio team</div> |
| 70 | + |
| 71 | +[videos]: https://tokio.rs/blog/2026-05-29-tokioconf-2026-videos |
| 72 | +[sessionize]: https://sessionize.com/tokioconf-2027 |
| 73 | +[Discord]: https://discord.gg/tokio |
| 74 | +[tokioconf.com]: https://tokioconf.com |
| 75 | +[hello@tokioconf.com]: mailto:hello@tokioconf.com |
| 76 | +[turmoil]: https://github.com/tokio-rs/turmoil |
| 77 | +[loom]: https://github.com/tokio-rs/loom |
0 commit comments