DevOps Engineer
Upload My Resume
Drop here or click to browse · PDF, DOCX, DOC, RTF, TXT
Requirements
• Experience supporting distributed systems or multi-service architectures. • Experience in regulated, high-reliability, or enterprise environments. • Infrastructure-as-code experience (e.g., Nix, Terraform, or similar). • Experience operating cloud infrastructure (AWS, GCP, Azure). • Contributions to open-source projects, tooling, or public infrastructure repositories.
Responsibilities
• Design, build, and maintain infrastructure and deployment pipelines supporting applications. • Support and evolve Linux-based systems, including a transition to Nix / NixOS and reproducible build environments. • Create and maintain CI/CD pipelines for Scala- and TypeScript-based services. • Partner closely with software engineers to improve: • build and release workflows • observability, reliability, and operational tooling • Operate and support production systems with a focus on reliability, security, and auditability. • Help standardize configuration, tooling, and environments across development and production. • Participate in incident response, root cause analysis, and continuous improvement. • Document systems, processes, and operational knowledge clearly and thoughtfully.
Benefits
• Play a key role in a thoughtful transition to reproducible, declarative infrastructure using Nix. • Collaborate with strong engineers solving genuinely hard technical problems. • Emphasis on correctness, maintainability, and long-term system health—not quick hacks. • Strong learning culture with support for deep technical growth. • Remote-first, flexible work environment. • Competitive compensation based on experience and location. • We care more about what you’ve built and operated than where you’ve worked. Please include: • Your resume or CV. • Links to GitHub, GitLab, or other public repositories showing infrastructure code, tooling, automation, or systems work you’ve done. • Open-source contributions, side projects, or examples of non-trivial operational systems are highly encouraged. • If a repository represents team-based work, please briefly describe your personal contributions.