2

Remote Software Engineer Spotify Jobs in Wisconsin

Software Engineering Manager

Kohler, WI · On-site +1

$129K - $165K/yr

This role is fully remote. Specific Responsibilities: * Lead, mentor and manage a team of up to 8 software engineers. * Manage the development of mobile and web front-end solutions - define ...

... Software Developers, IT, Project Management Professionals, and more. At NV5 Geospatial, we are a collaboration of intelligent, innovative thinkers who care for each other, our communities, and the ...

... Software Developers, IT, Project Management Professionals, and more. At NV5 Geospatial, we are a collaboration of intelligent, innovative thinkers who care for each other, our communities, and the ...

This role is open to remote What you will be doing * Conduct code-level software analyses to ... Knowledge of programming languages. (COBOL/JCL) * Knowledge of primary database engines. (VSAM/CICS)

This role is open to remote What you will be doing * Conduct code-level software analyses to ... Knowledge of programming languages. (COBOL/JCL) * Knowledge of primary database engines. (VSAM/CICS)

$90K - $100K/yr

Technical/software development experience. * Experience in software development; experience (C# ... REMOTE Basic Requirements Required Skills: * High School diploma, Bachelor's degree in Engineering ...

Security Engineer (AppSec)

Milwaukee, WI · On-site +1

$57.75 - $77.25/hr

As a Security Engineer (Software Focus) at SysLogic , you will be responsible for identifying and ... As needed provide training on secured development principals in both remote and in person settings.

next page

Showing results 1-20

Remote Software Engineer Spotify information

How does a remote software engineer at Spotify typically collaborate with distributed teams?

As a remote software engineer at Spotify, you will regularly collaborate with team members across different time zones using tools like Slack, Zoom, and collaborative coding platforms such as GitHub. Agile ceremonies, such as daily standups, sprint planning, and code reviews, are conducted virtually to maintain alignment. Clear communication and proactive documentation are vital, and you'll often pair program or participate in asynchronous discussions to resolve issues and share ideas. Spotify emphasizes a strong team culture, so virtual social events and regular check-ins are common to foster connection and support.

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

To excel as a Remote Software Engineer at Spotify, you need strong programming skills (commonly in languages like Java, Python, or JavaScript), experience with scalable system design, and a relevant degree or equivalent experience. Familiarity with cloud platforms (such as AWS or Google Cloud), CI/CD tools, and version control systems like Git is typically required. Outstanding communication, self-motivation, and collaboration skills are essential for thriving in a remote, cross-functional team environment. These abilities ensure you can build reliable, innovative software solutions while effectively contributing to Spotify’s distributed global teams.

What does a Remote Software Engineer at Spotify do?

A Remote Software Engineer at Spotify is responsible for designing, building, and maintaining software applications and systems that support Spotify's music streaming platform. They collaborate with cross-functional teams to develop new features, improve performance, and ensure a seamless user experience for millions of listeners. Working remotely, they leverage modern programming languages, tools, and agile methodologies, while staying connected with their team through digital communication channels. The role requires strong technical skills, effective communication, and the ability to work independently from any location.

What is the difference between Remote Software Engineer Spotify vs Remote Data Engineer Spotify?

AspectRemote Software Engineer SpotifyRemote Data Engineer Spotify
Required CredentialsBachelor's in CS or related field, programming skillsBachelor's in CS, Data Science, or related field, strong SQL and Python skills
Work EnvironmentCollaborates with software development teams, Agile environmentWorks with data pipelines, analytics teams, cloud platforms
Employer & Industry UsageCommonly employed in tech companies, including SpotifyUsed in data-driven roles within similar tech companies
Search & Comparison IntentFocuses on software development tasks at SpotifyFocuses on data infrastructure and analytics at Spotify

While both roles require technical skills and are employed within Spotify, a Remote Software Engineer primarily develops applications and features, whereas a Remote Data Engineer focuses on building data pipelines and managing data infrastructure. The choice depends on whether you prefer software development or data management within Spotify's environment.

What are the most commonly searched types of Software Engineer Spotify jobs in Wisconsin? The most popular types of Software Engineer Spotify jobs in Wisconsin are:
What job categories do people searching Remote Software Engineer Spotify jobs in Wisconsin look for? The top searched job categories for Remote Software Engineer Spotify jobs in Wisconsin are:
What cities in Wisconsin are hiring for Remote Software Engineer Spotify jobs? Cities in Wisconsin with the most Remote Software Engineer Spotify job openings:

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Madison, WI • Remote

$123K - $162K/yr

Full-time

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