Developer Relations Lead

About the role

The role establishes community norms and drives engagement so engineers adopt Flux for hardware design. It converts recurring support themes into durable learning resources and represents Flux externally to accelerate trust. This position reports to the COO and operates at the start of the product journey.

Key facts

What you'll do

Community norms are defined, moderated, and expanded to guide behavior and expectations for power users and VIP customers. Engagement grows through targeted outreach, events, and ongoing conversations that keep the community active and informed.

Recurring questions are synthesized into durable artifacts such as improved documentation, tutorials, FAQs, reference projects, and runnable examples. These artifacts reduce repeated support load and give engineers a clear path to successful usage.

The product education roadmap is owned across documentation, interactive walkthroughs, tutorials, and example designs to guide new users. Content is structured to match how engineers learn and progress with the platform.

Feedback from updates flows back into the content so instructions stay current and reliable.

These stories demonstrate practical outcomes and help engineers evaluate the platform.

This alignment helps prioritize fixes and improvements based on real usage.

Hardware advocates and creators receive clear briefs and quality standards, enabling them to produce high-quality content without direct management. Guidance maintains technical credibility while scaling influence.

Requirements

Prior experience in DevRel, technical community, solutions engineering, technical marketing, or a closely related role for technical users is required.

Credible technical depth is required, ideally with hands-on exposure to PCB workflows in professional or serious hobbyist contexts. Understanding of design, fabrication, and assembly constraints is necessary.

Strong writing and content structuring skills are required, especially for documentation, tutorials, and learning paths that guide users step by step. Clarity and scannability are essential for busy engineers.

Comfort being public-facing is required, including running community motions, talking to customers, and representing Flux at events and in communications. Confidence in live settings supports community growth.

Ability to build lightweight systems from scratch is required, covering tagging, measurement, content pipelines, and feedback loops.

High ownership, bias to action, and good judgment in ambiguous environments are required. Decisions are made with incomplete information while maintaining quality and direction.

Nice to have

Experience building or migrating communities across platforms such as Slack and Discourse is preferred. Track records of sustained engagement demonstrate ability to retain active participants.

Experience owning documentation as a maintained product surface using Mintlify or similar tools is preferred. Update workflows tied to product changes help keep public materials synchronized.

Experience creating technical case studies or customer stories grounded in real workflows is preferred. Evidence of impact makes narratives persuasive for similar prospects.

Background in PLG developer tools or products sold to technical audiences is preferred. Familiarity with developer onboarding and conversion patterns supports effective storytelling.

Prior work with hardware startups, makers, robotics, embedded, or adjacent ecosystems is preferred. Exposure to constraints and best practices improves credibility with technical users.

Experience working with advocates, creators, or influencer-style partners while maintaining technical credibility is preferred. Partnerships expand reach without compromising depth.

Skills & tools

Technical communication platforms such as Mintlify, ReadMe, or similar shape structured documentation. Version control and publishing workflows keep content aligned with releases.

Community tools like Discord or forums host discussions, onboarding, and ongoing engagement. Analytics platforms measure participation and content effectiveness.

Content creation tools including video, static site generators, and presentation formats support multi-format learning. Reusable components reduce redundant effort.

Practical notes

US authorized work authorization is required for this role. The position is based in the San Francisco Office with regular onsite presence expected.