Developer Relations Engineer

Coder is an open-source remote development platform trusted by platform engineers at some of the world’s largest enterprises. As a DevRel Engineer, you’ll shape the experience that helps curious users become active practitioners, contributors, and advocates inside their companies, universities, and home labs.

Responsibilities:

• Be a consistent presence in Discord and GitHub by answering questions, unblocking users, and spotting recurring patterns
• Support community contributors by helping useful fixes, templates, and ideas move into the registry, docs, or product and engineering backlog
• Translate community friction into actionable feedback for product, engineering, docs, and marketing
• Track the broader developer pulse across Hacker News, Reddit, LinkedIn, and similar channels, then surface relevant signals internally
• Balance self-serve support with direct help so users can move quickly, with or without contacting Coder
• Curate the registry with a community lens: audit coverage gaps, prioritize what platform engineers need, and keep high-use templates maintained
• Create and maintain high-quality first-party templates for key stacks, including Python, Node, Go, Rust, and Java
• Build reference templates across Docker, Kubernetes, Proxmox, AWS, and bare metal
• Make contributing to the registry easier by improving contributor guides, streamlining reviews, and partnering with engineering on registry server improvements
• Review community pull requests quickly and constructively, with clear feedback, reasonable quality bars, and a bias toward getting good work merged
• Maintain CI, linting, and automated testing so the registry stays healthy as the Terraform provider evolves
• Give talks or run workshops at technical events such as KubeCon, Open Source Summit, SCaLE, FOSDEM, and similar conferences
• Build demo environments backed by public GitHub repos so anyone can clone, deploy, and learn from them
• Create hardware demos on physical devices such as Raspberry Pi, Intel NUCs, and home lab servers
• Produce recorded demos that give sales, marketing, onboarding, and community teams clear walkthroughs of important use cases
• Run live product demos at events, meetups, and online, grounded in real user scenarios rather than slides
• Collaborate with marketing on content that extends your reach, including blog posts, social clips, podcast appearances, and launch announcements
• Audit existing docs and guides for gaps, friction, and stale paths, then fix them through rewrites, restructuring, or net-new content
• Own the getting-started experience from install to first productive workspace, with a measurable focus on reducing activation drop-off
• Write deep-dive guides for complex scenarios such as Docker-in-Docker, air-gapped deployments, multi-region setups, GPU workloads, and enterprise IdP integrations
• Partner with PMs and technical writers to make community-facing docs complete, accurate, and actually usable
• Education partnerships with universities, bootcamps, and hackathon organizers that bring Coder into labs and classrooms
• Community funds for members building useful projects, including home lab setups, educational tools, and open-source integrations
• Home lab licenses that put Coder Premium in the hands of power users and self-hosters who shape community word of mouth
• Platform engineering roundtables with senior practitioners to gather feedback, share roadmap context, and build lasting relationships
• Bounty programs that reward high-value contributions to the registry, docs, or core tooling
• Create end-to-end tutorials for real workflows, including migrating from local development to Coder, setting up AI coding agents, and running ephemeral PR environments
• Build and maintain a library of reference deployments that show best practices for common deployment targets
• Turn repeated questions into durable resources that help the next user move faster

Requirements:

• A software or platform engineering background. You've written code, managed servers, and troubleshot technical systems
• Strong practitioner empathy. You can meet developers, platform engineers, self-hosters, and enterprise users where they are
• Willingness to travel up to 20%
• A tinkering mindset. You look for ways to improve, automate, and simplify, then act on them
• PM-like pattern recognition. You can spot recurring signals in community feedback, prioritize what matters, and route insights to the right teams
• Bias for action. When something is broken or missing, you fix it. When ownership is unclear, you clarify it fast
• Experience participating in technical communities, whether as an active contributor, quiet observer, moderator, or maintainer
• Strong technical writing. You can turn a complex process into something a busy platform engineer will actually finish
• Comfort using tools that scale your impact, including LLMs, automation, and scripting, without automating away the human presence that makes a community worth joining
• Experience speaking at conferences, running workshops, or building an audience around technical content
• Experience as a community moderator, support engineer, maintainer, or trusted technical presence in an active community
• A recognizable presence in a technical community such as open source, platform engineering, self-hosting, or infrastructure
• Familiarity with Coder or other remote development environment tools, including Gitpod, DevPod, or GitHub Codespaces
• Prior work on a developer-facing open-source project with an active user community
• Exposure to enterprise platform engineering concepts such as SSO, SAML, Vault, Artifactory, and internal developer portals