2

Remote Full Stack Software Engineer Jobs in New Hampshire

Software Engineer Location: Dover, NH Job Type: Full-Time / Permanent Company Overview Q LLC is a ... Experience collaborating with offsite/remote teams, with excellent communication skills to ensure ...

With more than 50 developers, AI & Fullstack engineers, UX designers and consultants working directly with other WongDoody teams, we are team players and specialists - oth in frontend and backend. As ...

Senior Software Engineer, Backend

Concord, NH · On-site +1

$165K - $241K/yr

... the software development lifecycle. Preferred Qualifications * Programming experience in Rust ... The full salary range for certain locations is listed below. For locations not listed below, the ...

This position partners with software engineers, DevOps teams, and security professionals to embed security into the full software development lifecycle. Collaborate within an expanding Cybersecurity ...

$139K - $168K/yr

Previous software engineering experience via an internship, work experience, or coding competition ... LI-SS2 LI-REMOTE

$139K - $168K/yr

Previous software engineering experience via an internship, work experience, or coding competition ... LI-SS2 LI-REMOTE

$139K - $168K/yr

Previous software engineering experience via an internship, work experience, or coding competition ... LI-SS2 LI-REMOTE

$139K - $168K/yr

Previous software engineering experience via an internship, work experience, or coding competition ... LI-SS2 LI-REMOTE

next page

Showing results 1-20

Remote Full Stack Software Engineer information

How does a Remote Full Stack Software Engineer typically collaborate with team members across different time zones?

As a Remote Full Stack Software Engineer, collaboration often involves asynchronous communication tools like Slack, project management platforms such as Jira or Trello, and regular video meetings scheduled to accommodate various time zones. You may need to plan your workday to overlap partially with teammates for real-time discussions, while also making use of detailed documentation and code reviews to keep everyone aligned. This remote setup encourages strong written communication skills and self-motivation, but also fosters a results-oriented environment where deliverables and clear updates are highly valued.

What is the difference between Remote Full Stack Software Engineer vs Remote Front End Developer?

AspectRemote Full Stack Software EngineerRemote Front End Developer
Required skillsProficiency in both front-end and back-end technologies, such as JavaScript, Python, or Java, along with database managementExpertise in front-end technologies like HTML, CSS, JavaScript, and frameworks like React or Angular
Work environmentTypically involved in full project development, working across server, database, and client-sideFocuses primarily on user interface and client-side development
Common industry usageUsed in startups, tech companies, and agencies requiring versatile developersCommon in companies emphasizing UI/UX and front-end design

The main difference is that a Remote Full Stack Software Engineer handles both front-end and back-end development, while a Remote Front End Developer specializes in creating and optimizing user interfaces. Full Stack Engineers have broader responsibilities, whereas Front End Developers focus on the visual and interactive aspects of applications.

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

To thrive as a Remote Full Stack Software Engineer, you need strong proficiency in both front-end (e.g., React, Angular) and back-end (e.g., Node.js, Python, Java) development, often supported by a relevant degree or equivalent experience. Familiarity with version control systems like Git, cloud platforms (AWS/Azure), and continuous integration tools are typically required, and certifications in these technologies can be advantageous. Exceptional problem-solving skills, self-motivation, and clear communication are vital soft skills, especially when collaborating across distributed teams. These abilities ensure you can independently deliver high-quality, scalable solutions while maintaining effective teamwork in a remote environment.

What is a Remote Full Stack Software Engineer?

A Remote Full Stack Software Engineer is a professional who designs, develops, and maintains both the front-end and back-end components of web applications while working from a location outside of a traditional office. They are proficient in multiple programming languages and frameworks, enabling them to handle tasks across the entire software development lifecycle. Remote Full Stack Engineers collaborate with team members using online tools and communication platforms, ensuring projects are delivered efficiently regardless of their physical location.
What are popular job titles related to Remote Full Stack Software Engineer jobs in New Hampshire? For Remote Full Stack Software Engineer jobs in New Hampshire, the most frequently searched job titles are:
What job categories do people searching Remote Full Stack Software Engineer jobs in New Hampshire look for? The top searched job categories for Remote Full Stack Software Engineer jobs in New Hampshire are:
Infographic showing various Remote Full Stack Software Engineer job openings in New Hampshire as of July 2026, with employment types broken down into 92% Full Time, 4% Part Time, and 4% Contract. Highlights an 89% Physical, 4% Hybrid, and 7% Remote job distribution.

Senior Software Engineer Applied AI

Advanced Monitored Caregiving Inc.

Concord, NH • Remote

$123K - $162K/yr

Full-time

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