2

Remote Controls Engineer Jobs in Green Bay, WI (NOW HIRING)

Build out our fleet management layer -- telemetry, OTA, remote ops, fleet-wide observability * Work ... Collaborate directly with mechanical, electrical, and controls engineers -- and with the ...

Cares about leading the way in construction, engineering, manufacturing and renewable energy. Cares ... REMOTE How Does FTI Give YOU the Chance to Thrive? If you're energized by new challenges, FTI ...

Engineering Buyer

Green Bay, WI · Remote

$70K - $80K/yr

This is a full-time, exempt position with flexibility for onsite in De Pere, WI, hybrid, or remote ... Demonstrated experience with procurement practices, supplier management, and documentation controls ...

Engineering Buyer

Green Bay, WI · On-site +1

$70K - $80K/yr

This is a full-time, exempt position with flexibility for onsite in De Pere, WI, hybrid, or remote ... Demonstrated experience with procurement practices, supplier management, and documentation controls ...

Engineering Buyer

Green Bay, WI · On-site +1

$70K - $80K/yr

This is a full-time, exempt position with flexibility for onsite in De Pere, WI, hybrid, or remote ... Demonstrated experience with procurement practices, supplier management, and documentation controls ...

Project Director

Green Bay, WI · Remote

$155K - $200K/yr

... or working fully remote within the United States . This role leads complex, multi discipline ... and project engineers, and support strong overall team performance * Oversee project controls ...

Project Director

Green Bay, WI · On-site +1

$155K - $200K/yr

... or working fully remote within the United States . This role leads complex, multi discipline ... and project engineers, and support strong overall team performance * Oversee project controls ...

... engineering, and finance-to strengthen our global supply chain and mitigate compliance risks ... Please note that a fully remote option is not available. Relocation assistance is also provided.

Remote Controls Engineer information

See Green Bay, WI salary details

$53.5K

$93.9K

$127.4K

How much do remote controls engineer jobs pay per year?

As of Jul 28, 2026, the average yearly pay for remote controls engineer in Green Bay, WI is $93,933.00, according to ZipRecruiter salary data. Most workers in this role earn between $81,200.00 and $105,000.00 per year, depending on experience, location, and employer.

How can I make $100,000 a year working from home?

Remote Controls Engineers can reach a $100,000 annual salary by gaining specialized skills in embedded systems, automation, and programming languages like C or Python, along with relevant certifications. Building experience through complex projects, working for high-paying companies, or consulting can also increase earning potential while working remotely.

What engineer makes $500,000 a year?

Remote Controls Engineers typically do not earn $500,000 annually; such high salaries are more common in executive or specialized roles within engineering fields. Senior engineers with extensive experience, advanced skills, or leadership positions in high-demand industries may reach high six-figure incomes, but $500,000 is rare for this role alone.

What engineers make $200,000 a year?

Senior controls engineers, including remote controls engineers, with extensive experience, specialized skills in automation and embedded systems, and often advanced certifications can earn $200,000 or more annually. High salaries are typically associated with industries like aerospace, defense, or large-scale manufacturing, especially for those in leadership or highly technical roles.

What is a Remote Controls Engineer job?

A Remote Controls Engineer designs, develops, and maintains automated control systems that can be managed remotely. They work with hardware and software to ensure seamless communication between control systems and remote operators. Their role often involves programming PLCs, optimizing communication protocols, and troubleshooting system issues. Industries such as manufacturing, robotics, and energy commonly employ Remote Controls Engineers to enhance efficiency and safety in operations.

Can Controls Engineers work remotely?

Controls Engineers can often work remotely, especially in roles focused on design, programming, and system analysis that rely on computer-based tools. However, some tasks requiring on-site installation, maintenance, or troubleshooting may necessitate physical presence. The feasibility of remote work depends on the employer, project requirements, and the engineer's skills with remote collaboration tools.

What are the key skills and qualifications needed to thrive in the Remote Controls Engineer position, and why are they important?

To thrive as a Remote Controls Engineer, you need a strong background in electrical or mechanical engineering, control systems design, and programming, often supported by a relevant engineering degree. Familiarity with industry-standard PLCs, SCADA systems, HMI software, and certifications such as Professional Engineer (PE) or relevant manufacturer certifications are highly valuable. Strong analytical thinking, problem-solving abilities, and effective communication skills are essential for collaborating across multidisciplinary teams. These skills and qualifications are critical for designing reliable control solutions, troubleshooting issues, and ensuring project success in dynamic, technology-driven environments.

What types of projects and teams does a Remote Controls Engineer typically work with?

Remote Controls Engineers often work on projects related to the automation and remote operation of equipment in industries such as manufacturing, energy, utilities, and transportation. You’ll typically collaborate with electrical engineers, software developers, project managers, and field technicians to design, implement, and optimize control systems. Projects may involve integrating new automation solutions, upgrading legacy equipment, or troubleshooting system issues. This role often allows you to see projects through from initial design and specification all the way to commissioning and support, offering excellent opportunities for technical growth and cross-functional teamwork.

What are the most commonly searched types of Controls Engineer jobs in Green Bay, WI? The most popular types of Controls Engineer jobs in Green Bay, WI are:
What are popular job titles related to Remote Controls Engineer jobs in Green Bay, WI? For Remote Controls Engineer jobs in Green Bay, WI, the most frequently searched job titles are:
What cities near Green Bay, WI are hiring for Remote Controls Engineer jobs? Cities near Green Bay, WI with the most Remote Controls Engineer job openings:
Infographic showing various Remote Controls Engineer job openings in Green Bay, WI as of July 2026, with employment types broken down into 83% Full Time, and 17% Contract. Highlights an 100% Remote job distribution, with an average salary of $93,933 per year, or $45.2 per hour.
Senior Robotics Software Engineer

Senior Robotics Software Engineer

RC Mowers

Green Bay, WI • Remote

$100K - $140K/yr

Full-time

This job post has expired today. Applications are no longer accepted.


Job description

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.

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

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.

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...
  • The perception problem...

Pay Range: $100,000 - $140,000/yr

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.

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?