2

Remote Embedded Software Jobs in Springfield, IL

Through modern vertical software, embedded payments (Xplor Pay), and AI-powered capabilities, we ... You can work fully remote in this position, provided you have eligible working rights, and are able ...

Account Executive

Springfield, IL · On-site +1

$100K/yr

Through modern vertical software, embedded payments (Xplor Pay), and AI-powered capabilities, we ... You can work fully remote in this position, provided you have eligible working rights, and are able ...

Remote Embedded Software information

See Springfield, IL salary details

$69.4K

$152K

$172.5K

How much do remote embedded software jobs pay per year?

As of Jul 29, 2026, the average yearly pay for remote embedded software in Springfield, IL is $152,019.00, according to ZipRecruiter salary data. Most workers in this role earn between $130,300.00 and $171,500.00 per year, depending on experience, location, and employer.

What is a remote embedded software engineer?

A remote embedded software engineer is a professional who designs, develops, tests, and maintains software that runs on embedded systems, such as microcontrollers or specialized hardware, while working from a location outside the traditional office environment. These engineers typically collaborate with hardware teams, write code for real-time or resource-constrained systems, and use remote tools to debug and deploy software. They may work in industries like automotive, medical devices, consumer electronics, or industrial automation. Remote embedded software engineers rely on communication and project management tools to coordinate with their teams and ensure product quality.

What are some common challenges faced by remote embedded software engineers, and how can they be addressed?

Remote embedded software engineers often face challenges such as limited access to physical hardware for testing, coordinating with hardware teams across locations, and ensuring clear communication about design specifications. To overcome these, teams typically use simulation tools, remote access labs, and detailed documentation. Regular virtual meetings and collaborative platforms also help maintain alignment and facilitate troubleshooting in distributed environments.

What are the key skills and qualifications needed to thrive as a Remote Embedded Software Engineer, and why are they important?

To thrive as a Remote Embedded Software Engineer, you need expertise in embedded systems programming (typically in C/C++), hardware interfacing, and a relevant degree in computer engineering or electrical engineering. Familiarity with development tools such as debuggers, version control systems (e.g., Git), and real-time operating systems (RTOS) is commonly required. Strong problem-solving abilities, self-motivation, and effective remote communication skills help you excel in a distributed team environment. These skills ensure reliable software integration with hardware, efficient collaboration, and successful delivery of complex embedded solutions.

What is the difference between Remote Embedded Software vs Remote Firmware Engineer?

AspectRemote Embedded SoftwareRemote Firmware Engineer
Required CredentialsBachelor's in Computer Engineering, Electrical Engineering, or related; experience with embedded systemsBachelor's in Electrical Engineering, Computer Engineering, or related; experience with firmware development
Work EnvironmentDevelops software for embedded devices, often in hardware labs or remote setupsCreates low-level firmware for hardware components, typically in hardware labs or remote
Industry UsageAutomotive, IoT, consumer electronics, industrial systemsConsumer electronics, IoT, aerospace, automotive
Common Search/ComparisonYesYes

Remote Embedded Software and Remote Firmware Engineer roles both involve working on embedded systems, but Embedded Software focuses on higher-level software development, while Firmware Engineers work on low-level hardware control code. Both require similar credentials and are used across industries like automotive and IoT, often in remote or hybrid environments.

What Are Remote Embedded Software Jobs?

Remote embedded software jobs include embedded software engineer positions. As a work from home embedded software engineer, you develop embedded software systems for a variety of computerized devices. Your responsibilities start with assessing your client’s needs. You then design and code the embedded software, troubleshoot your software systems, perform research and test actions on the software, and implement software updates whenever necessary. Other duties include maintaining the software programs, documenting solutions to issues, providing the necessary post-production support, and reviewing the implemented system to debug the embedded environment and interpret error reports.

