1

Robotics Perception Engineer Jobs in Wisconsin (NOW HIRING)

Senior Robotics Software Engineer

Suamico, WI · On-site

$119.70K - $157.80K/yr

RC Mowers I We're Hiring Senior Robotics Software Engineer Full-Time | In-Person | Suamico, WI We ... The perception problem. LiDAR is great until it isn't. It can't tell you a dark patch is standing ...

Senior Robotics Software Engineer

Suamico, WI · On-site

$119.70K - $157.80K/yr

RC Mowers I Were Hiring Senior Robotics Software Engineer Full-Time | In-Person | Suamico, WI We ... Work on perception, sensor fusion, and decision-making in unstructured outdoor environments

Senior Robotics Software Engineer

Suamico, WI

$119.70K - $157.80K/yr

RC Mowers I We're Hiring Senior Robotics Software Engineer Full-Time | In-Person | Suamico, WI We ... Work on perception, sensor fusion, and decision-making in unstructured outdoor environments

Robot Welder II

Kenosha, WI · On-site

$17.50 - $24.25/hr

Maintain Touch-Sence Programming. * Unload finished parts. * Perform manual Finish Welding ... Close, distance, and peripheral vision; depth perception. Work Environment: * Work location:

Robotic Operator - SPS System supports overall operations and basic maintenance for robotics used ... Work closely with engineers, fabricators, and other team members to ensure seamless production ...

Physical AI Senior Manager

Milwaukee, WI · On-site

$124.60K - $164.50K/yr

