Your next conference talk is hiding in your everyday web development work
Your next conference talk is hiding in your everyday web development work
The page that felt fast on your laptop but struggled on someone else’s phone. The component that looked finished until you tried navigating it with a keyboard. The API integration that sent you and another team searching for the same bug.
You probably didn’t think “conference talk” while working through these problems. You were trying to understand what was happening and ship something that worked.
But the investigation, decisions and lessons behind that work could be useful to someone facing a similar challenge.
If you have considered speaking at a web development conference but wondered what you could contribute, start with a problem you remember solving.
Revisit the task that surprised you
Look back at a task that took an unexpected turn.
Perhaps a small interface change exposed a problem with your application’s state management. A third-party script affected page performance. Or a deployment worked perfectly in one environment and failed in another.
What did you expect to happen? What happened instead? How did you work out the difference?
Those questions help uncover a story that another developer can follow. They also give you something concrete to explain, including the clues you missed and the tools that helped.
The final fix might have been small. Understanding why it worked is where your experience becomes valuable.
Your decisions give the topic depth
You don’t need to have built a new JavaScript framework to share a useful perspective on web development.
Think about the choices behind your work. Why did you introduce server-side rendering? How did you decide which parts of a design system to standardise? What convinced your team to change an API contract or simplify a build pipeline?
Explain the options you considered and the constraints you faced. A small team maintaining an existing product may make different choices from a team starting a new application.
That context helps attendees understand your reasoning and judge what applies to their own projects.
Look at where different disciplines meet
Some useful talk ideas emerge at the boundaries between responsibilities.
A frontend developer may discover that an interface needs information the API doesn’t provide. An accessibility review may reveal assumptions shared by design and development. A performance investigation may involve browser behaviour, network requests and backend processing.
If you worked through one of these situations, explain how the pieces connected. What did each person or team need to understand? Which change helped you move forward?
Your talk could explore a technical solution, a way of collaborating or both. Be specific about what changed and how you assessed the result.
Find a focused web development conference talk idea
Broad topics become easier to develop when you narrow them to a practical question. For example:
- Web performance: How did you investigate a page that felt slow on users’ devices?
- Accessibility: What did you learn when testing a custom component with keyboard navigation?
- Frontend architecture: How did you simplify state management in one complicated feature?
- APIs: How did frontend and backend teams agree on a contract they could test?
- Testing: How did you investigate and reduce flaky browser tests?
- Developer tooling: Which changes made your team’s local setup easier to use?
Choose an experience you can support with examples. Show what you tried, what you observed and what you would approach differently next time.
Check what you can share publicly, and use simplified examples where project details need to remain private.
How to submit a conference talk
Once you have a topic, describe the intended audience and the problem your session will help them understand.
Then complete this sentence:
“After this session, web developers will be able to…”
Use that answer to shape your abstract. Explain the scope, the approach you will explore and the practical takeaways. Make any required knowledge clear so attendees know what to expect.
Ask a colleague who wasn’t involved in the work to read your proposal. Can they explain what they would learn? Their questions can help you identify missing context or narrow the topic further.
You don’t have to cover an entire discipline. Give yourself room to explain one problem well.
Bring your experience to Webdevcon 2027
At Webdevcon, we welcome practical insights into building for the web, including frontend and backend development, APIs, architecture, development tooling and the skills that help teams work together.
Whether you are considering your first submission or preparing a new talk, take another look at the work you have already done.
What challenged your assumptions? What became clearer along the way? What would you explain to another developer about to face the same problem?
The Webdevcon 2027 Call for Papers closes on 18 December 2026. All talks are presented in English.
Read the submission guidelines and submit your talk.
