InternshipAll 60 tasks, level by level
The real graded Developer Relations tasks the portal assigns, grouped into three levels.
The portal assigns these Developer Relations tasks. Finish Level 1 before Level 2 and Level 2 before Level 3. Your mentor may mark some tasks as required for the certificate.
Level 1: Foundations (24 tasks)
| Task | What to do |
|---|---|
| What DevRel is | Explain developer relations: advocacy, community, content and feedback to the product team. |
| Pick a technology | Choose one developer tool or API you will advocate for during the internship and explain why. |
| Getting-started guide | Write a getting-started guide for your chosen tool and test it from a clean machine. |
| Sample app | Build a small sample app using the tool and publish it in a repo named devrel-internship. |
| Developer persona | Describe 2 developer personas who would use your tool: background, goals and frustrations. |
| Blog post | Write a 1,000-word technical blog post about something you built, with code samples. |
| Social posts | Write 5 short developer-friendly posts (LinkedIn or X) about your tool with code or screenshots. |
| Community research | List 10 communities (Discord, Reddit, meetups, forums) where developers of your tool gather. |
| Answer questions | Answer 5 real questions on Stack Overflow, GitHub Discussions or a forum, and link them. |
| Lightning talk | Prepare and record a 5-minute lightning talk about your sample app. |
| Personal developer profile | Polish your GitHub profile README and pinned repos as a developer advocate would. |
| Code sample quality | Review your sample app for clear names, comments and a README anyone can follow. |
| Developer journey map | Map a developer's journey from discovering your tool to becoming an advocate. |
| Code snippet library | Create 10 copy-paste-ready code snippets for common tasks with your tool. |
| FAQ from forums | Collect the 15 most common questions about your tool from forums and answer them. |
| Thread or carousel | Write a technical thread or carousel that explains one concept with code. |
| README makeover | Rewrite the README of your sample app so a beginner can run it in 5 minutes. |
| Demo script | Write a 5-minute demo script with exact steps and a backup plan. |
| Slide design | Make a 10-slide deck with big code, few words and a clear story. |
| Office hours | Host a 30-minute office hours session for classmates and record questions. |
| Community guidelines | Write community guidelines for a Discord or WhatsApp developer group. |
| Changelog post | Write a short post explaining what changed in the latest release of your tool. |
| Accessibility in content | Add captions, alt text and transcripts to your content. |
| Personal content plan | Plan one piece of content a week for a month. |
Level 2: Building real features (20 tasks)
| Task | What to do |
|---|---|
| Video tutorial | Record a 10-minute screen-cast tutorial and upload it (YouTube unlisted is fine). |
| Live demo | Run a live coding demo for classmates and collect feedback with a short form. |
| Workshop design | Design a 1-hour hands-on workshop: agenda, prerequisites, exercises and solutions. |
| Developer feedback report | Collect feedback from 5 developers who tried your guide and write a report for the product team. |
| Open-source contribution | Make a meaningful contribution (code or docs) to the open-source project behind your tool. |
| Newsletter | Write two issues of a developer newsletter with news, a tip and a featured community project. |
| Event plan | Plan a college meetup or online event: topic, speakers, promotion and run sheet. |
| Content calendar | Build a one-month content calendar across blog, video and social. |
| Measuring DevRel | Define metrics for DevRel (activation, community growth, content reach) and how to track them. |
| Comparison guide | Write an honest comparison of your tool and two alternatives, with when to use each. |
| Interactive tutorial | Build an interactive tutorial (CodeSandbox, StackBlitz or a notebook). |
| Integration guide | Write a guide for using your tool with another popular framework. |
| Live stream | Host a live coding stream or recorded session and answer chat questions. |
| Developer survey | Run a short developer survey and share the results publicly. |
| Podcast or interview | Interview a developer about how they use the tool and publish it. |
| Sample app gallery | Build three small sample apps for different use cases. |
| Localisation of content | Create one tutorial in an Indian language and compare engagement. |
| Campus talk | Give a talk at a college or meetup and collect attendance and feedback. |
| Bug bash | Organise a bug bash where community members test a new feature. |
| DevRel metrics review | Review one month of metrics and decide what to stop, start and continue. |
Level 3: Professional work and capstone (16 tasks)
| Task | What to do |
|---|---|
| Run the workshop | Deliver your workshop to at least 10 people and report attendance, feedback and improvements. |
| Community program | Design a student ambassador or champions program with roles, rewards and activities. |
| Docs improvement proposal | Audit the official docs of your tool and propose 5 improvements with examples. |
| Conference talk proposal | Write a talk proposal (title, abstract, outline) for a real developer conference CFP. |
| Hackathon kit | Create a hackathon starter kit: template repo, challenge ideas and judging criteria. |
| Real company DevRel | Write a developer-facing guide or post about a Training Trains, W3AppDevelopers or DomainHostly product. |
| Analytics review | Review the reach of everything you published and write what worked and what you would change. |
| Capstone: DevRel portfolio | Publish a DevRel portfolio: sample apps, posts, videos, talk, workshop results and community impact. |
| Program proposal | Write a proposal for a DevRel program with goals, budget and metrics. |
| Partner content | Co-create content with another community or company. |
| Advocate feedback loop | Set up a regular process for sharing developer feedback with engineering. |
| Crisis communication | Plan how to communicate an outage or breaking change to the developer community. |
| Conference booth plan | Plan a conference booth: demo, swag, lead capture and follow-up. |
| Mentor new contributors | Mentor two new contributors to make their first pull request. |
| Content repurposing | Turn one talk into a blog post, a video, a thread and a newsletter item. |
| Capstone 2: launch campaign | Plan and run a developer launch campaign for a feature or project, with content, events and a results report. |