How to become a developer advocate: Part 4, submitting to a call for papers

A successful transition from engineering to developer advocacy or technical pre-sales requires a combination of soft skills, including public speaking, building empathy with one's audience, and finding the right approach to share knowledge. To craft an effective abstract for a conference call for papers (CFP), it is essential to carefully read the conference's CFP, identify the target audience and suggested topics, and choose a problem or experience that can be confidently shared. The abstract should present the problem, describe the solution, and highlight the benefits of the proposed talk, while also being concise and free from sales pitches unless specifically requested by the conference. A well-written title that captures the essence of the talk in 50 characters or less is also crucial, and having a trusted advisor review the abstract for technical accuracy can make all the difference.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.