Senior DevOps Engineer

About the position

We are seeking a Senior DevOps Engineer with a proven history of designing and managing large-scale infrastructure. This role involves identifying needs, architecting solutions, and implementing them from start to finish. The ideal candidate is proficient in writing Terraform modules, troubleshooting CI pipelines, and leading initiatives to enhance deployment reliability. Experience in high-stakes, complex systems, particularly in regulated or safety-critical domains, is essential. The ability to take end-to-end ownership and deliver solutions independently is highly valued. This position offers the unique opportunity to build infrastructure that supports software for real aircraft, moving beyond typical SaaS platforms. Unlike many senior DevOps roles, there is no on-call rotation, ensuring nights and weekends are free.

Responsibilities

  • Infrastructure Architecture: Own the design and evolution of Merlin's cloud and on-premises infrastructure across AWS and Azure. Make architectural decisions that balance cost, reliability, security, and compliance.
  • Infrastructure as Code: Lead Terraform-based IaC initiatives across the organization. Establish standards, review infrastructure changes, and drive the team toward fully code-managed environments.
  • CI/CD Platform Ownership: Set the technical direction for CI/CD pipelines across multiple interdependent systems using GitHub Actions. Drive reliability, performance, and maintainability improvements at the platform level.
  • Security & Compliance: Own DevSecOps tooling — security scanning (SAST, SCA, container scanning), SBOM generation, and artifact integrity. Ensure pipelines meet contractual and regulatory obligations including export control and CDRL requirements.
  • Cloud Environment Management: Manage cloud infrastructure across commercial and government-aligned environments, including Azure GCC High or equivalent FedRAMP/DoD-compliant platforms.
  • Deployment Automation: Design and improve deployment pipelines to test systems, bench hardware, and flight test aircraft using Docker, Debian packaging, Ansible, and JFrog Artifactory.
  • Cross-Team Collaboration: Partner with flight software engineers, systems engineers, IT, and leadership to ensure infrastructure supports program priorities. Communicate clearly and document your work to drive adoption across teams.

Requirements

  • 3–5 years of experience in DevOps, Platform Engineering, Site Reliability Engineering, or a related role
  • Deep expertise with Infrastructure as Code — Terraform required; CloudFormation or Pulumi also acceptable
  • Strong hands-on experience with AWS and Microsoft Azure — AWS is our primary cloud for engineering infrastructure; both platforms are active parts of the role
  • Strong experience with CI/CD platforms — GitHub Actions preferred; Jenkins, GitLab CI, or CircleCI also acceptable
  • Solid experience with Linux system administration (Ubuntu preferred)
  • Proficiency with Docker for building, publishing, and deploying container images
  • Strong scripting skills in Python and Bash
  • Experience with security and compliance tooling — SAST, SCA, SBOM generation, container scanning, or artifact signing
  • Experience with configuration management tools — Ansible preferred; Chef, Puppet, or similar also acceptable — including managing software and configuration state across physical systems and embedded hardware targets (e.g., bench hardware, flight test aircraft), not just cloud or server infrastructure
  • Familiarity with artifact repositories — JFrog Artifactory, Nexus, or similar package/container registries
  • Strong problem-solving skills, attention to detail, and ability to work independently with minimal direction
  • Excellent communication and documentation skills

Nice-to-haves

  • Experience with government-aligned cloud environments — Azure Government, GCC High, or equivalent FedRAMP/DoD-compliant platforms
  • Experience working in GCC High (Microsoft Azure Government Community Cloud) or other FedRAMP/DoD-compliant cloud environments
  • Experience with Debian packaging (dpkg, dch, Launchpad PPAs, or S3-hosted APT repos)
  • Experience with software products that include a physical systems component — aircraft, robotics, medical devices, autonomous vehicles, or similar
  • Familiarity with distributed pub/sub frameworks (e.g., ROS2) and underlying middleware such as DDS and Zenoh
  • Knowledge of networking fundamentals and network security best practices
  • Experience working in a regulated environment (aerospace, automotive, medical, defense) where traceability and process compliance matter
  • Familiarity with SITL (Software-in-the-Loop) or HIL (Hardware-in-the-Loop) simulation infrastructure
  • Familiarity with dev containers and containerized development environments
  • Familiarity with orchestration techniques for automated regression and simulation-level integration testing (e.g., ReSim or similar frameworks)
Back to blog

Common Interview Questions And Answers

1. HOW DO YOU PLAN YOUR DAY?

This is what this question poses: When do you focus and start working seriously? What are the hours you work optimally? Are you a night owl? A morning bird? Remote teams can be made up of people working on different shifts and around the world, so you won't necessarily be stuck in the 9-5 schedule if it's not for you...

2. HOW DO YOU USE THE DIFFERENT COMMUNICATION TOOLS IN DIFFERENT SITUATIONS?

When you're working on a remote team, there's no way to chat in the hallway between meetings or catch up on the latest project during an office carpool. Therefore, virtual communication will be absolutely essential to get your work done...

3. WHAT IS "WORKING REMOTE" REALLY FOR YOU?

Many people want to work remotely because of the flexibility it allows. You can work anywhere and at any time of the day...

4. WHAT DO YOU NEED IN YOUR PHYSICAL WORKSPACE TO SUCCEED IN YOUR WORK?

With this question, companies are looking to see what equipment they may need to provide you with and to verify how aware you are of what remote working could mean for you physically and logistically...

5. HOW DO YOU PROCESS INFORMATION?

Several years ago, I was working in a team to plan a big event. My supervisor made us all work as a team before the big day. One of our activities has been to find out how each of us processes information...

6. HOW DO YOU MANAGE THE CALENDAR AND THE PROGRAM? WHICH APPLICATIONS / SYSTEM DO YOU USE?

Or you may receive even more specific questions, such as: What's on your calendar? Do you plan blocks of time to do certain types of work? Do you have an open calendar that everyone can see?...

7. HOW DO YOU ORGANIZE FILES, LINKS, AND TABS ON YOUR COMPUTER?

Just like your schedule, how you track files and other information is very important. After all, everything is digital!...

8. HOW TO PRIORITIZE WORK?

The day I watched Marie Forleo's film separating the important from the urgent, my life changed. Not all remote jobs start fast, but most of them are...

9. HOW DO YOU PREPARE FOR A MEETING AND PREPARE A MEETING? WHAT DO YOU SEE HAPPENING DURING THE MEETING?

Just as communication is essential when working remotely, so is organization. Because you won't have those opportunities in the elevator or a casual conversation in the lunchroom, you should take advantage of the little time you have in a video or phone conference...

10. HOW DO YOU USE TECHNOLOGY ON A DAILY BASIS, IN YOUR WORK AND FOR YOUR PLEASURE?

This is a great question because it shows your comfort level with technology, which is very important for a remote worker because you will be working with technology over time...