Autonomy is not one market
Ground vehicles, aerial platforms, maritime systems, industrial robots, and surgical systems all get called autonomy. The underlying physics, constraints, regulatory environments, and talent requirements are different enough that treating them as one category makes the landscape harder to read, not easier.
Autonomy is a useful category for venture capital. It is a less useful category for understanding where specific technical work is happening and what it actually demands.
The deployment environment shapes everything
A system operating in a structured warehouse has different sensing requirements, update cycles, failure modes, and certification paths than one operating in a contested outdoor environment. Both might be called autonomous. They are not the same engineering problem.
The useful question is not whether a company does autonomy. It is what environment the system has to operate in, and what that implies for every layer of the stack.
Talent requirements follow domain constraints
A team building maritime autonomy needs people who understand sensor fusion in salt-water environments, RF behavior at sea, and the regulatory landscape for unmanned surface vessels. That is a different profile than a team building warehouse robotics or airborne platforms.
Treating autonomy as one recruiting market is how companies end up with the wrong people for the actual problem.