Developer relations is a discipline with its own professional vocabulary. These exercises cover the collocations developer advocates and DevRel teams use when creating content, engaging communities, and presenting at conferences.
0 / 5 completed
1 / 5
The developer advocate was hired to ___ for the new GraphQL API and onboard external teams.
Write documentation is the standard professional collocation for authoring technical reference material. 'Write' is the canonical verb in technical writing. 'Create' is also used; 'make' and 'produce' focus on output rather than the craft of technical writing.
2 / 5
The DevRel team was asked to ___ for each major SDK to reduce the barrier to adoption.
Create tutorials is the standard developer relations collocation for producing step-by-step educational content. 'Create' emphasises content production. 'Write' is also common; 'build' is informal in a content context; 'make' is too vague.
3 / 5
The developer advocate used the forum and Discord server to ___ and answer questions.
Engage the community is the standard DevRel collocation for actively participating in and building relationships within a developer ecosystem. 'Engage' implies two-way interaction and sustained relationship-building. 'Support' and 'help' are reactive; 'join' implies passive membership.
4 / 5
Three team members were selected to ___ and demonstrate the platform's new inference capabilities.
Present at conferences is the standard professional collocation for delivering a talk or demo at an industry event. 'Present' implies delivering prepared content to an audience. 'Speak' is also common; 'go to' and 'attend' describe participation only, not presenting.
5 / 5
The product team set up office hours for the developer advocate to ___ from API consumers.
Gather feedback is the standard DevRel and product collocation for proactively soliciting opinions and insights from users. 'Gather' implies active, structured elicitation. 'Collect' is also common; 'receive' implies passive intake; 'get' is too informal.