2

Remote Goldman Sachs Software Engineer Jobs in Michigan

Software Systems Engineer

Zeeland, MI · On-site +1

$159K - $188K/yr

This role is not eligible for remote work. WHAT YOU'LL DO * Consistently execute the processes for ... Engineering or a related field. * 5 years technical experience in systems or software development ...

Software Systems Engineer

Grand Rapids, MI · On-site +1

$166K - $196K/yr

This role is not eligible for remote work. WHAT YOU'LL DO * Consistently execute the processes for ... Engineering or a related field. * 5 years technical experience in systems or software development ...

This is a remote position. Responsibilities * Design, develop, test, and deploy full-stack features ... Post-secondary education in computer science, software engineering, or a related field, or ...

This is a remote position. Responsibilities * Design, develop, test, and deploy full-stack features ... Post-secondary education in computer science, software engineering, or a related field, or ...

This is a remote position. Responsibilities * Design, develop, test, and deploy full-stack features ... Post-secondary education in computer science, software engineering, or a related field, or ...

$111K - $146K/yr

Bachelor's degree in Computer Science, Software Engineering, Information Technology, Data Science ... A hybrid role based in Obispado, Monterrey, with most work expected to be remote and office ...

Senior Software Engineer, DevOps

Ann Arbor, MI · On-site +1

$160K - $190K/yr

We are seeking a Senior Software Engineer, DevOps to help design, build, and operate Utilidata ... remote work. Our Commitments: Utilidata values the diversity of our team. We provide equal ...

Showing results 21-40

Remote Goldman Sachs Software Engineer information

What does a remote Goldman Sachs software engineer do?

A Remote Goldman Sachs Software Engineer is responsible for designing, developing, and maintaining software applications that support the firm's financial services and operations. Working remotely, they collaborate with cross-functional teams to create scalable and reliable solutions, often using modern programming languages and technologies. Their work includes coding, testing, debugging, and deploying software, as well as participating in code reviews and staying updated with industry best practices. Remote engineers leverage digital collaboration tools to communicate effectively and ensure security standards are met while working outside the office.

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

To thrive as a Remote Goldman Sachs Software Engineer, you need strong programming skills (such as in Java, Python, or C++), computer science fundamentals, and typically a bachelor’s degree in a related field. Familiarity with financial systems, cloud platforms, version control tools like Git, and experience using CI/CD pipelines are commonly required, while certifications in cloud computing or cybersecurity can be advantageous. Excellent problem-solving abilities, self-motivation, and strong communication skills help you collaborate effectively across remote teams and adapt to dynamic project needs. These combined skills are crucial for delivering secure, scalable solutions in a highly regulated, fast-paced financial technology environment.

What is the difference between Remote Goldman Sachs Software Engineer vs Remote JPMorgan Chase Software Engineer?

AspectRemote Goldman Sachs Software EngineerRemote JPMorgan Chase Software Engineer
Required CredentialsBachelor's in CS or related field; coding skills; financial industry knowledgeBachelor's in CS or related field; coding skills; financial industry knowledge
Work EnvironmentRemote, collaborative teams within financial servicesRemote, collaborative teams within banking and financial services
Employer & Industry UsageGoldman Sachs, investment banking, asset managementJPMorgan Chase, banking, investment, and financial services

The Remote Goldman Sachs Software Engineer and Remote JPMorgan Chase Software Engineer roles share similar credentials, work environments, and industry usage. Both positions involve remote work within major financial institutions, requiring comparable skills and educational backgrounds. The main difference lies in the specific company and its unique projects or focus areas within the financial sector.

How does a remote Goldman Sachs software engineer typically collaborate with team members across different time zones?

As a remote Software Engineer at Goldman Sachs, you'll often work with colleagues located around the globe. Collaboration is facilitated through regular video meetings, agile ceremonies, and communication platforms like Slack and Jira. Flexibility in scheduling and clear documentation are essential to ensure smooth handoffs and project continuity. You'll also participate in code reviews and pair programming sessions virtually to maintain high-quality standards and foster team cohesion.
What are the most commonly searched types of Goldman Sachs Software Engineer jobs in Michigan? The most popular types of Goldman Sachs Software Engineer jobs in Michigan are:
What job categories do people searching Remote Goldman Sachs Software Engineer jobs in Michigan look for? The top searched job categories for Remote Goldman Sachs Software Engineer jobs in Michigan are:
What cities in Michigan are hiring for Remote Goldman Sachs Software Engineer jobs? Cities in Michigan with the most Remote Goldman Sachs Software Engineer job openings:

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Lansing, MI • Remote

$124K - $163K/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.