Robotic Systems Engineer
Robotic Systems Engineer
Posted today
SENIORITY
Lead
About the role
- Integrate new robot arms, haptic devices, teleoperation rigs and sensors into reliable software stacks used by research and deployment teams
- Build infrastructure for deployed robots, keeping round-trip latency under 200ms across hundreds of miles
- Debug hardware-software problems across drivers, communication protocols, calibration and physical hardware
- Build the software interfaces that connect hardware to ML training and data pipelines
- Work with the ML and hardware teams to get new hardware capabilities into production fast
- 1 - 8 years of experience, including 2+ years integrating hardware into software stacks
- Strong software engineering with embedded systems and hardware SDKs (this is essential)
- You've integrated robots, sensors or hardware into production systems (this is essential)
- Real-time systems experience where the output can't stall
- Own a critical layer: you'll sit between the hardware and the AI, at the heart of the product
- Early and well funded: join a small team at the start, with competitive equity
- Real robots, real deployment: your work runs on physical machines in industry
- Visa support: transfers and new sponsorships welcome (H-1B, OPT, TN)6 days a week on-site in San Francisco
Before you apply
Applying takes about a minute. These four things decide how fast it moves after that.
Your profile is current
It's what we read first. Occupations, seniority and locations matter more than a long history.
Two examples you can talk through
Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.
A number in mind
What you're on now and what would make you move. We negotiate better when we know both.
Your notice period
Employers plan around it, and it's the question that stalls offers most often.
Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.
