{"id":647268,"date":"2025-10-08T17:26:27","date_gmt":"2025-10-08T16:26:27","guid":{"rendered":"https:\/\/blog.jetbrains.com\/?post_type=kotlin&p=647268"},"modified":"2025-10-17T10:40:43","modified_gmt":"2025-10-17T09:40:43","slug":"crafting-your-kotlinconf-proposal-expert-tips","status":"publish","type":"kotlin","link":"https:\/\/blog.jetbrains.com\/ja\/kotlin\/2025\/10\/crafting-your-kotlinconf-proposal-expert-tips","title":{"rendered":"Crafting Your KotlinConf Proposal: Expert Tips to\u00a0 Help You Stand Out"},"content":{"rendered":"\n

Thinking about sharing your Kotlin expertise on the big stage? KotlinConf<\/a> is the premier event for all things Kotlin, and getting a talk accepted for inclusion in the conference is a fantastic way to contribute to the community and elevate your profile. However, submitting a talk proposal, especially for the first time, can feel daunting. With so many brilliant minds around, how do you give your proposal the best shot at being accepted?<\/p>\n\n\n\n

In this post, we\u2019ll share some ways to make your submission stand out, combining best practices for conference proposals with insider advice from JetBrains speakers, KotlinConf program committee members, and experienced presenters.<\/p>\n\n\n\n

The tips are tailored to KotlinConf in particular, but most of these ideas are applicable to any developer conference.<\/p>\n\n\n\n

1. Make sure your title is clear and compelling<\/h2>\n\n\n\n

You never get a second chance to make a first impression, and your talk\u2019s title is your earliest opportunity to capture attention. Reviewers and attendees alike may decide whether to read further based solely on those first few words.<\/p>\n\n\n

\n
\n
\n
\n \"\"\n <\/div>\n
\n

Pamela Hill. Developer Advocate, KotlinConf Program Committee member, KotlinConf speaker<\/h4>\n

X<\/a>, Bluesky<\/a>, LinkedIn<\/a><\/p>\n

A carefully-selected title can make all the difference! Audience members often lack the time or attention span to read more than the title when deciding whether to attend a talk. Prefer clarity over a catchy or fun title that doesn\u2019t give a good idea of what the talk is about in a nutshell.<\/span><\/i><\/p>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n\n\n

Choose a title that communicates your topic in plain terms, hints at the level, and makes the benefit to the audience obvious.<\/p>\n\n\n\n

\n

Your Voice Belongs Here: Creating Compelling KotlinConf Proposals<\/em><\/a><\/i> is a supportive and practical livestream for people from underrepresented groups in tech \u2013 whether you’re preparing for your first talk or have speaking experience and want to take the next step onto a bigger stage like KotlinConf. Join Pamela Hill and Cheuk Ting Ho, seasoned speakers, CFP writers, and friendly program committee members, as they share what makes a proposal stand out, how to shape your Kotlin journey into a strong submission, and what reviewers are really looking for. Watch the livestream recording.<\/p>\n<\/div>\n

<\/p>\n\n\n\n

Watch now<\/a><\/p>\n\n\n\n

2. Tell a story with your abstract \u2013 with the audience in mind<\/h2>\n\n\n\n

Crafting a great talk is not just about presenting information \u2013 it\u2019s also about storytelling. Think of your proposal as a promise to provide a valuable learning experience wrapped in a story that makes it engaging.<\/p>\n\n\n

\n
\n
\n
\n \"\"\n <\/div>\n
\n

Sebastian Sellmair. Software Developer, KotlinConf speaker<\/h4>\n

X<\/a>, Bluesky<\/a>, YouTube<\/a><\/p>\n

Talking at KotlinConf is a great experience and a huge achievement for any Kotlin developer. While choosing a great title, having highly polished animations, and curating high-quality memes might enhance your talk, the most important thing is having a story worth telling. Do you have something novel and technically interesting to present? Can you break down a topic in a way that is engaging and truly fun? Can you inspire fellow developers?<\/span><\/i><\/p>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n\n\n

Your abstract should explain what you\u2019ll cover, what the attendees will gain, and why your talk matters. Reviewers don\u2019t need a full script, but they do need a clear, detailed impression of your talk.<\/p>\n\n\n

\n
\n
\n
\n \"\"\n <\/div>\n
\n

M\u00e1rton Braun. Developer Advocate, KotlinConf Program Committee member, KotlinConf speaker<\/h4>\n

X<\/a>, Bluesky<\/a>, LinkedIn<\/a><\/p>\n

While we don\u2019t need a full script for your talk as the abstract, we\u2019re also unlikely to accept a talk where the abstract is just a single sentence. Two or three paragraphs are usually enough to provide meaningful detail.<\/span><\/i><\/p>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n\n\n

Think of your abstract as a preview, not a transcript \u2013 just enough detail to show the value and flow of your talk.<\/p>\n\n\n\n

Submit your session<\/a><\/p>\n\n\n\n

3. Start with the problem and build anticipation<\/h2>\n\n\n\n

When writing your proposal, set the stage by outlining the challenge or pain point your talk addresses. Create curiosity before giving the solution. This builds anticipation and helps the audience connect with your topic.<\/p>\n\n\n

\n
\n
\n
\n \"\"\n <\/div>\n
\n

Jodie Burchell. Developer Advocate and Data Scientist<\/h4>\n

LinkedIn<\/a>, Mastodon<\/a>, Bluesky<\/a><\/p>\n

Hook your audience by telling them the problem you’re going to be solving. People love mystery books for a reason, and that’s because they build up a bit of suspense before they jump into the solution. A great proposal will do the same thing.<\/span><\/i><\/p>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n\n\n

4. Think like an attendee: What’s their takeaway?<\/h2>\n\n\n\n

The best proposals start with the audience. Instead of asking, \u201c<\/em>What do I want to present?\u201d<\/em>, consider what the attendees will learn and why they will find it valuable.<\/p>\n\n\n

\n
\n
\n
\n \"\"\n <\/div>\n
\n

Svetlana Isakova. Team Lead in Kotlin Developer Advocacy, KotlinConf Program Committee member, KotlinConf speaker <\/h4>\n

X<\/a><\/p>\n

When submitting a talk, think like an attendee: Would you want to sit through this? What\u2019s in it for the audience? That\u2019s why we ask about key takeaways. What do you want people to learn, try, do, or feel inspired by?<\/span><\/i><\/p>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n\n\n\n

Be precise with key takeaways. Avoid vague statements like \u201cYou\u2019ll learn best practices.\u201d Instead, be concrete and specific.<\/p>\n\n\n\n

Here are a few examples from KotlinConf 2025 talks:<\/p>\n\n\n\n