Report number: MTF-CF-RR-2026-10-12-ROBOT-PM
Author: MTF Institute Research Team
Independent review: MTF Institute Research QA
Evidence date: 12 October 2026
Geography: United States, United Kingdom, Germany and Canada, reported separately

Executive summary

This study examines 33 current employer-owned requisitions for robotics and embodied-autonomy product work that were individually read and coded on 12 October 2026. The principal country attribution is 24 United States, three United Kingdom, three Germany and three Canada. They come from 23 employer groups. Bounded searches in the four declared countries did not yield 100 suitable current vacancies, so the study reports the smaller verified sample with its country and sector limits. It is a structured purposive study of advertised work, not a representative survey, a measure of national hiring prevalence or a forecast.

The strongest common thread is product decision work, not robot programming. The reviewed postings describe identifying a customer's problem, deciding which use case and segment to serve, defining a product roadmap and requirements, resolving hardware-software tradeoffs with specialists, asking for field evidence, and connecting a release to adoption or commercial results. Individual jobs combine those activities differently. Path Robotics links industrial robot discovery to MVP and commercialization. Standard Bots asks a product manager to turn site visits and prototypes into specifications and strategy. Piaggio Fast Forward explicitly spans consumer and industrial robot lines. These are source-linked examples, not claims that every robotics employer uses the same operating model.

The sample has material concentration and sector limits. Six U.S. requisitions are from Apptronik, three Canadian requisitions are from Vention, and all three UK-attributed roles concern autonomous road or airport equipment. Six road/airport roles across the full study are retained because they have real product authority over physical autonomous machines, but their specialized markets cannot be generalized to home or factory robots. Removing them leaves 27 consumer, industrial, field or robot-platform roles: 21 U.S., three German and three Canadian, with no UK role in that narrower view. Two surgical-robot positions and three German defense positions were kept only as separately labelled context, outside the 33. No four-country prevalence rate is calculated.

ROS 2 is important technical context for product integration, yet the accepted-role coding did not identify an explicit ROS 2 requirement in the retained minimal excerpts and coded fields. This is a bounded observation about the study record, not proof that the technology is absent from every full job page. A German defense-context product posting held outside the principal denominator does explicitly name ROS2 programming. A product manager can still need to ask about a robot's supported ROS distribution, interfaces, compatibility tests, update ownership and field evidence; recent Open Robotics and Robotiq releases supply ecosystem context. The principal vacancy evidence does not support presenting hands-on ROS 2 development as a general hiring requirement.

Research question and eligibility

The question is: What duties, outputs, hard and behavioral skills, tools, qualifications, work rhythms, interfaces and decision boundaries appear in a verified cross-sector sample of current robotics product-management vacancies in the four declared countries? The United States was the first declared geography. After several lawful source passes found substantially fewer than 100 suitable U.S. roles, a four-country design was declared before non-U.S. collection. The United States, United Kingdom, Germany and Canada were searched as separate strata. The verified sample remained smaller than 100; findings are limited to these observed roles and reported separately by country.

A posting entered the principal sample only when an individual current employer page or employer-controlled applicant system showed an applicable work location, role details and an application path, and the duties showed substantive product decision authority. Eligible products are physical robots, autonomous machines or software/hardware platforms that directly configure, control, deploy or support them. The role needed observable responsibility for several of customer or use-case discovery, product vision, requirements, roadmap, technical tradeoffs, launch or commercialization, deployment evidence and lifecycle measures. Merely working at a robotics company did not qualify a generic software, sales, product-marketing, operations or engineering job.

The study excluded closed and redirecting postings, unreadable search snippets, foreign-only roles, repeated requisition IDs, and positions whose primary work lacked product ownership. A product title alone was insufficient. Multiple office locations on one requisition counted once. A posting open in more than one declared country also counted once under one primary country attribution, with all eligible locations recorded. German pages were coded from their original employer text with short English translations where needed. Where a posting did not state a preferred qualification, daily cadence or approval route, the code is not stated, not an inferred absence.

