📝 CFP Proposal Writing
0 / 26 completed
1 / 26
What is the standard structure of a compelling CFP abstract?
Option B describes the proven CFP abstract formula.
Abstract structure:
Key vocabulary: compelling hook, learning outcomes, target audience, speaker authority, abstract vs. talk description
Abstract structure:
| Section | Purpose | Example |
|---|---|---|
| Compelling hook | Why this problem matters | "Kubernetes RBAC misconfigurations are the #1 cause of cloud breaches" |
| Learning outcomes | What attendees will leave able to do | "Attendees will leave able to audit..." |
| Speaker authority | Why you are qualified | "I have hardened 40+ production clusters" |
Key vocabulary: compelling hook, learning outcomes, target audience, speaker authority, abstract vs. talk description
2 / 26
"The CFP asks for session format: talk, workshop, or lightning talk" — what is a lightning talk?
Option D is correct. A lightning talk presents a single idea briefly.
Session format comparison:
Key vocabulary: lightning talk, single-idea focus, first-time speaker strategy
Session format comparison:
| Format | Duration | Best for |
|---|---|---|
| Lightning talk | 5–10 min | Single idea, first-time speakers |
| Talk | 25–45 min | Core conference session |
| Workshop | 60–120 min | Hands-on, interactive learning |
Key vocabulary: lightning talk, single-idea focus, first-time speaker strategy
3 / 26
"The program committee rejected your proposal as too vendor-specific" — what does vendor-specific mean?
Option A is correct. Program committees actively filter out vendor-specific proposals.
Vendor-neutral vs. vendor-specific:
Key vocabulary: vendor-neutral content, broadly applicable, program committee
Vendor-neutral vs. vendor-specific:
| Vendor-specific ✗ | Vendor-neutral ✓ |
|---|---|
| "IaC at our company with Terraform Cloud" | "IaC patterns for multi-cloud environments" |
| "How we scaled with AWS Lambda" | "Serverless cold-start patterns and trade-offs" |
Key vocabulary: vendor-neutral content, broadly applicable, program committee
4 / 26
"The CFP asks for key takeaways (3-5 bullets)" — what makes a takeaway effective?
Option C is correct. Effective takeaways are specific and actionable.
Takeaway quality comparison:
Formula: "Attendees will be able to [specific action] [specific context]"
Key vocabulary: actionable takeaway, learning outcome, attendee value proposition
Takeaway quality comparison:
| Weak takeaway ✗ | Strong takeaway ✓ |
|---|---|
| "Learn about Kubernetes security" | "Be able to audit RBAC roles for three common misconfigurations" |
| "Understand CI/CD better" | "Know how to implement a zero-downtime deployment pipeline using feature flags" |
Formula: "Attendees will be able to [specific action] [specific context]"
Key vocabulary: actionable takeaway, learning outcome, attendee value proposition
5 / 26
"Your talk was accepted — write a speaker bio" — what should it include?
Option B is correct. A speaker bio follows a clear formula and is always written in third person.
Speaker bio formula:
Key vocabulary: speaker bio, third-person bio, talk-specific relevance
Speaker bio formula:
| Element | Example |
|---|---|
| Name + Role | "Jana Novak is a Senior Platform Engineer at FinCo" |
| Professional expertise (talk-relevant) | "specialising in Kubernetes RBAC and zero-trust networking" |
| Speaker credibility | "She has hardened 40+ production clusters across three regulated industries" |
| Personal touch (optional) | "Outside work, Jana co-organises the local CNCF meetup" |
Key vocabulary: speaker bio, third-person bio, talk-specific relevance
6 / 26
You're reviewing a draft PR description for a new API endpoint. The developer, David, writes: 'This endpoint returns JSON data formatted according to RFC 7231.' While technically accurate – referencing the relevant standard – it might intimidate some team members unfamiliar with the specification. Which of the following responses would best help David refine his description while acknowledging the technical detail?
David's statement is technically correct but overly technical and potentially intimidating. Option 2 directly addresses this by requesting a simplified explanation, demonstrating an understanding of the team's diverse knowledge levels. The other options either oversimplify the importance of standards or shift the focus away from usability concerns. This approach encourages David to tailor his communication for broader comprehension.
7 / 26
Code Review Comment
You're reviewing a PR submitted by Alex for a new microservice that handles user authentication. Alex has included a comment in the PR description stating: 'Utilizing OAuth 2.0 for secure access and delegation.' While this accurately describes the technology, Sarah, another reviewer, points out that many team members are unfamiliar with the nuances of OAuth 2.0 and might misinterpret its implications.
Which of the following responses would best address Sarah's concern and guide Alex towards a clearer explanation within the PR description?
The correct answer (option 2) acknowledges Alex's choice while providing a practical suggestion for clarity and educating the team. The other options are problematic: option 1 dismisses a valid technology choice; option 3 is too technical without context; and option 4 removes valuable information that could be explained simply. This response balances technical accuracy with accessibility, which is crucial during code reviews.
8 / 26
During a code review of Emily's PR introducing a new rate limiting system, she uses the term 'throttling'. While technically correct – reducing the frequency of requests – it doesn't fully convey the system's behavior. Ben, another reviewer, suggests phrasing that highlights both the limitation and the potential for dynamic adjustment. Which of the following responses would best address Ben's concern and facilitate a more informative discussion?
'Throttling' can be perceived as static. Suggesting we implement 'dynamic rate limiting', which allows us to adapt to changing traffic patterns, provides a clearer picture of how the system responds in real-time.'
The incorrect options either dismiss the concern about clarity or offer overly simplistic/misleading alternatives. The correct answer acknowledges the potential for ambiguity with 'throttling' and proposes a more descriptive term – 'dynamic rate limiting' – that better communicates both the limitation *and* the system's adaptive capabilities. This demonstrates an understanding of communicating technical concepts effectively.
9 / 26
You're reviewing a draft PR description for a new database migration. Maria writes: 'This migration updates the schema to align with the latest version of the PostgreSQL standard.' While technically correct – referencing the relevant specification – it's likely to confuse developers unfamiliar with PostgreSQL internals and potential compatibility issues. David, another reviewer, suggests a more accessible explanation. Which of the following responses would best address David's concern while maintaining technical accuracy?
The correct answer (option 2) provides a more approachable explanation for developers without deep PostgreSQL knowledge. It focuses on the benefits of using a recent version and avoids jargon like 'PostgreSQL standard' which could be confusing. Options A and D are too vague, while option B is overly specific about a particular version number, potentially leading to confusion if future versions change.
10 / 26
You're reviewing a draft PR description for a new API endpoint. The developer, David, writes: 'This endpoint returns JSON data formatted according to RFC 7231.' While technically accurate – referencing the relevant standard – it might intimidate some team members unfamiliar with the specification. Which of the following responses would best help David refine his description while acknowledging the technical detail?
David's statement is technically correct but overly technical and potentially intimidating. Option 2 directly addresses this by requesting a simplified explanation, demonstrating an understanding of the team's diverse knowledge levels. The other options either oversimplify the importance of standards or shift the focus away from usability concerns. This approach encourages David to tailor his communication for broader comprehension.
11 / 26
Code Review Comment
You're reviewing a PR submitted by Alex for a new microservice that handles user authentication. Alex has included a comment in the PR description stating: 'Utilizing OAuth 2.0 for secure access and delegation.' While this accurately describes the technology, Sarah, another reviewer, points out that many team members are unfamiliar with the nuances of OAuth 2.0 and might misinterpret its implications.
Which of the following responses would best address Sarah's concern and guide Alex towards a clearer explanation within the PR description?
The correct answer (option 2) acknowledges Alex's choice while providing a practical suggestion for clarity and educating the team. The other options are problematic: option 1 dismisses a valid technology choice; option 3 is too technical without context; and option 4 removes valuable information that could be explained simply. This response balances technical accuracy with accessibility, which is crucial during code reviews.
12 / 26
During a code review of Emily's PR introducing a new rate limiting system, she uses the term 'throttling'. While technically correct – reducing the frequency of requests – it doesn't fully convey the system's behavior. Ben, another reviewer, suggests phrasing that highlights both the limitation and the potential for dynamic adjustment. Which of the following responses would best address Ben's concern and facilitate a more informative discussion?
'Throttling' can be perceived as static. Suggesting we implement 'dynamic rate limiting', which allows us to adapt to changing traffic patterns, provides a clearer picture of how the system responds in real-time.'
The incorrect options either dismiss the concern about clarity or offer overly simplistic/misleading alternatives. The correct answer acknowledges the potential for ambiguity with 'throttling' and proposes a more descriptive term – 'dynamic rate limiting' – that better communicates both the limitation *and* the system's adaptive capabilities. This demonstrates an understanding of communicating technical concepts effectively.
13 / 26
You're reviewing a draft PR description for a new database migration. Maria writes: 'This migration updates the schema to align with the latest version of the PostgreSQL standard.' While technically correct – referencing the relevant specification – it's likely to confuse developers unfamiliar with PostgreSQL internals and potential compatibility issues. David, another reviewer, suggests a more accessible explanation. Which of the following responses would best address David's concern while maintaining technical accuracy?
The correct answer (option 2) provides a more approachable explanation for developers without deep PostgreSQL knowledge. It focuses on the benefits of using a recent version and avoids jargon like 'PostgreSQL standard' which could be confusing. Options A and D are too vague, while option B is overly specific about a particular version number, potentially leading to confusion if future versions change.
14 / 26
You're reviewing a draft PR description for a new API endpoint. The developer, David, writes: 'This endpoint returns JSON data formatted according to RFC 7231.' While technically accurate – referencing the relevant standard – it might intimidate some team members unfamiliar with the specification. Which of the following responses would best help David refine his description while acknowledging the technical detail?
David's statement is technically correct but overly technical and potentially intimidating. Option 2 directly addresses this by requesting a simplified explanation, demonstrating an understanding of the team's diverse knowledge levels. The other options either oversimplify the importance of standards or shift the focus away from usability concerns. This approach encourages David to tailor his communication for broader comprehension.
15 / 26
Code Review Comment
You're reviewing a PR submitted by Alex for a new microservice that handles user authentication. Alex has included a comment in the PR description stating: 'Utilizing OAuth 2.0 for secure access and delegation.' While this accurately describes the technology, Sarah, another reviewer, points out that many team members are unfamiliar with the nuances of OAuth 2.0 and might misinterpret its implications.
Which of the following responses would best address Sarah's concern and guide Alex towards a clearer explanation within the PR description?
The correct answer (option 2) acknowledges Alex's choice while providing a practical suggestion for clarity and educating the team. The other options are problematic: option 1 dismisses a valid technology choice; option 3 is too technical without context; and option 4 removes valuable information that could be explained simply. This response balances technical accuracy with accessibility, which is crucial during code reviews.
16 / 26
During a code review of Emily's PR introducing a new rate limiting system, she uses the term 'throttling'. While technically correct – reducing the frequency of requests – it doesn't fully convey the system's behavior. Ben, another reviewer, suggests phrasing that highlights both the limitation and the potential for dynamic adjustment. Which of the following responses would best address Ben's concern and facilitate a more informative discussion?
'Throttling' can be perceived as static. Suggesting we implement 'dynamic rate limiting', which allows us to adapt to changing traffic patterns, provides a clearer picture of how the system responds in real-time.'
The incorrect options either dismiss the concern about clarity or offer overly simplistic/misleading alternatives. The correct answer acknowledges the potential for ambiguity with 'throttling' and proposes a more descriptive term – 'dynamic rate limiting' – that better communicates both the limitation *and* the system's adaptive capabilities. This demonstrates an understanding of communicating technical concepts effectively.
17 / 26
You're reviewing a draft PR description for a new database migration. Maria writes: 'This migration updates the schema to align with the latest version of the PostgreSQL standard.' While technically correct – referencing the relevant specification – it's likely to confuse developers unfamiliar with PostgreSQL internals and potential compatibility issues. David, another reviewer, suggests a more accessible explanation. Which of the following responses would best address David's concern while maintaining technical accuracy?
The correct answer (option 2) provides a more approachable explanation for developers without deep PostgreSQL knowledge. It focuses on the benefits of using a recent version and avoids jargon like 'PostgreSQL standard' which could be confusing. Options A and D are too vague, while option B is overly specific about a particular version number, potentially leading to confusion if future versions change.
18 / 26
You're reviewing a draft PR description for a new API endpoint. The developer, David, writes: 'This endpoint returns JSON data formatted according to RFC 7231.' While technically accurate – referencing the relevant standard – it might intimidate some team members unfamiliar with the specification. Which of the following responses would best help David refine his description while acknowledging the technical detail?
David's statement is technically correct but overly technical and potentially intimidating. Option 2 directly addresses this by requesting a simplified explanation, demonstrating an understanding of the team's diverse knowledge levels. The other options either oversimplify the importance of standards or shift the focus away from usability concerns. This approach encourages David to tailor his communication for broader comprehension.
19 / 26
Code Review Comment
You're reviewing a PR submitted by Alex for a new microservice that handles user authentication. Alex has included a comment in the PR description stating: 'Utilizing OAuth 2.0 for secure access and delegation.' While this accurately describes the technology, Sarah, another reviewer, points out that many team members are unfamiliar with the nuances of OAuth 2.0 and might misinterpret its implications.
Which of the following responses would best address Sarah's concern and guide Alex towards a clearer explanation within the PR description?
The correct answer (option 2) acknowledges Alex's choice while providing a practical suggestion for clarity and educating the team. The other options are problematic: option 1 dismisses a valid technology choice; option 3 is too technical without context; and option 4 removes valuable information that could be explained simply. This response balances technical accuracy with accessibility, which is crucial during code reviews.
20 / 26
During a code review of Emily's PR introducing a new rate limiting system, she uses the term 'throttling'. While technically correct – reducing the frequency of requests – it doesn't fully convey the system's behavior. Ben, another reviewer, suggests phrasing that highlights both the limitation and the potential for dynamic adjustment. Which of the following responses would best address Ben's concern and facilitate a more informative discussion?
'Throttling' can be perceived as static. Suggesting we implement 'dynamic rate limiting', which allows us to adapt to changing traffic patterns, provides a clearer picture of how the system responds in real-time.'
The incorrect options either dismiss the concern about clarity or offer overly simplistic/misleading alternatives. The correct answer acknowledges the potential for ambiguity with 'throttling' and proposes a more descriptive term – 'dynamic rate limiting' – that better communicates both the limitation *and* the system's adaptive capabilities. This demonstrates an understanding of communicating technical concepts effectively.
21 / 26
You're reviewing a draft PR description for a new database migration. Maria writes: 'This migration updates the schema to align with the latest version of the PostgreSQL standard.' While technically correct – referencing the relevant specification – it's likely to confuse developers unfamiliar with PostgreSQL internals and potential compatibility issues. David, another reviewer, suggests a more accessible explanation. Which of the following responses would best address David's concern while maintaining technical accuracy?
The correct answer (option 2) provides a more approachable explanation for developers without deep PostgreSQL knowledge. It focuses on the benefits of using a recent version and avoids jargon like 'PostgreSQL standard' which could be confusing. Options A and D are too vague, while option B is overly specific about a particular version number, potentially leading to confusion if future versions change.
22 / 26
During a code review of Ben's PR introducing a new caching layer for API responses, he writes in the commit message: 'Implementing Least Recently Used (LRU) eviction policy to optimize performance.' Which phrasing best clarifies this approach for another developer?
The original description is technically correct but lacks crucial context. It's important to clarify parameters like cache size and expiration times, which directly impact the effectiveness of the LRU policy. Simply stating 'LRU' assumes a shared understanding that isn't always present, especially with less experienced developers or those unfamiliar with caching strategies. Option A is too critical; option C minimizes the need for clarification.
23 / 26
Sarah, a senior engineer, sends this Slack message to the team: 'Let's refactor this function to improve its readability and reduce cyclomatic complexity.' What does Sarah *most* likely mean in this context?
'Readability' and 'cyclomatic complexity' are common terms in software development referring to code quality. Sarah is advocating for improvements to the *structure* of the function – simplifying its logic and reducing nesting – which directly addresses these concerns. While performance optimization (option 3) can sometimes be a consequence, it's not the primary focus here. Option 1 & 4 are irrelevant to her message.
24 / 26
You're debugging an API endpoint that returns data in JSON format. The response includes the following field: 'status_code': '409 Conflict'. What does this status code *primarily* indicate?
A '409 Conflict' status code in RESTful APIs signifies that a conflict occurred during the request. This typically happens when you attempt to create a resource that already exists, or modify a resource concurrently with another operation. It's distinct from other common codes like '401 Unauthorized' (authentication) or '500 Internal Server Error' (server issue).
25 / 26
David is writing the description for a PR that implements a new feature: a two-factor authentication system. He writes: 'This change adds support for TOTP (Time-based One-time Password) authentication.' Which of the following is the *most* appropriate addition to this description?
While all options could be relevant to a full PR description, David's statement focuses specifically on *how* the TOTP system is implemented. The most direct and necessary addition is to explain what user interface elements are impacted by this change – which part of the user experience will be affected by the new authentication method. The other options are less directly related to the core functionality being added.
26 / 26
During a daily stand-up, Maria reports: 'I'm working on improving the performance of the user profile service by optimizing database queries.' What is the *most* important next step she should take to provide more specific information?
Maria's statement is vague. The crucial next step is to detail *which* queries are being optimized and what their current execution times are. This provides concrete data for discussion and allows others to understand the scope of the work and assess its potential impact. Simply rewriting (option 1) or focusing on front-end optimization (option 3) are premature actions without understanding the root performance issue.
Frequently Asked Questions
What does the "CFP Proposal Writing" exercise practise?
Practice Call For Proposals vocabulary: abstract writing, session formats, speaker bio, learning outcomes.
How many questions are in this exercise?
This exercise has 26 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 "CFP Proposal Writing" 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.