Training Trains logo

Developer Relations Internship

Help developers succeed with technology: sample apps, tutorials, talks, videos, community building and feedback to product teams.

GitHubMarkdown / blogsVideo recordingDiscord / communities

What you'll work on

Full syllabus: all 60 graded tasks

These are the actual tasks the internship portal assigns for this domain. You submit each one with proof (a GitHub link or document) and a mentor reviews it.

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

Real software work, not just training

Every Developer Relations task is reviewed by our team and saved to your portfolio. Interns who pass the readiness check can take real work from Training Trains, W3AppDevelopers and DomainHostly projects on the Company Work board.

Digital MarketingFull Stack Web Application Development
See the software we build →

Frequently asked questions

Do I need experience to join the Developer Relations internship?+

You should be able to build small apps and enjoy explaining things to others.

What will I do in the Developer Relations internship?+

You complete 60 graded tasks in three levels: foundations, real features, and professional work. Each task is submitted with GitHub or document proof and reviewed. The final capstone is: Capstone 2: launch campaign.

Do I get a certificate for the Developer Relations internship?+

Yes. After your required tasks are approved, your attendance is above 75% and you pass the proctored final exam, you get a graded completion certificate that anyone can verify at trainingtrains.com/verify.

Can I do the Developer Relations internship online?+

Yes. You can do it fully online from home, or offline at our Erode and Perundurai branches. Tasks, quizzes and mentor reviews are the same in both modes.

Available both online (work from home) and offline at our Erode and Perundurai branches - see the full internship program details for departments, duration, and the application process.

Apply for the Developer Relations internship