Practice the key verb+noun collocations used in developer relations work, including community building, documentation writing, and developer advocacy in English.
0 / 5 completed
1 / 5
Fill in: 'Our DevRel team works hard to ___ a strong community around the open-source SDK.'
We 'build a community' — 'build' is the fixed collocation for the sustained effort of forming and strengthening a developer community. 'Grow' focuses on size rather than formation; 'create' implies a one-time act; 'develop' is better suited to skills or products.
2 / 5
Fill in: 'We hired two technical writers to ___ developer documentation for the new GraphQL API.'
We 'write developer documentation' — 'write' is the natural collocation for producing written technical content. 'Create documentation' is acceptable but slightly more formal; 'produce' sounds industrial; 'draft' implies a preliminary version, not the final deliverable.
3 / 5
Fill in: 'We will ___ a two-hour workshop at the conference to help attendees integrate the SDK.'
We 'host a workshop' — 'host' is the standard collocation when a team or company organises and runs a workshop for an external audience. 'Run' is also common but slightly more internal; 'give' suits presentations and talks; 'hold' collocates with meetings.
4 / 5
Fill in: 'Part of our DevRel workflow is to ___ GitHub issues within 48 hours of submission.'
We 'respond to GitHub issues' — 'respond to' is the idiomatic collocation for engaging with user-submitted issues in a public repository. 'Answer' is used for questions, not issues; 'reply' needs an object preposition ('reply to'); 'address' is used for broader concerns, not specific tickets.
5 / 5
Fill in: 'I was asked to ___ a product at every developer conference this quarter.'
We 'evangelize a product' — 'evangelize' is the DevRel-specific collocation for enthusiastically spreading awareness and adoption of a product. 'Promote' is a marketing term; 'market' implies paid activity; 'advocate' is used with 'for', not as a direct-object collocation.