Robots are shifting from fenced, single-task machines to systems that sense an unstructured space, decide what to do, and act. This changes the silicon requirements, and many of them show up at the robot level instead: 8 hours of battery life, a safety standard to meet, a bill-of-materials cost ceiling, and a model that was not yet written when the device was specified.
The core of the role is defining the next generation of the company's RZ microprocessor family for robotics and physical AI. You will work with product line management and architecture teams to turn real robot use cases into engineering-grounded product definitions covering device behaviour, the software and reference designs needed around it, and the trade-offs the market will tolerate. The lines span RZ/V devices with an NPU for vision AI, RZ/T and RZ/N devices for real-time and industrial networking, and RZ/G general-purpose MPUs. You will help decide each line's direction and how the three fit together inside one robot.
The job is product engineering with a focus on definition. You will need real technical depth, including benchmarking, building prototypes, and working alongside customer engineers, so that each requirement rests on measured evidence instead of assumptions.
Responsibilities
Write product requirements documents and feature specifications for RZ devices aimed at robotics and physical AI, based on use cases such as autonomous mobile robots, collaborative and industrial arms, humanoid and legged platforms, drones, and service robots.
Start from complete robot architectures and derive device requirements for perception, planning, control-loop timing, motion and motor control, safety and redundancy, thermal and power limits, I/O and connectivity. Decide how compute should be split across RZ/V, RZ/T, RZ/N and RZ/G devices in a system.
Track how robot architectures and software stacks change, from classic perception, planning and control pipelines to end-to-end physical AI and vision-language-action models. Turn those changes into system requirements for RZ covering data flow, timing, latency, safety, and the middleware, runtime and software support customers will need. Work with the AI and architecture specialists to map these onto NPU, CPU and memory choices.
Benchmark current RZ devices and competitor parts on real robot workloads, build proofs of concept, and use the results to set performance targets and name the gaps the next generation has to close.
Talk directly with robotics customers, robot OEMs and ecosystem partners to gather requirements, test concepts, and collect feedback on early specifications and roadmaps.
Define what surrounds the silicon: reference designs, evaluation kits, Linux and RTOS board support packages, ROS 2 support, AI toolchain features and partner software, so customers can move from evaluation to a working robot quickly.
Speak for the robotics customer in trade-off decisions with architecture, design and software teams. When cost, area, power and capability conflict, present a clear, evidence-based view of what the market will and will not accept.
Support launch and go-to-market work with technical positioning, competitive analysis, demos, and lead-customer engagement alongside product marketing and field teams.
Requirements
Required: a degree in electrical, electronic, computer or mechatronics engineering, or an equivalent qualification, plus substantial product engineering, product definition, systems engineering or applications engineering experience with embedded processors or robotics platforms.
Required: 7-9 years of relevant commercial experience.
Required: working knowledge of robotics systems. You should be able to discuss perception pipelines, SLAM, motion planning, real-time and motor control and safety architecture, and know where the hard problems sit.
Required: a working grasp of AI workloads on embedded targets, including model architectures, mapping to accelerators, quantisation, memory bandwidth as the usual limit, and the deployment toolchain.
Required: enough hands-on embedded work with Arm-based MPUs, embedded Linux, RTOS, C/C++ or Python, and benchmarking and profiling to test your own assumptions and earn the trust of architects and customer engineers.
Required: you have written product requirements or specifications that shipped, and you can defend them to executives and to a group of skeptical architects on the same day.
Required: hands-on experience with the company's RZ devices, for example the RZ/V2H, RZ/V2N, RZ/T2H or RZ/G3E.
Familiarity with ROS 2, real-time Linux, heterogeneous multi-core systems, robotics middleware, and industrial Ethernet such as EtherCAT.
Exposure to functional safety in robotics or industrial settings.
Experience building or deploying robots, whether commercially, in research, or as a serious hobbyist.
Experience in semiconductor or embedded processor businesses, including how design wins and long product lifecycles work in practice.
Conditions
Equal opportunity and affirmative action employer; applicants are considered without regard to protected characteristics.
Benefits
A competitive benefits package in addition to salary. Details are shared during the hiring process.