1 / 5
"The company is hiring a Developer Advocate" — what is the primary purpose of this role?
-
-
-
-
Option A is correct. Developer Advocates sit at the intersection of community and product.
DevRel role comparison:| Role | Primary focus |
|---|
| Developer Advocate | Community trust, honest feedback loops, external developer success |
| DX Engineer | Tooling, SDKs, docs, onboarding flow improvements |
| Technical Evangelist | Outward marketing, brand positioning via technical content |
Key vocabulary: developer advocate, internal feedback loop, developer experience (DX), DevRel
2 / 5
"The DevRel team is measuring developer experience (DX)" — what does DX measure?
-
-
-
-
Option D is correct. DX measures the entire developer journey, not just usage volume.
DX metrics:| Metric | What it measures |
|---|
| Time-to-first-value (TTFV) | Minutes from signup to first successful API call |
| Pit of success | Does the easiest path lead to correct usage? |
| Support ticket volume | Proxy for friction — high volume = poor docs/DX |
| SDK ergonomics score | How natural is it to use the SDK correctly? |
Key vocabulary: developer experience, time-to-first-value, pit of success, SDK ergonomics
3 / 5
"The advocate must give honest feedback even when critical" — what does this tension reveal about the DevRel role?
-
-
-
-
Option B is correct. The DevRel trust triangle is the core tension of the role.
DevRel trust triangle:| Relationship | Expectation | Risk if broken |
|---|
| Community trust | Honest content — acknowledges limitations | Seen as marketing, not advocacy |
| Company relationship | Represent the brand professionally | Role eliminated or scope reduced |
Advocates who are purely promotional quickly lose community credibility — the core value of the role disappears.
Key vocabulary: authentic advocacy, community trust, internal product feedback
4 / 5
"We're running a hackathon to build community around our API" — what makes it effective?
-
-
-
-
Option C is correct. Great hackathons are about low friction and creative problem-solving.
Hackathon design checklist:| Element | Why it matters |
|---|
| Clear problem statement | Participants need focus — "build anything" leads to confusion |
| No-approval API access | Every sign-up step lost = fewer participants |
| Live support channels | Blocked developers quit; instant help = projects ship |
| Creative solution recognition | Recognition matters as much as prize money |
Key vocabulary: hackathon design, low barrier to entry, problem statement quality, developer onboarding event
5 / 5
"The DevRel strategy needs internal vs. external DevRel distinction" — what is the difference?
-
-
-
-
Option B is correct. Both require the same skills — the audience is different.
Internal vs. external DevRel:| Dimension | External DevRel | Internal DevRel |
|---|
| Audience | External developer community | Internal engineers / teams |
| Activities | Talks, blog posts, OSS, events, tutorials | Internal docs, platform advocacy, DX improvements |
| Goal | Community growth, product adoption | Developer productivity, platform usage |
Key vocabulary: internal DevRel, platform advocacy, developer productivity