What are the responsibilities and job description for the Developer Relations Lead position at Dexmate?
About Dexmate
Dexmate is building the platform for physical AI — general-purpose humanoid robots and the full-stack infrastructure powering them. Our mission is to make physical AI accessible to every developer, the way cloud computing made software infrastructure accessible to everyone before it. We're now building the developer ecosystem that turns our product momentum into a movement.
The role
You'll be our Developer Relations hire and the architect of everything community. This is a senior IC role with a mandate to build a team.
What You'll Do
Dexmate is building the platform for physical AI — general-purpose humanoid robots and the full-stack infrastructure powering them. Our mission is to make physical AI accessible to every developer, the way cloud computing made software infrastructure accessible to everyone before it. We're now building the developer ecosystem that turns our product momentum into a movement.
The role
You'll be our Developer Relations hire and the architect of everything community. This is a senior IC role with a mandate to build a team.
What You'll Do
- Set the vision and execute the community strategy — programs, channels, metrics, and rituals that attract robotics developers, AI researchers, students, etc.
- Write and publish technical content: tutorials, integration guides, architecture teardowns. Ship real code. Publish under your name.
- Be the developer's voice inside the company — own the feedback loop from community friction to product roadmap.
- Design and run hackathons, workshops, developer days, etc.
- Hire and grow the DevRel team starting with a Developer Advocate in Month 4
- Technical depth in robotics or adjacent systems — control, planning, simulation, edge compute, physical AI, etc.
- Real code you can point to: SDK integrations, sample apps, open-source contributions in robotics or AI
- 5 years in developer relations, solutions engineering, or technical advocacy — with time actually building a community, not adjacent to one
- Strong writer. You know the difference between a tutorial and a reference doc and you care about both.
- Builder mentality. No playbook exists. You'll write it.
- Based in or willing to relocate to the Bay Area — robots are physical, you need to be on-site.
- Prior 0-to-1 community build
- Open-source project with real traction
- Physical AI or embodied AI background
- Conference speaker
- University research network