ZipRecruiter

Log In

2

Remote Gitops Engineer Jobs in Washington (NOW HIRING)

Onyx Point, Inc.

Agile Developer 3 - 8813-OL

Hanover, MD · On-site +1

$78K - $250K/yr

AWS tools, Maven, , Gitlab & GitOps; Kubernetes, docker - Database : NoSQL / MongoDB Query and ... Flexible work arrangements, including remote work options * Flexible Spending Accounts (FSAs)

Career Renew

Senior Infrastructure Engineer

Washington, DC · Remote

$170K - $220K/yr

... remote role for US based candidates, they need to work EST schedule. Salary range: 170-220K USD ... Familiarity with GitOps patterns and deployment automation technologies * Expertise in DevEx or ...

Maximus

Senior Director, Secure DevOps Requisition

VA · On-site +1

$130K - $167K/yr

This is a remote position. Essential Duties and Responsibilities: - Oversee the development and ... Job-Specific Minimum Requirements: - Bachelor's degree in a closely related field (Engineer ...

Maximus

Sr. Architect - Cloud Platforms

VA · On-site +1

$65.25 - $83/hr

... and GitOps (Argo CD). - Drive shift left security adoption and developer enablement. - Align ... Remote EEO Statement Maximus is an equal opportunity employer. We evaluate qualified applicants ...

Atlassian

Senior Infrastructure Engineer

Washington, DC · Remote

$122K - $167K/yr

This is a full time, remote role across USA. Responsibilities You\'ll design and improve our ... You have experience with deployment automation and GitOps practices--ideally with ArgoCD, but ...

Onyx Point, Inc.

Software Engineer 3-BP-174

Hanover, MD · On-site +1

$78K - $250K/yr

... and PKI management Experience with GitOps development and CI/CD pipelines Basic Linux ... Flexible work arrangements, including remote work options * Flexible Spending Accounts (FSAs)

next page

Showing results 1-20

All JobsRemote Gitops Engineer JobsRemote Gitops Engineer Jobs in Washington

Remote Gitops Engineer information

What is a Remote GitOps Engineer?

A Remote GitOps Engineer is a software professional who manages and automates infrastructure and application deployments using GitOps principles, typically while working from a remote location. GitOps is a methodology that uses Git repositories as the single source of truth for declarative infrastructure and applications. The engineer is responsible for implementing, maintaining, and troubleshooting continuous deployment pipelines, ensuring that changes are version-controlled and auditable. They often work with tools like Kubernetes, ArgoCD, and Flux, collaborating with development and operations teams to streamline DevOps workflows.

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

To thrive as a Remote GitOps Engineer, you need a strong background in software development, infrastructure-as-code, and experience with cloud platforms, often supported by a degree in computer science or a related field. Familiarity with tools like Kubernetes, Docker, Terraform, Git, and CI/CD systems, along with certifications such as CKA or AWS Certified DevOps Engineer, is highly valuable. Excellent problem-solving, communication, and self-motivation are key soft skills for collaborating remotely and managing complex workflows. These skills ensure efficient, reliable, and scalable deployment pipelines, enabling teams to deliver software securely and quickly in distributed environments.

How does a Remote GitOps Engineer typically collaborate with development and operations teams to ensure smooth deployment processes?

As a Remote GitOps Engineer, you'll frequently collaborate with both development and operations teams through tools like Git, Slack, and video conferencing. Your main responsibility is to ensure deployment pipelines are automated and transparent, often acting as a bridge between developers writing code and operations teams managing infrastructure. Regular communication and documentation are crucial to resolve issues quickly and keep everyone aligned. You will also participate in code reviews, incident response, and infrastructure improvements, ensuring deployments are reliable and reproducible across distributed teams.

What is the difference between Remote Gitops Engineer vs Cloud Engineer?

AspectRemote Gitops EngineerCloud Engineer
Required CredentialsCertifications like Kubernetes, Docker, GitOps toolsCloud platform certifications (AWS, Azure, GCP), Linux skills
Work EnvironmentRemote, DevOps teams, CI/CD pipelinesRemote or on-site, cloud infrastructure management
Industry UsageDevOps, software development, automationCloud services, infrastructure, application deployment
Search & Comparison IntentFocus on automation, deployment, CI/CDFocus on cloud infrastructure, architecture

The Remote Gitops Engineer specializes in automating deployment processes using GitOps tools and practices, primarily working remotely within DevOps teams. In contrast, a Cloud Engineer manages cloud infrastructure and services across platforms like AWS, Azure, or GCP. While both roles require cloud and automation skills, the Gitops Engineer emphasizes continuous deployment and automation pipelines, whereas the Cloud Engineer focuses on infrastructure setup and management.