The full discovery inventory contained 75 unique requisition candidates from several source passes. Detailed second-pass review concentrated on 45 high-fit candidate identities; 33 met the principal role and direct-page tests, 11 were retained only for comparison and one was excluded. The other discovery records are not silently promoted into the report's denominator. Duplicate observations were removed by employer and requisition identity, including alternative ATS paths and cross-country locations. Every retained principal record has its own source URL, retrieval date, live-status observation, brief excerpt, country attribution and coded requirement fields. The source index below lets a reader check the retained requisitions without copying their full job descriptions.

Sample profile and concentration

Primary country attribution Requisitions Employer groups Main boundary
United States 24 17 Six Apptronik roles; includes specialist vehicle and robot-platform products
United Kingdom 3 2 All three are autonomous road or airport equipment roles
Germany 3 3 Autonomous cleaning, humanoid/robot platform and robot tooling
Canada 3 1 All three are Vention product-line or application roles
Unique study inventory 33 23 No pooled national prevalence estimate

The 33 are distinct advertised jobs, not 33 independent companies. Apptronik contributes six different U.S. requisitions across simulation, human-robot interaction, hardware, teleoperation and applied AI product responsibilities. They show how one employer distributes product work, but repeated company practice is not six independent confirmations of an industry-wide rule. Vention's three Canadian roles similarly describe one company's hardware, programming and application portfolio. A one-requisition-per-employer sensitivity reduces the inventory to 23 employer observations. It is a concentration check, not probability weighting or a replacement denominator for country-wide inference. In Canada it leaves one employer, so no conclusion about Canadian employers generally follows.

The sector sensitivity is equally important. Six physical autonomous road or airport-machine roles meet the broad predeclared product definition, and their generic PM decisions inform the sample. They do not show how a domestic vacuum is priced, how a factory cobot is installed or what local approval a public-road vehicle needs. Excluding those six leaves 27 roles across the U.S., Germany and Canada; the UK stratum falls to zero in that narrower device view. A report that hid this change would overstate the breadth of UK consumer or industrial robotics evidence.

What product managers are asked to decide

Choose a problem and buyer. Several roles make discovery a continuing activity rather than a one-time feature request. The Path Robotics product manager connects customer and application discovery to commercialization of robotic welding. Piaggio Fast Forward's product manager has to prioritize both consumer and industrial product lines. A home-following cargo robot and an industrial mobile carrier share technology, but their buyer, purchasing route, service expectations and acceptable friction differ. A useful product output is a bounded opportunity statement naming the user, job, environment, baseline alternative and evidence needed to advance.

Turn market needs into a coherent product. Standard Bots requests discovery and engineering-ready specifications for a robot platform. NEURA Robotics and Vention show product-line work that reaches from market and customer inputs into roadmap and application choices. The product manager need not design a motor or write the control stack to make a consequential tradeoff. The professional work is to state which capability is promised, where the operating boundary lies, which alternatives were rejected, what validation is necessary and who can approve a change.

Coordinate hardware and software as one offer. The Skydio Dock Hardware Platform role connects physical dock, drone, firmware, vision and unattended deployment in one product remit. Viam's platform role centers APIs and SDKs that configure and control robots. Nimble Robotics' cloud-logistics role connects software with a robotic fulfilment system. These are distinct products and levels of technical ownership, but all expose an interface question: what combination of device, software, customer environment and support configuration is actually tested? A decision record or acceptance matrix can make version dependencies, failure handling and ownership visible.

Prove readiness beyond a demo. Third Wave Automation makes autonomous-forklift product requirements and field trials part of a technical PM remit. Ambi Robotics connects product choices to integration, deployment and customer outcomes. A product decision needs an agreed test situation, baseline, fault and recovery observations, acceptance criteria and a handoff from product development to field/service owners. The exact site and safety approval remains a specialist and employer-specific matter.

Close the commercial loop. The reviewed roles include pricing, business case, partner or launch decisions in some postings, but those responsibilities are not universal. Path Robotics explicitly links product development and commercialization; Piaggio Fast Forward spans consumer and enterprise product choices; Würth's end-of-arm role evaluates market potential and partners. A plausible commercial work product states the target segment, total customer workflow, deployment and support costs, pricing/packaging hypothesis, partner responsibilities, measurement plan and the evidence that would change the launch decision. It should not extrapolate a national sales opportunity from this vacancy sample.

Skills, levels and work rhythm

