Robots are shifting from caged, single-task machines to systems that sense an unstructured space, decide what to do, and act on it. This changes what the silicon has to deliver, and many requirements come from the robot rather than from a chip spec: 8 hours of battery life, a safety standard to meet, a bill-of-materials target, and a model that did not exist when the device was defined.
The core of the role is defining the next generation of the Renesas RZ microprocessor family for robotics and physical AI. Working with product line management and architecture teams, you will turn real robot use cases into engineering-grounded product definitions covering device behaviour, the software and reference designs around it, and the trade-offs the market will accept. The scope spans RZ/V vision AI devices with NPU, RZ/T and RZ/N real-time and industrial networking devices, and RZ/G general-purpose MPUs, and you will help decide each line's direction and how they fit together in one robot.
This is a product engineering role focused on definition. You will need real technical depth: benchmarking, prototyping, and working alongside customer engineers, so requirements rest 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 including 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 budgets, I/O and connectivity, and how compute splits across RZ/V, RZ/T, RZ/N, and RZ/G devices.
Track how robot architectures and software stacks are changing, from classical perception, planning, and control pipelines to end-to-end physical AI and vision-language-action models. Turn this into system requirements covering data flow, timing, latency, safety, and the middleware, runtime, and software stack customers will need. Work with the AI and architecture specialists to map these onto NPU, CPU, and memory decisions.
Benchmark current RZ devices and competitors on real robot workloads and build proofs of concept. Use the results to set performance targets and to identify gaps the next generation must close.
Work 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 BSPs, ROS 2 support, AI toolchain features, and partner software, so customers can move from evaluation to a working robot quickly.
Represent the robotics customer in trade-off discussions with architecture, design, and software teams. When cost, area, power, and capability conflict, present evidence on what the market will and will not accept.
Support launch and go-to-market 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 experience in product engineering, product definition, systems engineering, or applications engineering for embedded processors or robotics platforms.
Working knowledge of robotics systems: perception pipelines, SLAM, motion planning, real-time and motor control, and safety architecture, including where the hard problems sit.
Working knowledge of AI workloads on embedded targets: model architectures, mapping to accelerators, quantisation, memory bandwidth as the usual bottleneck, and the deployment toolchain.
Enough hands-on embedded experience with Arm-based MPUs, embedded Linux and RTOS, C/C++ or Python, and benchmarking and profiling to test your own assumptions and earn the trust of architects and customer engineers.
Experience writing product requirements or specifications that were built and shipped, and the ability to defend them to an executive audience and to sceptical architects on the same day.
Hands-on experience with Renesas RZ devices, for example 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 a robotics or industrial context.
A background building or deploying robots, commercially, in research, or seriously as a hobbyist.
Experience in semiconductor or embedded processor businesses, including how design wins and long product lifecycles work in practice.
Conditions
Equal opportunity employer; applicants are considered without regard to protected characteristics.
Benefits
A competitive benefits package alongside salary; details are provided during the hiring process.