ZipRecruiter

Log In

2

Remote Integration Software Engineer Jobs in Green Bay, WI

RC Mowers

Senior Robotics Software Engineer

Green Bay, WI · Remote

$100K - $140K/yr

Build out our fleet management layer -- telemetry, OTA, remote ops, fleet-wide observability * Work ... A sense of when to build, when to integrate, and when to throw something out * The judgment to ...

1 point system

Senior OTM Developer

Green Bay, WI · Remote

Job Title Senior OTM Developer Location Remote Description : OTM (Oracle Transportation Management ... Suite for managing integration flows * This Senior OTM Consultant/Developer will implement ...

Amteck, LLC

BIM Technician - Electrical

Appleton, WI · On-site +1

This position is eligible to be fully remote or for work out of our Lexington, KY HQ or our ... BIM software * Model Coordination:Integrating design information from various disciplines ...

next page

Showing results 1-20

All JobsIntegration Software Engineer JobsRemote Integration Software Engineer JobsRemote Integration Software Engineer Jobs in Green Bay, WI

Remote Integration Software Engineer information

See Green Bay, WI salary details

$43.3K

$120.9K

$168.8K

How much do remote integration software engineer jobs pay per year?

As of Jul 28, 2026, the average yearly pay for remote integration software engineer in Green Bay, WI is $120,877.00, according to ZipRecruiter salary data. Most workers in this role earn between $101,200.00 and $136,200.00 per year, depending on experience, location, and employer.

What is the difference between Remote Integration Software Engineer vs Remote API Developer?

AspectRemote Integration Software EngineerRemote API Developer
Required CredentialsBachelor's in CS or related field, experience with integration toolsBachelor's in CS or related field, experience with API design
Work EnvironmentCollaborates with cross-functional teams, remote or hybridWorks on API development, testing, and documentation remotely
Industry UsageUsed in software, SaaS, and enterprise integration projectsCommon in web services, SaaS, and mobile app development
Search & Comparison IntentOften compared for integration roles involving systems and data flowCompared for API-specific development and design roles

The Remote Integration Software Engineer and Remote API Developer roles share similar credentials and work environments but focus on different aspects of software development. The Integration Engineer emphasizes connecting various systems, while the API Developer specializes in designing and building APIs. Both roles are vital in modern software ecosystems and often overlap in skills and industry usage.

What are popular job titles related to Remote Integration Software Engineer jobs in Green Bay, WI? For Remote Integration Software Engineer jobs in Green Bay, WI, the most frequently searched job titles are:
What job categories do people searching Remote Integration Software Engineer jobs in Green Bay, WI look for? The top searched job categories for Remote Integration Software Engineer jobs in Green Bay, WI are:
What cities near Green Bay, WI are hiring for Remote Integration Software Engineer jobs? Cities near Green Bay, WI with the most Remote Integration Software Engineer job openings:
Remote Integration Software Engineer jobs near you
Infographic showing various Remote Integration Software Engineer job openings in Green Bay, WI as of July 2026, with employment types broken down into 91% Full Time, 6% Part Time, 1% Temporary, and 2% Contract. Highlights an 86% Physical, 5% Hybrid, and 9% Remote job distribution, with an average salary of $120,877 per year, or $58.1 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?