Can translate between controls engineers, data scientists, and frontline operations * Carry a ... Robotics and autonomy (e.g., industrial robotics, mobile robotics and AMRs, perception-to-action ...

Production Lead

New Berlin, WI · On-site

$18.25 - $25.25/hr

The production lead position manages the build of custom mechanical systems for industrial robotic ... engineering projects and stakeholders in accordance with VMRA and applicable governing standards.

next page

Showing results 1-20

Robotics Perception Engineer information

What are the key skills and qualifications needed to thrive as a Robotics Perception Engineer, and why are they important?

To thrive as a Robotics Perception Engineer, you need strong expertise in computer vision, sensor fusion, machine learning, and proficiency in programming languages like C++ and Python, often supported by a degree in robotics, computer science, or a related field. Familiarity with tools and frameworks such as ROS (Robot Operating System), OpenCV, and deep learning libraries, as well as experience with sensors like LiDAR and cameras, is typically required. Excellent problem-solving abilities, teamwork, and adaptability help set standout professionals apart in this role. These competencies are crucial for enabling robots to accurately interpret and interact with their environment, leading to robust and reliable autonomous systems.

What are some common challenges faced by Robotics Perception Engineers when integrating new sensors into autonomous systems?

Robotics Perception Engineers often encounter challenges such as sensor calibration, data synchronization, and managing varying data quality when integrating new sensors. Ensuring that sensor data is accurately aligned in time and space is crucial for reliable perception in autonomous systems. Additionally, engineers must address the complexities of fusing data from multiple modalities (like cameras, LiDAR, or radar) while optimizing processing efficiency. Close collaboration with hardware and software teams is essential to troubleshoot integration issues and achieve robust, real-time perception.

What are Robotics Perception Engineers?

Robotics Perception Engineers are professionals who specialize in enabling robots to interpret and understand their environment using sensors and data processing algorithms. They work on developing and implementing computer vision, sensor fusion, and machine learning techniques so that robots can perceive objects, people, and surroundings. Their work is crucial for applications such as autonomous vehicles, drones, industrial automation, and service robots. By improving a robot's ability to 'see' and make sense of the world, they help create safer and more effective robotic systems.

What is the difference between Robotics Perception Engineer vs Computer Vision Engineer?

AspectRobotics Perception EngineerComputer Vision Engineer
Required CredentialsBachelor's or Master's in Robotics, Computer Science, or Electrical Engineering; experience with perception algorithmsBachelor's or Master's in Computer Science, Electrical Engineering, or related fields; strong programming skills in vision processing
Work EnvironmentRobotics labs, autonomous vehicle companies, industrial automationSoftware companies, tech startups, research labs focusing on image and video analysis
Industry UsageAutonomous vehicles, robotics, manufacturingHealthcare, security, consumer electronics, automotive

Robotics Perception Engineers focus on developing perception systems specifically for robots, integrating sensors and perception algorithms for navigation and interaction. Computer Vision Engineers primarily develop algorithms for interpreting visual data across various applications. While both roles require strong programming and understanding of perception, Robotics Perception Engineers specialize in sensor fusion and real-time processing within robotic systems, whereas Computer Vision Engineers work more broadly on image analysis and recognition tasks.

What are popular job titles related to Robotics Perception Engineer jobs in Wisconsin? For Robotics Perception Engineer jobs in Wisconsin, the most frequently searched job titles are:
What cities in Wisconsin are hiring for Robotics Perception Engineer jobs? Cities in Wisconsin with the most Robotics Perception Engineer job openings:
Senior Robotics Software Engineer

Senior Robotics Software Engineer

RC Mowers

Suamico, WI • On-site

$119.70K - $157.80K/yr

Full-time

Medical, Dental, Vision, Life, Retirement, PTO

Posted 25 days ago


Job description

RC Mowers I We're Hiring
Senior Robotics Software Engineer
Full-Time | In-Person | Suamico, WI
We build full-size commercial autonomous robots that mow large properties without an operator in the seat. They run in real terrain - wet grass, dust, heat, GPS dropouts, unstructured environments - for municipalities, DOTs, and commercial contractors across North America.
Our machines ship today, and they work. What this category becomes over the next decade is still being written - we plan to write most of it.
We're hiring a senior ROS2 engineer to help us do it.
THE PROBLEM YOU'D OWN
The core of this job is developing in ROS2: building, extending, and shipping the software that makes our machines do what they do. New behaviors, new capabilities, better decisions in the field. That's the day-to-day.
Within that, two areas have outsized leverage on where the platform goes - and you'd help us decide where to push hardest:
The fleet problem. We're scaling toward thousands of units operating in the field. That means treating robots more like servers - telemetry, observability, OTA updates, fleet-wide health, remote diagnostics, mission orchestration, the whole stack that lets a small team operate a large fleet without things falling apart. If you've done backend or distributed systems work and want to bring that discipline to robotics, this is where it shows up.
The perception problem. LiDAR is great until it isn't. It can't tell you a dark patch is standing water, that a shirt on the ground is soft, or that the thing twenty feet ahead is a person, a deer, or a fence post - distinctions that matter when you're deciding whether to stop, slow, reroute, or proceed. Camera-based vision that complements LiDAR in unstructured outdoor environments is one of the highest-leverage problems we have. If computer vision is what gets you out of bed, there's a charter for you here.
We'd be thrilled to hire someone strong on one and curious about the other. We don't expect both at world-class depth - but we do expect deep ROS2 fluency. That's the constant.
WHAT YOU'D ACTUALLY DO
  • Develop and ship ROS2 features that enhance machine behavior and unlock new capabilities
  • Build out our fleet management layer - telemetry, OTA, remote ops, fleet-wide observability
  • Work on perception, sensor fusion, and decision-making in unstructured outdoor environments
  • Collaborate directly with mechanical, electrical, and controls engineers - and with the technicians who validate and field-test what you build
  • Make architectural calls that affect what the platform can do two and three years out
  • Help shape how we hire, review, and scale the software team as we grow

WHAT YOU BRING
  • Strong production ROS2 experience - not a class, not a side project; you've shipped and maintained ROS2 software that users depend on
  • Solid C++ and/or Python; comfort moving between them
  • Experience with at least one of: fleet management/distributed systems at scale, or computer vision and sensor fusion in real-world conditions
  • A sense of when to build, when to integrate, and when to throw something out
  • The judgment to operate as a senior IC: you scope your own work, push back when the spec is wrong, and ship without needing to be managed
  • Clear technical writing - design docs, postmortems, code review comments that move the team forward

BONUS POINTS
  • Outdoor or off-road robotics experience (agricultural, construction, defense, mining, AMR)
  • Production computer vision in unstructured environments
  • OTA update systems, fleet telemetry pipelines, remote operations tooling
  • Embedded Linux, real-time systems, or low-level controls experience
  • GPS-denied or GPS-degraded localization
  • Work that's been deployed at meaningful scale (hundreds-plus units)

ABOUT THE TEAM
The engineering team is ten people. No one is coasting.
We don't have process layers between you and the machine. Code review matters here. Design discussions are technical and direct. Decisions get made by the people closest to the work - and the company is led by an engineer who knows the difference between cheap and right. We make trade-offs deliberately, not by default.
You'll have unusual ownership for a company our size, and peers who'll push back hard when you're wrong.
We're based near Green Bay, Wisconsin. Cost of living is a fraction of what you'd pay in a coastal tech hub, the commute is ten minutes, and the work is on real robots in real terrain - not a campus parking lot.
WHAT THIS IS NOT
A research position. A role where you'll spend a year on a prototype that doesn't ship. A place where someone else writes the spec and you implement it. A team where senior means "has been here longest."
HOW TO STAND OUT
A resume helps, but tell us about something you've built or shipped. The harder, messier, and closer to production, the better.
We want to know:
  • What was the problem?
  • What did you build?
  • What broke, and how did you find it?
  • What would you do differently?
  • What did you learn that changed how you work?

Code, design docs, postmortems, talks, papers, demos - anything that shows how you think.
ABOUT RC MOWERS
We design and build autonomous and remote-operated mowing equipment for difficult environments - a growing, profitable company shipping to municipalities, DOTs, and commercial contractors across North America.
COMPENSATION & BENEFITS
Compensation commensurate with experience. Benefits include health, dental, and vision insurance, 401(k) with company match, paid vacation and sick leave, and disability, life, and accident insurance.
Hiring is subject to a pre-employment background check and drug screening. RC Mowers provides equal employment opportunities to all employees and applicants.