Developer Relations Lead

About Dexmate

Dexmate is building the foundation for physical AI — combining a new generation of robots with a universal Physical AI OS, making robots as easy to build and deploy as software. Today, robotics is fragmented, slow, and closed: most builders are forced to reinvent the same stack again and again, and most ideas never make it past the prototype stage. We exist to change that. Our mission is to democratize robotics by lowering the barrier to entry, delivering a plug-and-play platform for developers, researchers, and enterprises, and cultivating an open ecosystem that accelerates the evolution of physical AI. If you want to help shape the next layer of human capability — and believe the future of robotics should be built together, not in isolation — we'd love to build it with you.

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

Who you are

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

Strong bonus:

• Prior 0-to-1 community build

• Open-source project with real traction

• Physical AI or embodied AI background

• Conference speaker

• University research network
  

If you think the best robotics platform wins by having the best builders on it — come build the community.