All proposals must be submitted by 11:59 pm EST, 25 June 2021.
There's tons of useful information that will help to shape your proposal. Browse through these details before submitting the form.
Before you volunteer yourself, consider whether anyone in your network from an underrepresented group would be a great fit for this conference. If you'd like to nominate a speaker, contact us and we'll encourage them to submit a proposal.
All proposals must be submitted by 11:59 pm Eastern Time, 25 June 2021
We expect all Sponsors (with speaking spots) to complete the submission process in full, following all instructions. Through the Call for Proposals process, you’ll work with the team to shape your session and collect all details for promotion.
As part of your proposal, we'll ask you to prepare the following:
• A session title
• A description
• A 2-5 minute video where we ask you to pitch your session
There's also a number of other questions we collect as part of the process, you can check out the full form here.
The video component is the most distinctive part of our process. In this video we want you to tell us the main idea behind your session, and what audience members will learn.
We recommend using Loom for this – feel free to share your screen if you want to use a doc or slides to run through your session at a high level. If you haven't used Loom before, check out this helpful article.
Multiple members of your team are welcome to submit the CFP. Due to the limited space in the agenda, we will only be able to accept one session per company at first. We will work with your team to figure out:
• which session you will move forward with
• how to bring other teammates into the session
If the opportunity arises for a member of your team to present another session, we’ll let you know. If not, we’ll chat about potentially presenting this content at other events such as meetups or how-to hours.
Since this is an online event, a pitch video is a great proxy for your eventual session and helps us assess proposals reliably. We included this as part of our process last year and found it really effective.
The best way to assess this is to consider whether your content is relevant for our attendees. Here's how we're thinking about the different types of attendees, and what they want to take away from Coalesce:
• The Committed End User: These are the people that are using dbt every day and are fully bought into the analytics engineering mindset. They want to learn how to be an even more impactful data professional — what projects they can work on next, how data works at other organizations, or what skills they can add to their repertoire (including adjacent skills such as blogging or interviewing)
• The Skeptical End User: This person is dipping their toes into the world of dbt. They likely use other parts of the modern data stack every day but aren't yet bought into the dbt viewpoint. They want to know the value of using dbt.
• The Team Lead: This person runs a data team, has an ear for the C-Suite, and runs a budget. They want to know how to make their team more impactful, and where the industry is heading next.
• The Decision Maker: CIOs, CTOs, CPOs, thought-leaders, c-suite professionals thinking about making more money and biz outcomes. This person is ultimately on the hook for the success/failure of tech adoption. They are responsible for making decisions that are good for the business today & 5-10 years from now.
We are also open to a number of different formats for sessions this year! Here are some of the session types we're thinking about:
• Keynotes: Forward-looking talks establishing an underlying theme, delivering a core message, and setting the tone of the conference.
• Panels: Conversations diving into a relevant data topic led by a variety of community voices/perspectives. Typically one hour long.
• Community talks: Talks focused on how to solve a business problem with analytics engineering
• Workshops: Demos/tutorials/walkthroughs of tools and techniques — see features, functionality, etc. in action
• Other: We're open to your format ideas too!
If you're searching for extra inspiration, all of our sessions from last year's conference are available on our YouTube channel.
First and foremost, have a specific problem or closely related set of problems in mind. You should investigate or even propose a solution to these problems in a way that confers value to the audience. You should be able to tell us about a problem, propose a solution or new way of viewing the problem, and then explain concretely how you will argue for your ideas. Everything from a deeply technical talk on snapshots to a diversity-empowered data team talk is welcome at Coalesce.
Generally speaking, successful proposals come from folks who have already come up with a problem and a solution, with a narrative roadmap from start to finish. That said, be empowered to get creative with your narrative format. How you choose to tell the story is up to you! Don't get hung up on needing to be a superstar speaker—we'll work with you on delivery. Being a strong presenter who brings enthusiasm to their talk is a plus, but given the choice between great ideas and great entertainment, we'll take the former.
The talk proposal you submit should demonstrate ample forethought. The more concrete you can be, the more chance your talk will make an impression on us (and audiences at Coalesce!).
Finally, last year we shared a blog post that highlighted themes from some of the best proposals we received.
We'll review each proposal based on the strength of the proposal, topic fit for Coalesce, and strength of the speaker.
Once we've identified the best proposals, we then work them into an agenda, where we consider:
• What timezone is the speaker based in? Can we fit them in on the day that best matches their timezone?
• Does each day have content that's relevant to different attendees and a variety of formats?
• Are our lead talks at a time of day that reaches the most attendees?
• Do the topics on the agenda feel repetitive?
• Are we missing out on an important topic area?
• As a result, there may be some time between submitting your proposal and hearing back from us.
Last year, we had over 100 proposals, and we expect even more this year. As a result, we are unable to provide individual feedback on unsuccessful proposals. Last year we wrote a roundup of what we learned — if we notice common themes in proposals again this year, we'll write another post with our updated lessons!
Yes, we welcome and encourage first-time speakers! You may notice that our application process doesn't ask for any information about previous speaking experience, as we don't want to filter first-time speakers out of the process. If selected, we'll work with you to make sure your talk is the best it can be.
Yes! We're looking for talks that are relevant to members of the dbt Community — in most cases these talks will come from teams that are using dbt. However, so long as your data team has a viewpoint that's compatible with ours, and you're familiar with the modern data stack, you'll likely have things to say that are relevant to the community. Last year we had a number of talks in this category: talks on how to write about your work, hiring, assessing offers, structuring data teams, and more.
As a speaker, we expect that you meet all required due dates, in particular:
• June 25: Call for Proposals due
• July 9: Speaker confirmation form due
• July 30: Presentation outline due
• August 31: First draft of presentation due
• September: Attend presentation test run and feedback session
• October 22: Second draft of presentation due for design review
• November 22: Final presentations submitted
• December 6-10: Present!
We also want you to:
• Be open to feedback from our team at any stage — we're more hands-on than most conference organizers. We want you to give the best presentation possible, and will always give feedback that we feel is in your best interest!
• Be open to working with us on turning your presentation into a blog post on the dbt blog, or a Discourse article. We might be able to lend some resources for ghost-writing, but we'll also need your input on a final version.
Representation matters. As such, we have the following goals for our speaker lineup:
• At least 50% of speakers are non-cis-men
• At least 40% of speakers are non-white
In order for us to reach these goals, our team will:
• proactively reach out to individuals within our networks to build a diverse set of CfP respondents
• align on talk selection criteria ahead of reviewing proposals to reduce bias
• ensure we have a diverse group of individuals reviewing proposals
• increase access to feedback for individuals from underrepresented groups
Further, all individuals within the dbt Community, including those that attend this event, are required to abide by the dbt Community Code of Conduct. This code promotes inclusivity and prioritizes marginalized people’s safety over privileged people’s comfort.
Got a question we didn't cover here? Please let us know at email@example.com so we can add it!