Hard skills in this sample are applied to decisions: customer and market research, product requirements, prioritization, hardware-software integration literacy, field testing, KPI design, launch planning and business reasoning. The specific named technology varies. Some roles expect deep robotics hardware or autonomy experience; others center a directly connected developer or fleet platform. A generic “must code ROS 2” requirement is not supported by the accepted-role coding. The independent dated technology corpus describes recent ROS 2 ecosystem changes; it does not convert them into a vacancy prevalence claim.

Behavioral expectations are observable. Product professionals gather evidence from customers and field teams, translate technical limits into choices, explain tradeoffs to engineering and commercial partners, resolve unclear ownership and bring a decision to the person with authority. Apptronik's product leadership postings illustrate multiple cross-functional interfaces inside one employer; Vention's application role connects product decisions with customer use and deployment. These are more teachable than abstract labels such as “excellent communication” because they can be practiced as a customer interview, requirement review, decision memo or launch-readiness meeting.

The sample skews toward experienced positions. A title such as senior, staff, principal or director is not evidence that the employee may independently authorize a safety control, regulatory position, spend or deployment. Only stated responsibilities and approvals were coded. The individual pages often specify lifecycle activities such as discovery, prototype, launch and support, but few define a daily or weekly routine and most do not state a detailed escalation route. Those missing facts cannot be filled by inference from job titles. An employer's product governance, engineering process, safety specialists, operations and country-specific market-access owners determine the real decision boundary.

Country-specific interpretation

United States. The 24 U.S.-attributed roles span industrial, field, consumer/industrial, robot-platform and specialist autonomous-vehicle work. Examples from Path Robotics, Standard Bots, Apptronik, Skydio and Piaggio show multiple product settings. The six Apptronik requisitions and software-platform edge roles matter to interpretation. This is not a representative U.S. occupation or market-size survey.

United Kingdom. The three UK-attributed roles come from Wayve and AeroVect and concern autonomous-driving or airport ground-equipment products. Their customer, vehicle and field decisions can inform a comparison of embodied-product management. They do not establish a UK consumer-robot or factory-robot PM pattern. Two Wayve records come from one employer, and the roles permit work in other declared countries; each requisition appears only once in the unique study inventory.

Germany. The three principal roles are from Hako, NEURA Robotics and Würth, covering autonomous cleaning, a robot platform and end-of-arm solutions. The limited sample shows plausible market, requirements, partnership and product-line work across these settings. It does not measure Germany-wide demand or establish a national skill rate. Three separate defense-context roles discovered in Germany are comparison only; their military-specific capabilities and approvals are not general robotics PM requirements.

Canada. The three principal requisitions are all from Montréal-based Vention, across hardware/robotics, MachineLogic and applications. They show one employer's distribution of product-line, software and use-case work. Counting three jobs does not create three independent company observations or support a claim about Canadian employers as a whole. Canadian supplier Robotiq's separate 2026 ROS 2 release offers technology context, not a fourth vacancy or a national adoption measure.

Evidence limits and source inventory

All roles were checked as point-in-time public employer pages on 12 October 2026. A live application control supports that date's status, not how long the job was open or whether it will remain available. The study intentionally favors readable employer sources. Some Workday and other dynamic pages, stale search-index entries and closed ATS paths could not enter the principal denominator. That access pattern and the small purposive sample mean there is no safe national or worldwide prevalence claim. The UK and Canada strata are especially narrow; sector and employer concentration limit transfer even within countries. The 33-role count is a study inventory, not a labour-market estimate.

Coding records only what each page states. Short source excerpts make individual examples traceable, but an excerpt missing a word is not proof that the full page lacks the concept. Software and hardware roles differ in depth; no one posting is a universal job description. The one-per-employer and vehicle-excluded views are sensitivity tests for concentration and sector choice, not alternative probability samples. Current product releases, industry figures and market-access changes are examined in a separate non-vacancy article with their own source and geography limits.

The public source index below lists the 33 retained principal requisitions once each, with employer names, role titles and direct evidence links.

Source index

United States

United Kingdom

Germany

Canada

Continue learning

Apply the evidence from this report through MTF Institute's Professional Certificate in Robotics Product Management. The programme turns the identified capabilities into structured theory, guided AI practice and reusable workplace artifacts.