2

Remote Master Software Engineer Jobs in Missouri

Join a fully remote, international engineering environment where innovation, ownership, and AI-driven development are at the heart of building impactful software solutions. In this role, you will ...

$112K - $148K/yr

Role Specific Information About the Role As Senior Software Engineer, you will collaborate closely with design, product and engineering experts to tackle real-world challenges and deliver innovative ...

VP, Software Engineering

Hazelwood, MO · On-site +1

$250K - $335K/yr

This role is based in St Louis, MO and is not able to be fully remote. Candidates not based in the ... The Vice President, Software Engineering provides strategic leadership for the organization ...

VP, Software Engineering

Hazelwood, MO · On-site +1

$250K - $335K/yr

This role is based in St Louis, MO and is not able to be fully remote. Candidates not based in the ... The Vice President, Software Engineering provides strategic leadership for the organization ...

... software engineering standards. * Excellent technical leadership, communication, problem-solving, and mentoring skills. Benefits * Fully remote work opportunity. * Opportunity to shape the ...

New

Location - Remote (Europe) How You'll Make an Impact: As a Staff Machine Learning Engineer , you ... Software Engineering Rigor: Strong background in Python, distributed systems, and backend ...

This is a remote position, which requires regular travel to client sites Monday - Friday. We ... Ability to undertake software/firmware reverse engineering is a plus. * Capability to understand ...

Showing results 41-60

Remote Master Software Engineer information

Can remote master software engineers work fully remote?

Remote master software engineers can often work fully remote, depending on the company's policies and the nature of the projects. Many organizations allow fully remote work for senior engineering roles, especially when the job involves collaboration through online tools and requires advanced technical skills. However, some companies may require occasional on-site presence or have specific location restrictions.

What is the difference between Remote Master Software Engineer vs Remote Software Architect?

CriteriaRemote Master Software EngineerRemote Software Architect
Required CredentialsBachelor's or Master's in CS, relevant certificationsBachelor's or Master's in CS, certifications like TOGAF or cloud certifications
Work EnvironmentHands-on coding, development teams, project implementationDesigning system architecture, high-level planning, collaboration with stakeholders
Employer & Industry UsageTech companies, startups, software development firmsLarge enterprises, consulting firms, tech companies
Common Search & Comparison IntentYesYes

The Remote Master Software Engineer focuses on coding, development, and implementing software solutions, while the Remote Software Architect specializes in designing system structures and high-level planning. Both roles require technical expertise and often collaborate, but their core responsibilities differ significantly.

What are the most commonly searched types of Master Software Engineer jobs in Missouri? The most popular types of Master Software Engineer jobs in Missouri are:

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Jefferson City, MO • Remote

$116K - $153K/yr

Full-time

Posted 25 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.