> Markdown version of [/jobs/ext/4621377-member-of-technical-staff-robotics-systems-engineer](https://www.wearedevelopers.com/jobs/ext/4621377-member-of-technical-staff-robotics-systems-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).

---

# Member of Technical Staff, Robotics Systems Engineer

- **Company:** INDUSTRIAL NEXT INC.
- **Location:** San Francisco, CA, United States
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Systems Engineering, Network Interface Controllers, Firmware, Python (Programming Language)
- **Published:** November 7, 2026
- **Apply:** https://www.juju.com/job/28_25303_c51129c36359c4fbe2cf311b8ddd7b56

## About the Role

* Education. BS in ME, EE, or Robotics; equivalent industry depth. Strong expertise in two of mechanical, electrical, or software to specify and review the others.
 * Experience. 8+ years shipping robotic or hardware systems to paying customers. Has driven a product end-to-end - defined the architecture, qualified the vendors, drove integration, and shipped it through customer acceptance.
 * Multi-discipline systems depth. Has authored real interface control documents and architecture specs across mechanical, electrical, firmware and software, not just reviewed them.
 * Decides at 70% information. Can frame and resolve a real architecture decision under uncertainty and ship the answer in days. Makes and defends architectural calls before all the data is in. Does not require gated review boards to move.
 * Vendor management. Has run RFQ to sample to qualification to second-source for components that mattered; signed contracts, owned the relationship, caught real defects.
 * V-model systems engineering, startup-adapted. Has run requirements, design, integration and verification on real hardware without being slowed by gated review boards.
 * Reads code. Python / C++ / ROS-level fluency. Can drill into perception, motion, or controls when subsystems disagree.
 * Customer-facing technical relationship. Has run joint planning, milestone management, and escalation with customer engineering at the technical level.

Strongly preferred

 * Robotics-systems-engineering experience at a humanoid or hardware-shipping robotics company.
 * Industrial robotics, factory automation, or manufacturing customer domain.
 * Factory Acceptance Test / Site Acceptance Test design.
 * Mobile manipulator, wheeled humanoid, or station-based robotic system integration.
 * Has sourced critical components under schedule pressure.
 * Has run multi-customer programs sharing one architecture and one stack.
 * Industrial robot safety standards and functional-safety / hazard-analysis experience.

## Description

Role: Member of Technical Staff, Robotics Systems Engineer

Why this role matters

We're building one robotic system - a shared stack that scales across embodiments and customers. Holding that product together as it scales is a multi-disciplinary problem: requirements, architecture, interfaces, vendor decisions, integration plan, and acceptance criteria all have to converge on time across mechanical, electrical, firmware, software, and sensors. We need someone who can drive the system's technical architecture across all of that, hold the product picture across programs, and keep it coherent as we add embodiments and customers. Customer programs are the proving ground that hardens the product, not the source of one-off specs. As part of a small, fast-growing startup, you will be expected to also own the product up to deployment and serve the TPM role as well.

What you'll do

 * Drive system architecture, requirements, and interface definitions across mechanical, electrical, firmware, software, and sensors as the product scales across embodiments and customers.
 * Drive vendor selection and qualification for various components to integrate into the system, e.g. cameras, arms, end-effectors, controllers, motors, and sensors.
 * Define integration and acceptance criteria, and partner with deployment so customer programs harden the product rather than fork it.