What are popular job titles related to Remote Embedded Software jobs in Springfield, IL? For Remote Embedded Software jobs in Springfield, IL, the most frequently searched job titles are:
What cities near Springfield, IL are hiring for Remote Embedded Software jobs? Cities near Springfield, IL with the most Remote Embedded Software job openings:
Infographic showing various Remote Embedded Software job openings in Springfield, IL as of July 2026, with employment types broken down into 93% Full Time, and 7% Contract. Highlights an 26% In-person, and 74% Remote job distribution, with an average salary of $152,019 per year, or $73.1 per hour.

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Springfield, IL • Remote

$121K - $160K/yr

Full-time

Posted 14 days ago


Job description

Senior Software Engineer: Applied AI (Voice Agents & ML Systems)

AMC Health · Remote (US) · Full-time

The pitch

We build and operate production AI voice agents that hold real phone conversations in a regulated healthcare setting, plus the machine learning and LLM pipelines around them. This is one seat that spans four disciplines that rarely come together: real-time systems, LLM engineering, traditional machine learning, and serious cloud infrastructure, all in production, all with real consequences. If you are the kind of engineer who gets restless doing one thing, this role is the opposite problem.

What you'll work across

Real-time voice AI

  • Streaming, low-latency speech-to-speech systems built on modern LLMs
  • Telephony and real-time media (call control, live audio streaming)
  • Audio handling and the quirks of real human conversation (interruptions, timing, noise)
  • Concurrency on a latency-sensitive path, where p99 matters and a stall is something a caller hears

LLM engineering

  • Wrapping nondeterministic models in deterministic control so they behave reliably in production
  • Multi-model pipelines, prompt design, and cost/latency budgeting
  • Evaluation harnesses, including LLM-as-judge and automated agent-tests-agent approaches
  • Agentic tooling that gives AI systems safe, structured access to infrastructure

Traditional (non-LLM) machine learning

  • End-to-end ML pipelines: feature engineering, model training, and scheduled inference
  • Imbalanced, messy real-world data; calibration and explainability for non-technical consumers
  • Turning research notebooks into reproducible, auditable production pipelines

Cloud and infrastructure

  • Infrastructure as code across multiple environments (we run on AWS)
  • Managed compute, data, streaming, and orchestration services
  • Security engineering in a regulated setting: encryption, least-privilege access, strict data-handling discipline
  • Observability and telemetry-driven debugging, tracing a production issue from a metric anomaly to root cause

Plus occasional full-stack work on internal tools, and an engineering workflow that leans heavily on AI coding assistants, with human accountability for every change.

What you'll actually do

  • Ship and debug code on a live, real-time voice pipeline where latency and correctness are user-facing
  • Design control systems around LLMs: guardrails, budgets, watchdogs, safe fallbacks
  • Build and operate LLM evaluation and batch-analysis pipelines
  • Own traditional ML workflows from data to scheduled production inference
  • Trace production issues from a metric anomaly to root cause, including building the evidence when the cause is a vendor

Must-haves

  • 7+ years building and operating production backend systems, with strong general-purpose programming skills (we work primarily in Python)
  • Experience running distributed systems in the cloud; comfortable debugging from telemetry to root cause
  • Hands-on production experience with LLMs or generative AI (any provider or framework), plus the judgment to know when not to use a model
  • Working fluency across the traditional machine learning lifecycle (you productionize; you do not need to publish)
  • Disciplined in a regulated environment: small, reviewable changes and careful handling of sensitive data

Nice-to-haves

  • Real-time media or telephony experience
  • Front-end / full-stack ability
  • ML pipeline experience, vector search, or embeddings
  • Fluency with AI coding assistants (our workflows assume them, with human accountability for every change)

How we work

Smallest correct change wins. Every behavior change is validated against the live system. Evidence over opinion in debugging. Code review is rigorous. Safety and privacy gate everything.

Work authorization (no exceptions)

This role is open only to US citizens and lawful permanent residents (Green Card holders). We cannot consider candidates who require visa sponsorship now or in the future, and we are unable to make exceptions of any kind.

How to apply

Please submit both of the following:

  • Your LinkedIn profile URL
  • A phone number where we can reach you

A resume is welcome but optional; the two items above are required.