What are popular job titles related to Remote Gitops Engineer jobs in Washington? For Remote Gitops Engineer jobs in Washington, the most frequently searched job titles are:
What job categories do people searching Remote Gitops Engineer jobs in Washington look for? The top searched job categories for Remote Gitops Engineer jobs in Washington are:
What cities in Washington are hiring for Remote Gitops Engineer jobs? Cities in Washington with the most Remote Gitops Engineer job openings:
Remote Gitops Engineer jobs near you
Senior DevSecOps / AWS Cloud Engineer

Senior DevSecOps / AWS Cloud Engineer

GAMA-1 Technologies

Greenbelt, MD • Remote

$117K - $160K/yr

Full-time

Medical, Life, Retirement, PTO

Posted 3 days ago

Job description

Role summaryWe are seeking a remote Senior DevSecOps Engineer to own and evolve the platform — Terraform, EKS, GitLab CI/CD security gates, GitOps delivery, observability, and FISMA controls — and set the engineering standard for the team. You are the person who catches a backend block in the wrong module before it merges, and who makes the security gate something developers trust rather than route around.What you’ll do
  • Own the Terraform estate across the three repos and the 2-stack-perenv layout — directory-per-env roots, semver-pinned module consumption, a provider-pinning contract (version ranges in modules, locked in roots), S3 state with native locking, and OIDC (no static keys).
  • Lead state-safe refactors — split the monolith, fold sandbox stacks into the data stack using moved blocks / state mv, with backed-up state and zero-destroy plans on stateful resources (Aurora, Redis).
  • Build and operate EKS (toward Auto Mode), GitLab CI (runner-onEKS), and Argo CD GitOps — Helm, image signing, Kyverno admission, OPA policy decisions.
  • Harden the CI/CD security gate: container/filesystem scanning (Trivy), secret detection (Gitleaks), SBOM + signing, policy-as-code deny-gates, and ECR scan-on-push — wired so a failing gate blocks the merge.
  • Stand up the AWS-native observability stack (CloudWatch /
Container Insights, AMP, X-Ray/ADOT, Managed Grafana, Application Signals) with SLOs, alarms-as-code, and a dead-man’s-switch on the alerting path itself.
Drive the private-network migration (TGW egress, VPC endpoints, no NAT/IGW) and close FISMA gaps (CloudTrail/Config, Security Hub NIST 800-53, KMS where required, audit-account separation).
  • Review teammates’ IaC and set the standards.
Must-haves
  • Terraform at scale — root vs. child modules, state isolation, for_each/count/dynamic, drift, provider-pin conflicts, and state migration (moved/state mv) without destroying data. Writes modules others reuse. Can explain why workspaces ≠ directory-per-env.
  • Strong AWS cloud engineering — VPC/networking (private subnets, endpoints, TGW), IAM/OIDC, EKS, ECR, ALB/API-GW, and when SSE-S3 vs. KMS-CMK is actually required.
  • EKS you have operated, not just used — node/pod networking, IRSA, admission control, upgrades, troubleshooting a broken rollout.
  • CI/CD security (the “Sec” in DevSecOps) —
SAST/dependency/container scanning, secret scanning, supply-chain (SBOM, signing), policy-as-code, secrets hygiene. You have made a pipeline block on a finding.
  • Federal compliance fluency — NIST 800-53 / FISMA-Moderate; can map a control family (AU, CM, SC) to an actual implementation.
  • Writes clear PRs and reviews others’ code constructively.
Strongly preferred
  • Observability depth (OpenTelemetry, Prometheus/Grafana, SLO/errorbudget design).
  • Prior regulated/federal environment (NOAA/DoD/civilian agency, ATO process), clearance or Public-Trust history.
  • GitLab CI specifically, Argo CD, and Kubernetes runners.

GAMA-1 also offers a variety of benefits, including health insurance coverage, life and disability insurance, 401(k) savings plan, training and career development opportunities, paid holidays and paid time off (PTO - to cover vacation, illness or disability, appointments, emergencies or other situations that require time off from work). For more information click here.

ABOUT GAMA-1

GAMA-1 is a rapidly growing technology business that is based in Greenbelt, Maryland. GAMA-1 Technologies provides strategic information assurance, information security, and business enterprise and networking solutions to the Federal Government. Our success is based on the utilization of industry and agency standards, establishment of standardized processes, and IT Services expertise. At GAMA-1, we believe employees should grow, achieve, and develop just as the company grows, achieves, and develops. GAMA-1 is committed to providing our employees with opportunities for career advancement throughout their employment. For more information, visit www.gama1tech.com

GAMA-1 is an Equal Opportunity Employer and all qualified applicants will receive consideration for employment without regard to: veteran status, uniformed servicemember status, race, color, religion, sex, sexual orientation, gender identity, age, pregnancy (including childbirth, lactation and related medical conditions), national origin or ancestry, citizenship or immigration status, physical or mental disability, genetic information (including testing and characteristics), domestic violence victims, political orientation, status as a smoker or tobacco user, hairstyle, use of a service animal, education status, familial status, HIV/AIDS status, height, weight, reproductive healthcare decisions or any other category protected by federal, state or local law.