Senior Robotics Systems Integration Engineer

Dyna Robotics builds general-purpose robots powered by a proprietary embodied AI foundation model with top-in-industry generalization and real-world performance. Already deployed with customers across multiple industries, our robots do commercial-grade work in the physical world. Our team comes from Google DeepMind, Meta, and Cruise, and we're backed by CRV, First Round, and other leading investors.

The Role

We're looking for an engineer who will help make our humanoid robot better, not just keep it running. As our fleet grows, the evidence from fielded hardware becomes some of the most valuable input to our design. You'll turn failure data, bench findings, and fleet telemetry into concrete guidance for the mechanical, firmware, and controls teams as they iterate on the next generation of the system.

You'll sit at the intersection of hardware, firmware, controls, and data infrastructure. Your expertise will shape design decisions, from actuator selection and joint limits to calibration strategy and validation criteria, and you'll be a trusted voice in design reviews. You'll also be the person the team turns to when a robot does something nobody can explain, and you'll be comfortable getting directly on the hardware to find out why.

What You'll Do

• Root-cause complex failures across the fleet. Actuator dropouts, encoder and calibration drift, thermal events, CAN bus faults, and control-stack bugs, separating genuine hardware degradation from firmware, calibration, and model-side causes.

• Validate and repair hardware. Bench-test suspect actuators and electronics, perform rework and repairs, and run physical validation with test fixtures and boot and power-cycle rigs.

• Design and build supporting mechanical pieces. Take test fixtures, jigs, brackets, mounts, and small modifications to fielded robots from concept through fabrication, whether 3D printed or through the shop or a vendor.

• Turn mechanical evidence into design changes. Reason from your data about backlash, windup, gear wear, preload, and hard-stop behavior, and feed that back as concrete recommendations. The mechanical team owns major structural design and simulation, so you'll partner closely with them and with vendor models and joint-limit specs.

• Build and roll out fleet health metrics. Maintenance indices, hold-current precursors, backlash and deadband tracking, and bus-error monitoring, with alert rules tuned to fire on real faults rather than noise floors.

• Develop calibration and test tooling. Calibration tools with safety gates, characterization sweeps for new hardware revisions, and pre-merge validation harnesses for firmware and software changes.

• Wrangle robot telemetry at scale. Extract and decode logs (MCAP, npz, episode archives) from bandwidth-constrained robots, close gaps in the telemetry pipeline, and build the monitoring that should have existed already.

• Write things down and hand them off. Runbooks, SOPs, incident reports, and handoff packages clean enough that a teammate can pick the work up cold.

• Review PRs and propose fixes. Across firmware defaults, control code, and deployment configuration, catching interaction bugs between calibration tools, boot checks, and safety gates.

What You'll Bring

• 5-10 years in robotics, mechatronics, hardware test, or reliability engineering, with significant time on fielded hardware rather than lab prototypes.

• Practical bench skills (soldering, multimeter, calipers) and the ability to tear down, repair, and re-commission electromechanical assemblies independently.

• An understanding of how actuators fail mechanically, including backlash, wear, preload loss, and end-stop damage, and the ability to connect physical evidence to design causes. You won't be doing large structural design or FEA, but you should hold your own in a design review.

• Working knowledge of robot control: impedance and torque-controlled actuators, force-control parameters, and controller state lifecycles (boot, e-stop, reconnect). Enough to tune deployed behavior and recognize when a "hardware" fault is actually a controls bug. You do not need to design controllers from scratch.

• Strong Python for data analysis and tooling, plus solid time-series and signal-statistics instincts around noise floors, drift, persistence rules, and spotting when an alert is just a tiny denominator.

• Fluency with actuators and motor control: quasi-direct-drive systems, encoders, torque and current telemetry, CAN, and calibration and zeroing procedures.

• Experience with observability stacks (Datadog or similar) and git and PR-based workflows.

• Rigor about evidence. You distinguish measured from commanded and correlation from cause, and you will not ship a conclusion or set a baseline on contaminated data.

• The communication skills to influence design direction: you can bring data to a design review and make a clear, well-supported case.

Bonus Points For

• Experience with teleoperation systems, VR interfaces, or data-collection fleets.

• Prior work on hardware qualification (EVT, DVT, PVT) or manufacturing and incoming test.

• Simulation sanity-checking in MuJoCo.

• A track record of building tools and SOPs that other engineers actually adopt.

AtDyna Robotics, we build technology for the real world, which requires a team as diverse as the environments our robots inhabit. We are an equal opportunity employer committed to technical rigor and mutual respect.

Don’t let a checklist stop you. Data shows that underrepresented groups often only apply if they meet 100% of the criteria. We value problem-solving and grit over keyword matching. If you’re passionate about robotics, no matter your discipline, we want to hear from you, even if you don't check every box.