Talk submission guide
If you’ve never submitted a talk proposal before, the process can seem confusing, even a bit daunting. This guide is here to help.
At NZ Tech Rally, we want to make our talk submission process as transparent and supportive as possible. This guide walks you through exactly what we’re looking for in a great talk proposal, and hopefully helps take the pressure off along the way.
A quick note: this advice is specific to our event and our selection process. While some tips may apply elsewhere, every conference has its own criteria and quirks, so always check the details.
Let’s walk through our talk submission form, question by question.
Talk title
Keep it short, clear, and compelling. Your title should give people a strong sense of what your talk is about and hint at the tone or energy behind it.
Imagine attendees only see your title when deciding which session to go to. Would they understand what it's about? Would they choose your talk over four others running at the same time?
Avoid long or vague titles. In a multi-track format, shorter titles are easier to scan and more likely to grab attention.
Tip: It’s often easier to write your title after you’ve written your talk description.
Example:
Accessible by default: How to get there, and make it last
What is your talk about?
Give us a clear overview of your talk in 100 words or fewer. Focus on what the talk will cover, the story or idea you’re exploring, and the core message you want to share. It helps us understand the substance of your talk and where it best fits in the programme.
Keep it straightforward and focused. No need for polish, just help us see what your talk is really about.
This section is only for the selection committee and won’t be published.
Example:
After burning out early in my career, I started looking at how we reward “always on” behaviour in tech teams. This talk explores how burnout shows up in high-performing teams, why we miss the warning signs, and what team leads can do to build healthier, more sustainable cultures.
Elevator pitch
This is your talk’s teaser — brief, punchy, and engaging. Think of it like a movie trailer: what’s the premise, what kind of experience should attendees expect (story-driven, practical, inspiring), and why should they care?
This will appear on the website if you talk is selected. So no more than 75 words. Avoid technical jargon or too much setup. The goal is to help attendees quickly decide if this talk is for them.
Example:
Your team has been told to make your web app accessible in 12 months.
Starting tomorrow!
You’re vaguely aware of tabbing through the app, but surely there’s more to it?
This is a practical guide to becoming an accessible digital product team.
Spoiler: It’s a cultural shift.
How will you structure your talk?
Tell us roughly how you plan to organise your talk from start to finish. This helps us understand the flow, pacing, and how your ideas will unfold for the audience.
You don’t need to give a minute-by-minute breakdown, just a simple outline of your structure is enough. It helps us determine the right time slot and format for your talk.
This section is only for the selection committee and won’t be published.
Example:
Personal story → Key insight → Case study → Lessons learned → Practical takeaways
Who is this talk for, and what will attendees take away?
When we review submissions, we think first and foremost about our attendees.
If someone gives you 25 minutes of their time, what will they walk away with?
That’s why we tend to avoid talks that feel self-promotional or read like a company pitch. We’re looking for talks that share useful insights, experiences, and learnings that others can apply or reflect on.
Personal stories are welcome, especially when they’re used to highlight lessons, frameworks, or ideas that others can learn from. A story for story’s sake, without broader relevance, is less likely to be selected.
Help us understand:
Who is this talk for? Be specific — junior devs, team leads, designers, product managers, etc.
What will they get out of it? What might they learn, feel, reflect on, or do differently after?
A strong submission includes 3–5 bullet points outlining what your audience will take away. It shows that you’ve thought deeply about the value of your talk and who it’s for.
This section is only for the selection committee and won’t be published.
Why is this talk a good fit for NZ Tech Rally 2026?
This is an optional question, so please feel free to skip if you are not keen for a keynote slot.
Take a moment to reflect on how your talk connects to our 2026 conference theme:
Our tech, our way: shaping Aotearoa’s tech culture.
The best submissions are those that feel grounded in the local context and offer insight into how we shape tech and tech culture in Aotearoa, in our own unique way.
While any talk can be selected as a keynote, those most aligned with the theme are strong contenders. On the flip side, many unsuccessful submissions don’t show enough relevance to the theme, so this is your chance to make that connection clear.
Tell us:
What makes this talk especially relevant for this event, this theme, and this moment in Aotearoa’s tech story?
It doesn’t have to be long, but it does have to be thoughtful.
This section is only for the selection committee and won’t be published.
Do you have a track in mind for your talk?
We have five tracks for our 2026 conference:
Engineering & Platforms
Product, UX & Design
Testing & Quality
AI, Data & Ethics
Community, Culture & Wellbeing
If your talk fits clearly into one or more of these, select the checkboxes. It helps us with scheduling and balance across the day.
Keynote talks may or may not fall within these tracks, so don’t worry if yours feels broader.
Not sure where your talk fits? No problem — just leave it blank and we’ll figure it out.
Why do you want to speak at NZ Tech Rally?
We’d love to know what’s motivating you to speak at this event.
Maybe you want to share a hard-won lesson, tell a story you haven’t seen represented before, or give back to the tech community in Aotearoa New Zealand. Whatever it is, we’re keen to hear it.
There’s no right or wrong answer. It just helps us understand your “why”.
This section is only for the selection committee and won’t be published.
Are you ok with this talk being recorded?
We do our best to record all talks. We then post our talk recordings on our YouTube channel, so they can be shared with a wider audience beyond the conference. It’s a way to showcase your work and reach people who can’t attend in person.
However, we understand that not everyone or every employer is comfortable with this, especially if your talk includes work done at your organisation. That’s why we ask upfront: to avoid surprises or delays later in the process.
If you prefer not to be recorded, that’s completely fine. Your submission will still be considered equally.
Tip: If you’re unsure, it’s a good idea to check with your reporting line manager before submitting your talk.