Developer Relations Lead

Flux is taking the hard out of hardware, by developing the first AI Hardware Engineer. Our goal is to democratize the ability to create bleeding edge hardware, and revolutionize how electronics are designed and built around the world.

Flux is building the default starting point for hardware design. We are hiring a Developer Relations Lead to own community, product education, and customer-driven technical storytelling so engineers can learn Flux, trust it, and succeed without heavy support. This is a 0 to 1 role reporting to the COO.

• →

  Own the community: set norms, moderate, drive engagement, and build relationships with power users and VIP customers

• →

  Turn recurring questions into durable artifacts: docs improvements, tutorials, FAQs, reference projects, and examples

• →

  Own the product education roadmap across docs, walkthroughs, tutorials, and example designs

• →

  Lead a docs refresh (including Mintlify) and build a sustainable system to keep docs accurate as the product evolves

• →

  Create credible technical storytelling: case studies, customer workflows, and “how teams actually use Flux” narratives

• →

  Build the feedback loop from customers and community into Product and GTM so recurring friction gets fixed over time

• →

  Guide hardware advocates and creators with clear briefs and quality standards (initially leading without direct management)

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

• Credible technical depth, ideally with real exposure to PCB workflows (professional or serious hands-on)

• Strong writing and content structuring skills, especially for docs, tutorials, and learning paths

• Comfort being public-facing: running community motions, talking to customers, and representing Flux externally

• Ability to build lightweight systems from scratch: tagging, measurement, content pipelines, feedback loops

• High ownership, bias to action, and good judgment in ambiguous environments

• Experience building or migrating communities (Slack to forums like Discourse) and driving sustained engagement

• Experience owning docs as a maintained product surface (Mintlify or similar), including update workflows tied to product changes

• Experience creating technical case studies or customer stories grounded in real workflows

• Background in PLG developer tools or products sold to technical audiences

• Prior work with hardware startups, makers, robotics, embedded, or adjacent ecosystems

• Experience working with advocates, creators, or influencer style partners while maintaining technical credibility