> Markdown version of [/jobs/ext/3070028-robotics-hardware-engineer](https://www.wearedevelopers.com/jobs/ext/3070028-robotics-hardware-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Robotics Hardware Engineer - **Company:** Dyna Robotics - **Location:** Redwood City, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Computer-Aided Design, BASIC (Programming Language), Software Debugging, Firmware, Reliability Engineering, Hardware Testing - **Published:** September 25, 2026 - **Apply:** https://startup.jobs/robotics-hardware-engineer-reliability-bring-up-dyna-robotics-8963487 ## About the Role * 5-10 years in robotics, mechatronics, hardware test, or reliability engineering, with significant time on early-stage robotic hardware. * Strong benchtop skills (soldering, multimeter, calipers, wire harnesses, basic power tools) and the ability to tear down, repair, and re-commission electromechanical assemblies on your own. * Mechanical intuition: how actuators fail through backlash, wear, preload loss, and end-stop damage, and how to connect physical evidence to design causes. * Proficiency in CAD and Altium, a working understanding of GD&T, and the ability to review drawings. * Firmware and motor control fundamentals: debugging PCBs, quasi-direct-drive actuators, encoders, CAN, and calibration and zeroing. * Working knowledge of state-space robot control and how it behaves on real hardware. * Strong data fundamentals and rigor about evidence (you know what a p-value actually represents). * Experience working cross-functionally with researchers and engineers. Bonus Points For * Robotics startup experience * PCB design * Onshape * Familiarity with simulation * Building tools and SOPs that others actually adopt ## Description We're looking for a hands-on engineer to own the reliability of our humanoid robots through early-stage hardware bring-up and prototyping. The hardware is still taking shape, and that's the point: your findings feed directly into the next revision, and the tools and standards you build now will define how reliability works at Dyna as we scale. One day you're writing a degradation analysis; the next you're pulling an arm off a robot, probing a driver board, soldering a fix, and designing the bracket that makes it stick. You'll work across electrical, mechanical, software, and controls alongside a small team of engineers and researchers who dig into hard problems with you, and you'll be the person they call when a robot does something nobody can explain. This is not a desk job. Expect at least 20% of your time hands-on with hardware, often much more. It's a role for people who enjoy working without a playbook, move fast on their own, and find Type 2 fun in hard, ambiguous problems. What You'll Do * Root-cause failures on prototype hardware. Actuator dropouts, encoder drift, thermal events, CAN faults, and control-stack bugs, separating true hardware issues from firmware, calibration, and model-side causes. * Work hands-on at the bench. Test, rework, and repair actuators and electronics, from soldering and harness work to re-commissioning components on rigs you build yourself. * Design, build, and improve mechanical parts. Create fixtures, jigs, brackets, and robot modifications, and turn evidence about backlash, wear, and preload into concrete design changes with the mechanical team. * Build hardware health monitoring. Develop metrics and alerts that catch real faults, and wrangle telemetry (MCAP, npz, episode archives) from bandwidth-constrained robots. * Develop calibration and test tooling. Build calibration tools with safety gates, characterization sweeps for new hardware revisions, and validation harnesses, and review PRs across firmware, controls, and config. * Document and hand off. Write runbooks, SOPs, and incident reports clean enough that a teammate can pick up the work cold. ## Related Videos - [Robots are coming into the wild! Full-Stack Robotics Engineers, be ready!](https://www.wearedevelopers.com/videos/479-robots-are-coming-into-the-wild-full-stack-robotics-engineers-be-ready) - [Using AI Without Losing Your Skills](https://www.wearedevelopers.com/videos/2045-using-ai-without-losing-your-skills) - [WeAreDevelopers LIVE - Modern DevOps for IoT Devices and More](https://www.wearedevelopers.com/videos/1805-wearedevelopers-live-modern-devops-for-iot-devices-and-more) - [Playing Pong on a shoulder press machine](https://www.wearedevelopers.com/videos/100140-playing-pong-on-a-shoulder-press-machine) - [More efficient software for more efficient microchips](https://www.wearedevelopers.com/videos/1164-more-efficient-software-for-more-efficient-microchips) - [What I learned as a developer from accidents in space](https://www.wearedevelopers.com/videos/642-what-i-learned-as-a-developer-from-accidents-in-space) ## Related Articles - [How software is steering vehicle technology](https://www.wearedevelopers.com/magazine/515-how-software-is-steering-vehicle-technology) - [Is Software Engineering Hard?](https://www.wearedevelopers.com/magazine/448-is-software-engineering-hard) - [Highest Paying Tech Companies for Developers](https://www.wearedevelopers.com/magazine/220-highest-paying-tech-companies-for-developers) - [Top Characteristics of a Software Engineer](https://www.wearedevelopers.com/magazine/166-top-characteristics-of-a-software-engineer) - [What is Software Engineering?](https://www.wearedevelopers.com/magazine/289-what-is-software-engineering) - [Fully Remote Software Engineer Jobs](https://www.wearedevelopers.com/magazine/447-fully-remote-software-engineer-jobs)