Robotics Systems Engineer

About the role

This role focuses on integrating and validating hardware and software for home robots. The position contributes to system architecture and manufacturing processes for consumer robotics products.

Software engineers turn product ideas into working code. Engineers work in small teams, review each other's work, and ship in small batches. Most teams follow agile practices such as sprints and daily standups. Engineers also write tests, fix bugs, and improve performance. The field values clear communication as much as technical skill. Engineers spend part of every week on planning, code review, and debugging, not just writing new code. The ability to explain a technical decision in plain words separates strong engineers from the rest.

Key facts

What you'll do

System integration tests validate robotic actuation and perception hardware to ensure reliable performance in home environments. Cross-disciplinary faults in mechanical, electrical, firmware, and software layers are diagnosed and resolved to stabilize prototype units. Sensor and actuator bringup activities evaluate component behavior, confirming that hardware meets functional expectations. Motor and sensor drivers alongside Python and C++ tooling are maintained to support development and production workflows. Robot assembly procedures, bringup routines, QA tests, and troubleshooting methods are documented to create repeatable processes.

Requirements

More than 3 years of experience with complex robotic or electromechanical systems is required. Proficiency in Python or C++ is required for maintaining codebases and debugging integration issues. A strong system-level understanding of robotics hardware, firmware, and software layers must be demonstrated. Routine use of standard diagnostic tools such as oscilloscopes, multimeters, and logic analyzers is expected. Development and execution of test plans and procedures for electromechanical systems are required.

Nice to have

Deep experience with protocols including CAN, Ethernet, USB, MIPI, and GMSL is valued. Experience with quasi-direct-drive actuators is preferred. Calibration experience for computer vision systems is a nice-to-have skill.

Practical notes

This role is based in Redwood City, CA, and operates in a full-time capacity. The team is small and cross-functional, with a focus on consumer robotics. Typical interview steps

Hiring for engineering roles usually starts with a recruiter screen, followed by one or two technical rounds. Candidates often solve a coding problem, discuss past projects, and answer system design questions. Some loops include a take-home task. Final rounds typically cover team fit and give candidates a chance to ask questions. Interviewers look for how you break down an unfamiliar problem, not just whether you reach the answer. Practicing a few problems aloud and reviewing your own past projects are the best preparation.

Good to know

Work in this field involves real-world data and large-scale data collection. Robotics stack development spans perception, actuation, and system integration. Early team members influence product direction and manufacturing processes. The role emphasizes safety, reliability, and performance for household deployment. General knowledge of diagnostic tools and test procedures supports effective system validation.

Questions to ask

Worth asking in any interview: how the team measures success, who the role works with daily, what the onboarding looks like, and what the company is trying to achieve this year. Asking what past hires did well is a strong final question. Keep the list short and pick the questions that matter most to you.

Career growth

Engineering careers usually progress from individual contributor to senior, staff, and principal levels. Some engineers move into management and lead teams of five to twenty people. Others stay on the technical track. Growth follows demonstrated impact, not tenure alone. A typical engineering ladder has clear levels with defined expectations for scope, quality, and mentorship. Moving up usually requires owning outcomes end to end rather than completing assigned tickets.