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 / 5
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 / 5
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 / 5
"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 / 5
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.