2

Remote Nixos Jobs (NOW HIRING)

Familiarity with Nix or NixOS for reproducible builds and development environments * Experience ... remote and/or hybrid work available depending on position. All compensation and benefits are ...

Familiarity with Nix or NixOS for reproducible builds and development environments * Experience ... remote and/or hybrid work available depending on position. All compensation and benefits are ...

Remote Nixos information

What is the difference between Remote Nixos vs Remote Linux System Administrator?

AspectRemote NixosRemote Linux System Administrator
CredentialsKnowledge of NixOS, Linux fundamentals, scriptingLinux certifications (e.g., RHCE), scripting, system management
Work EnvironmentPrimarily remote, focused on NixOS configurations and deploymentRemote or on-site, managing various Linux distributions
Industry UsageTech companies using NixOS for reproducible environmentsBroad industry, including IT, finance, and healthcare
Search & Comparison IntentFocus on NixOS-specific skills and toolsGeneral Linux system management skills

Remote Nixos specialists focus on managing NixOS environments, emphasizing declarative configuration and reproducibility, while Remote Linux System Administrators handle a wider range of Linux distributions, focusing on system stability, security, and user support. Both roles require Linux knowledge but differ in specific tools and environment focus.

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

To thrive as a Remote NixOS Engineer, you need a strong understanding of Linux system administration, NixOS configuration, and declarative infrastructure management, typically backed by experience with open-source systems. Familiarity with tools like Nix, NixOps, Git, and CI/CD pipelines, as well as relevant certifications such as LFCS or RHCSA, is highly valuable. Excellent problem-solving abilities, self-motivation, and clear asynchronous communication are essential soft skills for remote collaboration and troubleshooting. These skills and qualities ensure reliable, maintainable infrastructure and effective teamwork in distributed environments.

What are some common challenges faced by professionals working remotely with NixOS, and how can they be overcome?

One common challenge for remote NixOS professionals is ensuring consistent development environments across distributed teams, as differences in system configurations can lead to unexpected issues. To overcome this, teams often leverage Nix's declarative configuration and reproducible builds, which help maintain uniformity regardless of where code is deployed. Additionally, clear documentation and regular communication are essential to synchronize configuration changes and troubleshooting. Emphasizing collaboration via version control and remote pairing tools can further mitigate challenges and foster efficient teamwork.

What is a Remote NixOS engineer?

A Remote NixOS engineer is a professional who specializes in deploying, configuring, and maintaining systems using the NixOS operating system while working from a remote location. NixOS is a unique Linux distribution known for its declarative configuration and reproducible builds, making it popular for infrastructure automation and DevOps tasks. Remote NixOS engineers often collaborate with teams to manage infrastructure, automate deployments, and ensure system reliability, all while working outside of a traditional office environment. Their skills are especially valuable for organizations seeking flexible, scalable, and reliable system management solutions.
More about Remote Nixos jobs
What cities are hiring for Remote Nixos jobs? Cities with the most Remote Nixos job openings:
What are the most commonly searched types of Nixos jobs? The most popular types of Nixos jobs are:
What states have the most Remote Nixos jobs? States with the most job openings for Remote Nixos jobs include:
Infographic showing various Remote Nixos job openings in the United States as of June 2026, with employment types broken down into 91% Full Time, 6% Part Time, and 3% Contract. Highlights an 37% Physical, 3% Hybrid, and 60% Remote job distribution.
Software Engineer II, ML Ops, tvScientific

Software Engineer II, ML Ops, tvScientific

Pinterest

San Francisco, CA • Remote

Other

Posted yesterday


Job description

About tvScientific

tvScientific is the first and only CTV advertising platform purpose-built for performance marketers. We leverage massive data and cutting-edge science to automate and optimize TV advertising to drive business outcomes. Our solution combines media buying, optimization, measurement, and attribution in one, efficient platform. Our platform is built by industry leaders with a long history in programmatic advertising, digital media, and ad verification who have now purpose-built a CTV performance platform advertisers can trust to grow their business.

In this role, you'll work at the intersection of SRE and low-latency distributed systems, with plenty of room to go deep on complex technical problems. You'll help build and operate the platform that powers AI model training, deployment and serving, contributing to meaningful, production-facing projects from day one.

You'll think about queries and RPCs in terms of syscalls, cache lines and wire formats, and design systems that stay fast and predictable under load. You'll help define and harden the foundation for our training and serving stack: from storage and indexing strategies, to streaming and fanout, to backpressure and failure handling across services and regions. You'll work closely with software engineering, data infra and SRE partners to ensure our systems are observable, debuggable and operable in production. You'll interact with IO scheduling and batching, lock-free and low-contention data structures, connection pooling, query planning, kernel and network tuning, on-disk layout and indexing, circuit breaking, autoscaling, incident response, NixOS, Rust and robust SLIs/SLOs.

What you'll do
  • Contribute to the infrastructure supporting AI workflows - training pipelines, Kubernetes deployments and CI/CD.
  • Help improve the developer experience for the data science team - small frictions add up, and you'll help eliminate them.
  • Build out and improve observability tooling - learning to see the system clearly is a core skill we'll develop together.
  • Keep deployments clean and correct as the platform evolves.
  • Grow into a deeper technical contributor under the mentorship of senior engineers who have done this at high scale.
What we're looking for
  • A genuine, demonstrable depth in Linux - hands-on experience beyond basic usage (for example, debugging, configuration or performance tuning).
  • Strong software engineering fundamentals - you write clean code, reason about systems and debug methodically.
  • A systems-oriented mindset - you think about why things work, not just that they work.
  • Early exposure to reliability concepts - CI/CD, infrastructure-as-code or similar.
  • An ownership mindset - especially when diagnosing and resolving production or project issues.
  • Comfort using AI tooling to accelerate your work, with the discipline to verify what it produces.
  • Demonstrated ability to use AI to improve speed and quality in your day-to-day workflow for relevant outputs.
  • A track record of critically evaluating and validating AI-assisted work (for example, testing, source checking, data validation, peer review).
  • High integrity and ownership: you protect sensitive data, avoid over-reliance on AI and remain accountable for final decisions and deliverables.
  • 2+ years of experience building and operating high-performance distributed systems.
  • Bachelor's degree in computer science, engineering, a related field or equivalent experience.
  • Nice-to-haves
    • Experience with NixOS or other tools for reproducible builds, and an interest in making development environments predictable and reliable.
    • Experience with Zig or similar low-level languages, and curiosity about what your compiler and runtime are doing under the hood.
    • You've reverse-engineered something - a protocol, a binary, a game, etc.
    • You've deployed something real to Kubernetes, even if it was a homelab.
    • Experience with Terraform or other infrastructure-as-code tools in a real context.
    • Exposure to adtech, CTV or other high-performance/low-latency environments.
    • Python or Scala experience in a data-adjacent context.

In-Office Requirement Statement:

  • We recognize that the ideal environment for work is situational and may differ across departments. What this looks like day-to-day can vary based on the needs of each organization or role.


Relocation Statement:

  • This position is not eligible for relocation assistance. Visit our PinFlex page to learn more about our working model.

#LI-SM4

#LI-REMOTE