📋 Submitting Conference Proposals
0 / 25 completed
1 / 25
A CFP form asks for a "talk title". Which title best practices apply?
Strong CFP titles are specific and outcome-oriented. Include the "who this is for" signal and the core takeaway. Avoid company names (vendor-specific bias), vague titles (no selection signal), and keyword stuffing.
2 / 25
The CFP abstract has a 300-word limit. How should you structure it?
The proven abstract formula: hook → problem → outcomes → credibility. 200–250 words leaves white space and signals editing discipline. The program committee reads hundreds of abstracts — a clear structure makes yours scannable.
3 / 25
The CFP asks "Why are you the right person to give this talk?" How do you answer?
Specificity wins: concrete deployments + measurable scale + relevant prior speaking. "Passionate" signals enthusiasm but not expertise. Years of experience without context is weak. Company positioning reads as vendor marketing.
4 / 25
"The program committee rejected your proposal — the abstract was too broad." Which revision strategy is correct?
"Too broad" means the committee cannot tell what attendees will specifically learn. The fix is narrowing scope and making outcomes concrete and measurable. Removing learning outcomes makes it worse. Adding topics widens scope further. Shortening without restructuring does not fix the problem.
5 / 25
The CFP asks for "target audience". Which answer is most effective?
Precise audience targeting helps the committee slot your talk into the right track and signals that you understand your audience deeply. "Everyone" and "developers" give the committee nothing to work with. The specific version names experience level, existing knowledge, and what they will gain — the three signals a program committee uses to place a talk.
6 / 25
Sarah from the Backend team sent this Slack message to the CFP organizers:
"Hey @cfp_organizers, just submitted my proposal for 'Optimizing Database Queries with Bloom Filters'. Is there a specific format you prefer for the technical details – should I include pseudocode snippets or diagrams? Just wondering if it's expected."This scenario reflects a common concern among developers when submitting conference proposals. While it's good to inquire about formatting expectations,
Sarah's message is slightly off-point – simply asking for format preferences without demonstrating an understanding of the CFP guidelines (e.g., content requirements) can seem like she hasn't fully absorbed the instructions. The correct response would acknowledge the request while immediately referencing the CFP document to clarify what level of technical detail is expected, ensuring a more professional and proactive approach.7 / 25
David in the code review channel Slack message: 'Just submitted my CFP abstract for the 'Serverless Architecture' track. The prompt asks for a brief overview of your proposed solution's key components and potential challenges. I'm struggling to balance technical depth with brevity – should I focus on outlining the architecture diagram first, or start by detailing the specific technologies I'll be using?'The key here is framing a CFP abstract. Starting with an architectural overview is generally the best approach because it provides immediate context for the reader – they need to understand what problem you're solving before diving into specific technologies. While detailing technologies is important, doing so within the framework of the overall architecture makes the information more digestible and demonstrates strategic thinking. Focusing solely on technology can quickly become overwhelming and lose sight of the core solution; a good abstract clearly communicates the 'what' and 'why' before getting into the 'how'.
8 / 25
Mark from the Frontend team posted this in a Slack channel discussing conference proposals:
"Just finalized my CFP abstract for 'Progressive Web Apps'. The prompt asks for a high-level overview of the core technologies. I'm worried about overwhelming people with details – should I prioritize listing all the frameworks and libraries I'll be using, or focus on the overall architectural approach?"The key here is understanding the CFP's intention: 'a high-level overview'. Listing every framework and library would likely overwhelm the audience and stray from that goal. Focusing on the architectural approach — which describes *how* the technologies are used together — provides a more digestible and relevant summary for potential attendees, aligning with best practices for conference proposals.
9 / 25
Alex's feedback highlights the need for greater clarity and concrete examples. Option 2 correctly identifies that the abstract *already* outlines solutions – it just needs to be bolstered with more specific details to make the value proposition clearer. Options 1 & 4 are incorrect because they misinterpret Alex's comment; option 3 is insufficient as it doesn't address the need for concrete examples.
10 / 25
During a standup update, you're discussing your conference proposal for 'GraphQL Performance Optimization'. Your team lead asks, "What's the most important thing to communicate in the abstract to get people interested?" Consider this snippet from the CFP:
'We seek proposals that demonstrate practical techniques and real-world examples of improving GraphQL performance. Proposals should highlight key strategies, such as query optimization, caching mechanisms, and schema design best practices.'
Which statement best reflects your response?
The key here is framing your proposal in terms of *value*. While technical details are important, the abstract should immediately demonstrate why someone would be interested. Option 2 is incorrect because focusing solely on jargon won't capture attention; option 1 is insufficient as it doesn't address the core prompt. Options 3 and 4 are also too broad – highlighting benefits and a real-world example is far more effective at grabbing the committee's interest.
11 / 25
Sarah from the Backend team sent this Slack message to the CFP organizers:
"Hey @cfp_organizers, just submitted my proposal for 'Optimizing Database Queries with Bloom Filters'. Is there a specific format you prefer for the technical details – should I include pseudocode snippets or diagrams? Just wondering if it's expected."This scenario reflects a common concern among developers when submitting conference proposals. While it's good to inquire about formatting expectations,
Sarah's message is slightly off-point – simply asking for format preferences without demonstrating an understanding of the CFP guidelines (e.g., content requirements) can seem like she hasn't fully absorbed the instructions. The correct response would acknowledge the request while immediately referencing the CFP document to clarify what level of technical detail is expected, ensuring a more professional and proactive approach.12 / 25
David in the code review channel Slack message: 'Just submitted my CFP abstract for the 'Serverless Architecture' track. The prompt asks for a brief overview of your proposed solution's key components and potential challenges. I'm struggling to balance technical depth with brevity – should I focus on outlining the architecture diagram first, or start by detailing the specific technologies I'll be using?'The key here is framing a CFP abstract. Starting with an architectural overview is generally the best approach because it provides immediate context for the reader – they need to understand what problem you're solving before diving into specific technologies. While detailing technologies is important, doing so within the framework of the overall architecture makes the information more digestible and demonstrates strategic thinking. Focusing solely on technology can quickly become overwhelming and lose sight of the core solution; a good abstract clearly communicates the 'what' and 'why' before getting into the 'how'.
13 / 25
Mark from the Frontend team posted this in a Slack channel discussing conference proposals:
"Just finalized my CFP abstract for 'Progressive Web Apps'. The prompt asks for a high-level overview of the core technologies. I'm worried about overwhelming people with details – should I prioritize listing all the frameworks and libraries I'll be using, or focus on the overall architectural approach?"The key here is understanding the CFP's intention: 'a high-level overview'. Listing every framework and library would likely overwhelm the audience and stray from that goal. Focusing on the architectural approach — which describes *how* the technologies are used together — provides a more digestible and relevant summary for potential attendees, aligning with best practices for conference proposals.
14 / 25
Alex's feedback highlights the need for greater clarity and concrete examples. Option 2 correctly identifies that the abstract *already* outlines solutions – it just needs to be bolstered with more specific details to make the value proposition clearer. Options 1 & 4 are incorrect because they misinterpret Alex's comment; option 3 is insufficient as it doesn't address the need for concrete examples.
15 / 25
During a standup update, you're discussing your conference proposal for 'GraphQL Performance Optimization'. Your team lead asks, "What's the most important thing to communicate in the abstract to get people interested?" Consider this snippet from the CFP:
'We seek proposals that demonstrate practical techniques and real-world examples of improving GraphQL performance. Proposals should highlight key strategies, such as query optimization, caching mechanisms, and schema design best practices.'
Which statement best reflects your response?
The key here is framing your proposal in terms of *value*. While technical details are important, the abstract should immediately demonstrate why someone would be interested. Option 2 is incorrect because focusing solely on jargon won't capture attention; option 1 is insufficient as it doesn't address the core prompt. Options 3 and 4 are also too broad – highlighting benefits and a real-world example is far more effective at grabbing the committee's interest.
16 / 25
Sarah from the Backend team sent this Slack message to the CFP organizers:
"Hey @cfp_organizers, just submitted my proposal for 'Optimizing Database Queries with Bloom Filters'. Is there a specific format you prefer for the technical details – should I include pseudocode snippets or diagrams? Just wondering if it's expected."This scenario reflects a common concern among developers when submitting conference proposals. While it's good to inquire about formatting expectations,
Sarah's message is slightly off-point – simply asking for format preferences without demonstrating an understanding of the CFP guidelines (e.g., content requirements) can seem like she hasn't fully absorbed the instructions. The correct response would acknowledge the request while immediately referencing the CFP document to clarify what level of technical detail is expected, ensuring a more professional and proactive approach.17 / 25
David in the code review channel Slack message: 'Just submitted my CFP abstract for the 'Serverless Architecture' track. The prompt asks for a brief overview of your proposed solution's key components and potential challenges. I'm struggling to balance technical depth with brevity – should I focus on outlining the architecture diagram first, or start by detailing the specific technologies I'll be using?'The key here is framing a CFP abstract. Starting with an architectural overview is generally the best approach because it provides immediate context for the reader – they need to understand what problem you're solving before diving into specific technologies. While detailing technologies is important, doing so within the framework of the overall architecture makes the information more digestible and demonstrates strategic thinking. Focusing solely on technology can quickly become overwhelming and lose sight of the core solution; a good abstract clearly communicates the 'what' and 'why' before getting into the 'how'.
18 / 25
Mark from the Frontend team posted this in a Slack channel discussing conference proposals:
"Just finalized my CFP abstract for 'Progressive Web Apps'. The prompt asks for a high-level overview of the core technologies. I'm worried about overwhelming people with details – should I prioritize listing all the frameworks and libraries I'll be using, or focus on the overall architectural approach?"The key here is understanding the CFP's intention: 'a high-level overview'. Listing every framework and library would likely overwhelm the audience and stray from that goal. Focusing on the architectural approach — which describes *how* the technologies are used together — provides a more digestible and relevant summary for potential attendees, aligning with best practices for conference proposals.
19 / 25
Alex's feedback highlights the need for greater clarity and concrete examples. Option 2 correctly identifies that the abstract *already* outlines solutions – it just needs to be bolstered with more specific details to make the value proposition clearer. Options 1 & 4 are incorrect because they misinterpret Alex's comment; option 3 is insufficient as it doesn't address the need for concrete examples.
20 / 25
During a standup update, you're discussing your conference proposal for 'GraphQL Performance Optimization'. Your team lead asks, "What's the most important thing to communicate in the abstract to get people interested?" Consider this snippet from the CFP:
'We seek proposals that demonstrate practical techniques and real-world examples of improving GraphQL performance. Proposals should highlight key strategies, such as query optimization, caching mechanisms, and schema design best practices.'
Which statement best reflects your response?
The key here is framing your proposal in terms of *value*. While technical details are important, the abstract should immediately demonstrate why someone would be interested. Option 2 is incorrect because focusing solely on jargon won't capture attention; option 1 is insufficient as it doesn't address the core prompt. Options 3 and 4 are also too broad – highlighting benefits and a real-world example is far more effective at grabbing the committee's interest.
21 / 25
Sarah from the Backend team sent this Slack message to the CFP organizers:
"Hey @cfp_organizers, just submitted my proposal for 'Optimizing Database Queries with Bloom Filters'. Is there a specific format you prefer for the technical details – should I include pseudocode snippets or diagrams? Just wondering if it's expected."This scenario reflects a common concern among developers when submitting conference proposals. While it's good to inquire about formatting expectations,
Sarah's message is slightly off-point – simply asking for format preferences without demonstrating an understanding of the CFP guidelines (e.g., content requirements) can seem like she hasn't fully absorbed the instructions. The correct response would acknowledge the request while immediately referencing the CFP document to clarify what level of technical detail is expected, ensuring a more professional and proactive approach.22 / 25
David in the code review channel Slack message: 'Just submitted my CFP abstract for the 'Serverless Architecture' track. The prompt asks for a brief overview of your proposed solution's key components and potential challenges. I'm struggling to balance technical depth with brevity – should I focus on outlining the architecture diagram first, or start by detailing the specific technologies I'll be using?'The key here is framing a CFP abstract. Starting with an architectural overview is generally the best approach because it provides immediate context for the reader – they need to understand what problem you're solving before diving into specific technologies. While detailing technologies is important, doing so within the framework of the overall architecture makes the information more digestible and demonstrates strategic thinking. Focusing solely on technology can quickly become overwhelming and lose sight of the core solution; a good abstract clearly communicates the 'what' and 'why' before getting into the 'how'.
23 / 25
Mark from the Frontend team posted this in a Slack channel discussing conference proposals:
"Just finalized my CFP abstract for 'Progressive Web Apps'. The prompt asks for a high-level overview of the core technologies. I'm worried about overwhelming people with details – should I prioritize listing all the frameworks and libraries I'll be using, or focus on the overall architectural approach?"The key here is understanding the CFP's intention: 'a high-level overview'. Listing every framework and library would likely overwhelm the audience and stray from that goal. Focusing on the architectural approach — which describes *how* the technologies are used together — provides a more digestible and relevant summary for potential attendees, aligning with best practices for conference proposals.
24 / 25
Alex's feedback highlights the need for greater clarity and concrete examples. Option 2 correctly identifies that the abstract *already* outlines solutions – it just needs to be bolstered with more specific details to make the value proposition clearer. Options 1 & 4 are incorrect because they misinterpret Alex's comment; option 3 is insufficient as it doesn't address the need for concrete examples.
25 / 25
During a standup update, you're discussing your conference proposal for 'GraphQL Performance Optimization'. Your team lead asks, "What's the most important thing to communicate in the abstract to get people interested?" Consider this snippet from the CFP:
'We seek proposals that demonstrate practical techniques and real-world examples of improving GraphQL performance. Proposals should highlight key strategies, such as query optimization, caching mechanisms, and schema design best practices.'
Which statement best reflects your response?
The key here is framing your proposal in terms of *value*. While technical details are important, the abstract should immediately demonstrate why someone would be interested. Option 2 is incorrect because focusing solely on jargon won't capture attention; option 1 is insufficient as it doesn't address the core prompt. Options 3 and 4 are also too broad – highlighting benefits and a real-world example is far more effective at grabbing the committee's interest.
Frequently Asked Questions
What does the "Submitting Conference Proposals" exercise practise?
Practice writing compelling CFP abstracts, speaker bios, and talk titles for tech conferences. 5 exercises.
How many questions are in this exercise?
This exercise has 25 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Conference & Community category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Submitting Conference Proposals" part of a larger series?
Yes — it's one exercise in the Conference & Community category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Conference & Community category page for related exercises, or browse the main Exercises hub for other IT English topics.