DevOps Engineer

Summary

Join MLabs as a proactive and independent DevOps Engineer to scale our zero-knowledge infrastructure. You will design, implement, and maintain CI/CD pipelines for a zk rollup and proving environment, automate builds, tests, and releases, and provision and manage machines for parallel SNARK proving. Responsibilities include supporting testnet deployments, monitoring health, managing upgrades, and collaborating with engineering teams. This role requires strong DevOps experience with Nix/Nixos, Terraform, Docker, and GitHub Actions, as well as experience with OCaml projects and distributed systems. The ideal candidate will possess strong problem-solving skills and excellent communication abilities.

Requirements

• Strong experience in DevOps (Nix/Nixos, Terraform, Docker, GitHub Actions, etc.)
• Experience with OCaml projects — understanding build systems like Dune, managing dependencies
• Experience deploying and managing distributed systems or proving clusters
• Comfortable with Linux systems administration, shell scripting, and automation
• Able to work independently with minimal supervision
• Comfortable owning projects from setup to maintenance
• Strong problem-solving mindset and sense of urgency
• Excellent communication in a remote-first, async environment

Responsibilities

• Design, implement, and maintain CI/CD pipelines for a zk rollup and proving environment
• Automate builds, tests, and releases
• Provision and manage machines for parallel SNARK proving at scale (cloud or bare metal)
• Support testnet deployments, monitor health, and manage upgrades
• Collaborate with protocol and engineering teams to integrate DevOps with zk circuits and infrastructure
• Implement logging, alerting, and monitoring for proving-related services

Preferred Qualifications

• Experience with Mina Protocol, o1js, or related zk-rollup technologies
• Familiarity with Ocaml or any other functional languages
• Familiarity with zero-knowledge proofs, ideally SNARKs
• Knowledge of Kubernetes or container orchestration for provers
• Exposure to testnets, forks, or zk infra deployment strategies