2

Remote Engineering Jobs in Lansing, MI (NOW HIRING)

Epic Denials Management Operator

Lansing, MI · Remote

$18.25 - $24.25/hr

Position Summary Join Deloitte's AI & Engineering practice to support hospital denials management ... This is a primarily remote role supporting enterprise Epic support, with minimal travel and ...

... REMOTE but candidate must reside in Michigan to be considered. You should minimally meet the knowledge, skills, and abilities listed below. * Bachelor's degree in Civil Engineering and minimum of ...

Engineers create products utilizing state-of-the-art technologies. They ensure successful releases ... Ability to work remote with a stable internet connection on an as needed basis. * Occasional ...

Engineers create products utilizing state-of-the-art technologies. They ensure successful releases ... remote with a stable internet connection on an as needed basis. • Occasional lifting and/or ...

The Litigation Project Manager position is fully remote and open to our offices in Michigan ... iscovery Engineers. * Draft and maintain documentation related to workflows, issues, and ...

Showing results 41-60

Remote Engineering information

See Lansing, MI salary details

$33K

$63.9K

$96.9K

How much do remote engineering jobs pay per year?

As of Aug 11, 2026, the average yearly pay for remote engineering in Lansing, MI is $63,876.00, according to ZipRecruiter salary data. Most workers in this role earn between $47,700.00 and $73,000.00 per year, depending on experience, location, and employer.

What are the key skills and qualifications needed to thrive as a remote engineer?

To thrive as a Remote Engineer, you need strong technical expertise in your engineering discipline, a relevant degree, and experience with distributed systems or remote collaboration. Familiarity with tools such as Git, cloud platforms (e.g., AWS, Azure), and team communication software like Slack or Zoom is typically required. Excellent self-motivation, time management, and clear written communication distinguish top performers in remote settings. These skills and qualities are crucial for delivering high-quality engineering solutions and maintaining productivity while collaborating with geographically dispersed teams.

What is remote engineering?

Remote engineering refers to engineering work that is performed outside of a traditional office or job site, typically from home or another remote location. Remote engineers use digital tools and communication platforms to collaborate with teams, design systems, write code, or manage projects from anywhere in the world. This work arrangement allows for greater flexibility and can help companies access a wider pool of talent. However, it also requires strong communication skills and self-discipline to maintain productivity and teamwork.

How do remote engineering teams typically coordinate and communicate to ensure project success?

Remote engineering teams commonly use a combination of collaboration tools like Slack, Jira, and GitHub to stay connected and manage projects efficiently. Regular virtual stand-ups, sprint planning meetings, and code reviews help maintain alignment and transparency among team members. Clear documentation and proactive communication are essential to overcome time zone differences and prevent misunderstandings. Most teams also establish shared coding standards and utilize version control to streamline contributions from multiple engineers working remotely.

What is the difference between Remote Engineering vs Remote Software Developer?

AspectRemote EngineeringRemote Software Developer
Required CredentialsBachelor's in Engineering, relevant certificationsBachelor's in Computer Science or related field, coding certifications
Work EnvironmentDesign, testing, and overseeing engineering projects remotelyWriting, testing, and deploying software remotely
Employer & Industry UsageEngineering firms, manufacturing, infrastructureTech companies, startups, software firms
Search & Comparison IntentUnderstanding engineering roles vs software roles remotely

Remote Engineering involves designing and managing engineering projects remotely, often requiring technical certifications and a background in engineering disciplines. Remote Software Developers focus on coding and software deployment from a remote location, typically with programming certifications. While both roles can be performed remotely, Remote Engineering emphasizes project oversight and technical engineering tasks, whereas Remote Software Development centers on software creation and maintenance.

What are the most commonly searched types of Engineering jobs in Lansing, MI? The most popular types of Engineering jobs in Lansing, MI are:
What are popular job titles related to Remote Engineering jobs in Lansing, MI? For Remote Engineering jobs in Lansing, MI, the most frequently searched job titles are:
What job categories do people searching Remote Engineering jobs in Lansing, MI look for? The top searched job categories for Remote Engineering jobs in Lansing, MI are:
What cities near Lansing, MI are hiring for Remote Engineering jobs? Cities near Lansing, MI with the most Remote Engineering job openings:
Infographic showing various Remote Engineering job openings in Lansing, MI as of August 2026, with employment types broken down into 88% Full Time, 6% Part Time, 5% Contract, and 1% Nights. Highlights an 88% Physical, 4% Hybrid, and 8% Remote job distribution, with an average salary of $63,876 per year, or $30.7 per hour.

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Lansing, MI • Remote

$124K - $163K/yr

Full-time

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