Coder is a company that provides a centralized platform for building and running cloud-based software development environments.
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. You’ll curate our template registry, improve community docs and guides, show up in Discord and GitHub, and demo Coder online and in person. You’ll work across product, engineering, marketing, and our open-source community to make every path into Coder clearer, faster, and more useful. Please note that this role is contract-to-hire. What you’ll do here Community and feedback loop A great developer community starts with showing up. You’ll be a technical presence people can trust: helpful, consistent, and able to answer hard questions. - 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. Registry The registry has contributors across Coder and the community. Your role is to keep it healthy, useful, and easy to contribute to. - 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. Conferences, demos, and events DevRel takes many forms. Some work happens on stage; some happens behind the scenes, making sure demos are stable, integrations work, and the right technical story is ready. - 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. Docs and guides PMs own docs for new features. Technical writing owns architecture. You’ll own the community experience: helping platform engineers and self-hosters get from zero to productive without needing to contact Coder. - 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. Community programs Every DevRel engineer owns at least one community program: a repeatable initiative that compounds over time and pulls people deeper into the Coder community. Possible programs include: - 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. These are examples, not a menu. The best program may be one that does not exist yet. Examples and tutorials This work starts with community signals, not internal preference. When users keep hitting the same wall, you’ll help decide whether the fix is a doc update, a script, a template, or a full reference example. - 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. What we’re looking for - 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 tra