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.

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 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.

Bonus tacos if you have

• 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.

How you’re measured

Open source is fundamental to Coder’s business model. A meaningful share of our ARR traces back to practitioners who started on OSS and brought Coder Premium into their organizations, so we track how community investment supports adoption, engagement, and revenue.

Our north star is highly engaged OSS deployments: open-source instances with 20 or more active users. Your work should connect back to that outcome, either directly or by building the foundation that gets us there.

Tangible metrics include:

• Deployments at scale: OSS instances with 20 or more active users.

• Weekly installs and activation rate: whether new users reach a first successful workspace.

• Community messages and engagement mix: total volume, help requests, feedback, showcases, and ideas.

• Champions: named, active community members we can identify by company, contribution, and relationship.

• Registry and docs health: contributor growth, time to merge, content reach, and organic search traffic.

We also look for signs that do not fit neatly into a dashboard:

• We know our most active community members by name, where they work, and what they’ve built.

• Sellers want to attend OSS events because they see the relationships and pipeline those events create.

• Engineers ask how to make product decisions better for OSS without waiting for a prompt.

• Programs you own are running, growing, and producing outcomes worth the investment.

About Coder

Coder is an AI software development company leading the future of autonomous coding. We empower teams to build software faster, more securely, and at scale through the collaboration of AI coding agents and human developers. Our mission is to make agentic AI a safe, trusted, and integral part of every software development lifecycle.

Our self-hosted AI Development Environment is the foundation for deploying agentic AI in the enterprise. It provides a secure, standardized, and governed workspace to deploy autonomous coding agents alongside human developers, accelerating innovation while maintaining control and compliance. Coder's isolated, policy-driven environments improve productivity, cut cloud costs, and reduce data risks. Developers transition to AI at their own pace using their own tools. Platform and security teams can govern, audit, and manage a great developer experience at scale.

Interview process 

We believe that the interview process should be transparent, consistent, and enjoyable. We value your time and hope to complete the interview process in two to four weeks, if schedules allow. Through your interviews, you will meet a mix of individual contributors, managers, and senior leaders.

AI use during the interview process

As an AI company, Coder embraces the use of AI tools, and we want to be transparent about our expectations as you navigate our interview process.

Not permitted: Using AI assistance during conversational interviews.

Permitted: Using AI tooling for take-home assessments. Please flag where and to what extent it was used in your take-home. Your submission will not be penalized for using AI as long as it is done honestly.

Our use of AI in hiring

We use AI tools to help manage our recruitment process efficiently and fairly. Specifically:

• Ashby helps us review inbound applications by surfacing candidates who best match the role requirements we've defined. This tool does not make hiring decisions - it helps our team prioritize which applications to review first.

• Granola takes notes during our interview calls so our team can focus on the conversation with you.

All hiring decisions are made by humans. Our team reviews applications, conducts interviews, and makes final selections. AI tools assist us but never replace human judgment, and these practices are conducted in compliance with applicable data protection, AI governance, and labor laws. Your data is not used to train AI models.

In accordance with New York City Local Law 144, an independent bias audit has been conducted on "Automated Employment Decision Tools"; results are available for Ashby.

If you're applying for a role at Coder and have questions about how we use AI in our process, or if you'd like to request information about the data we collect, please contact careers@coder.com.

Coder is a proud Equal Opportunity Employer

We are committed to providing equal employment opportunities to qualified applicants and do not discriminate on the basis of race, color, ancestry, religion, sex, pregnancy, gender, gender identity, gender expression, sexual orientation, national origin, age, marital status, genetic information, disability, protected veteran status or any other characteristic protected by federal, state, or local laws.