2

Remote Ngo Software Engineer Jobs in Wisconsin (NOW HIRING)

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

New

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

New

AI Innovation Engineer

Madison, WI · On-site +1

$90K - $135K/yr

Software Eng/Developer III Job Summary: The Division of Information Technology (DoIT) is an ... Remote work requires an approved flexible work arrangement (FWA), which is reviewed and approved ...

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

next page

Showing results 1-20

Remote Ngo Software Engineer information

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

To thrive as a Remote NGO Software Engineer, you need strong programming skills, experience with software development lifecycles, and a relevant degree in computer science or a related field. Familiarity with collaboration tools like Git, project management systems such as Jira, and cloud platforms is commonly required, along with knowledge of non-profit-focused tech stacks. Excellent communication, self-motivation, and problem-solving skills help you excel in remote and cross-cultural team environments. These abilities ensure you can deliver effective technology solutions that support NGO missions and operate efficiently in distributed settings.

What is the difference between Remote Ngo Software Engineer vs Remote Nonprofit Software Developer?

AspectRemote Ngo Software EngineerRemote Nonprofit Software Developer
CredentialsRelevant coding certifications, nonprofit sector experienceSame as above, often with nonprofit-specific knowledge
Work EnvironmentRemote, nonprofit organizations, tech teamsRemote, nonprofit sector projects
Employer & IndustryNonprofit organizations, NGOsNonprofit organizations, NGOs
Search & Comparison IntentUnderstanding roles in nonprofit tech projectsSimilar, focusing on nonprofit sector software roles

The main difference between a Remote Ngo Software Engineer and a Remote Nonprofit Software Developer lies in terminology and specific job focus. Both roles typically require similar technical skills and work in nonprofit environments. The term "Ngo" emphasizes the organizational type, while "Nonprofit" is more commonly used in job searches. Both roles aim to develop software solutions for nonprofit organizations, making their core responsibilities quite similar.

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

Remote NGO software engineers often work with teams spread across different time zones and may encounter limited resources or infrastructure compared to corporate settings. Effective communication and proactive collaboration are essential to ensure project alignment and timely delivery. Additionally, understanding the specific needs and constraints of NGOs, such as budget restrictions and compliance requirements, helps engineers create impactful, sustainable solutions. Regular check-ins, clear documentation, and utilizing project management tools can help overcome these challenges and foster a productive remote work environment.

What are Remote NGO Software Engineers?

Remote NGO Software Engineers are technology professionals who design, develop, and maintain software solutions for non-governmental organizations (NGOs) while working from a remote location. Their work supports NGO missions by creating tools such as websites, databases, mobile apps, and data analysis platforms that help manage projects, track impact, and improve communication. By working remotely, they can collaborate with international teams and contribute to global causes without being tied to a specific office location. This role often requires both technical expertise and an understanding of the unique needs and constraints of the non-profit sector.
What are the most commonly searched types of Ngo Software Engineer jobs in Wisconsin? The most popular types of Ngo Software Engineer jobs in Wisconsin are:

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Madison, WI • Remote

$123K - $162K/yr

Full-time

Posted 2 days ago

New


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.