About the role

We are looking for a Senior DevOps Engineer to own the infrastructure and delivery layer supporting our engineering teams. You will manage Kubernetes on EKS, evolve Terraform-based infrastructure as code, and build GitOps pipelines with GitHub Actions, ArgoCD, and Atlantis. This role also covers observability, security posture, and partnering directly with Tech Leads to translate requirements into production-ready infrastructure, with a part-time engagement through December.

What you will do

  • Infrastructure as Code: Own and evolve Terraform-based IaC for AWS resources, applying review discipline and change-safety practices to infrastructure the way engineers apply them to application code.
  • Kubernetes Platform Operations: Provision, configure, and maintain EKS clusters — workload scheduling, autoscaling, resource limits, ingress, and networking — supporting both long-running services and containerized batch/worker processing.
  • CI/CD & GitOps Delivery: Build and maintain deployment pipelines using GitHub Actions, ArgoCD, and Atlantis, with a focus on repeatable, auditable, low-drama releases and clear rollback paths.
  • Environment & Secrets Management: Maintain consistent, reproducible environments across dev/staging/prod, including secrets handling, configuration, and IAM/permission boundaries.
  • Observability: Instrument the platform for logging, metrics, tracing, and alerting so that engineers can diagnose their own issues, and so that failures surface before users find them.
  • Data & Application Infrastructure Support: Provision and support the infrastructure underpinning the data stack (S3-backed data lake, Glue/Athena, Airflow-orchestrated batch processing) and application dependencies (PostgreSQL, Redis) — supporting the platform, not authoring the pipelines or application logic.
  • Requirements Partnership: Work directly with Tech Leads and client engineers to clarify functional and non-functional requirements — capacity, latency, availability, cost, and security — rather than taking infrastructure requests at face value.
  • Cost & Reliability Stewardship: Monitor and challenge infrastructure cost and reliability tradeoffs, surfacing them early rather than after the bill or the incident.
  • Synchronous Collaboration: Work daily alongside client engineers over Slack and Google Meet.

Must haves

  • 5–7 years of DevOps, SRE, or platform engineering experience with a track record of owning production infrastructure.
  • AWS depth: hands-on production experience across core services — EKS, S3, IAM, VPC/networking, RDS — with the ability to reason about cost and security implications of design choices, not just get things running.
  • Kubernetes: real operational experience with EKS or comparable managed Kubernetes — deployments, services, ingress, autoscaling, resource management, and debugging workloads that misbehave in production.
  • Infrastructure as Code: strong Terraform proficiency, including module design, state management, and safe change practices for live infrastructure.
  • CI/CD & GitOps: hands-on experience building pipelines with GitHub Actions (or comparable), and with GitOps-style continuous delivery via ArgoCD, Flux, or similar. Exposure to Atlantis or an equivalent PR-driven Terraform workflow.
  • Containerization: Docker fluency — image design, layer/size optimization, multi-stage builds, and registry management.
  • Observability: experience instrumenting systems with logging, metrics, tracing, and alerting (CloudWatch, Datadog, Prometheus/Grafana, OpenTelemetry, or comparable).
  • Scripting & automation: strong Bash, plus enough Python to write and maintain automation, tooling, and glue code — this role reads and writes real code, even if it doesn't own the application.
  • Security fundamentals: least-privilege IAM design, secrets management, network segmentation, and a working understanding of how identity/authorization flows (e.g., Auth0-based) affect infrastructure design.
  • Data infrastructure literacy: enough familiarity with object-storage-backed data lakes and serverless query engines (S3/Glue/Athena or equivalent) and DAG-based orchestrators (Airflow or comparable) to provision, support, and troubleshoot them — without owning pipeline authorship.
  • Highly comfortable in Mac/Linux terminal-centric environments (Bash, Makefiles).
  • Practical, hands-on use of AI-assisted development tools (e.g., Claude Code), paired with the critical judgment to challenge AI output when it compromises long-term maintainability — a bar that applies with particular force to infrastructure code, where an unreviewed AI-suggested change can affect live systems.
  • Strong soft skills (mandatory, not a bonus): the ability to hold and defend a technical opinion — challenging a stakeholder's or a tool's proposed "quick fix" with sound reasoning in pursuit of a solution that scales and is maintainable long-term, while still being pragmatic enough to ship.
  • Risk awareness around stateful systems (mandatory): the instinct to identify and clearly communicate data-integrity and availability risks without being prompted — distinguishing reversible changes from irreversible ones, and treating anything touching persistent state or live traffic with appropriate caution.
  • Comfort with ambiguity (mandatory): work is frequently ad hoc and underspecified. This role requires defining the problem — gathering context, identifying constraints, and framing the work — before solving it, rather than waiting for a specification. Experience limited to well-specified work executed through agent workflows is not a fit.
  • Upper-Intermediate English level.

Nice to haves

  • Direct production experience with Atlantis, ArgoCD, or Athena/Glue specifically.
  • Experience running Airflow or a comparable orchestrator as a platform service.
  • Auth0, openfga/ReBAC, or fine-grained authorization infrastructure experience.
  • FinOps or sustained AWS cost-optimization work.
  • Service mesh, advanced Kubernetes networking, or multi-cluster operations.
  • Database operations experience — PostgreSQL tuning, backup/restore strategy, and supporting migrations against live systems.
  • Exposure to AWS Bedrock or the infrastructure/permissions side of LLM-backed workloads.
  • Incident response and postmortem practice in a team setting.

Perks

  • Growth without limits: build your skills through mentorship, internal TechTalks, challenging projects, and a dedicated annual learning budget
  • Competitive compensation: get recognition that reflects your skills and impact, with regular performance and compensation reviews
  • Flexibility: work 100% remotely with flexible hours that support focus, autonomy, and a healthy work rhythm
  • Meaningful, modern projects: build impactful products using modern technologies alongside global teams and leading brands
  • Collaborative culture: join a supportive environment with zero micromanagement where ideas are welcomed and contributions are recognized
  • Well-being & support: access local well-being programs and people-focused support tailored to your location

Didn’t find the perfect fit?

Subscribe to get notified about new roles that match your skills and interests.

Get role alerts

Hiring process timeline

We designed our hiring process to be fast, transparent, and convenient — so you always know what to expect and can move through the steps without unnecessary delays.

lightning-iconA quick note

After applying, keep an eye on your inbox — including your spam folder. Occasionally, emails from our hiring platform, LaunchPod, may land there.

1

Tell us about yourself

Submit a short application form.

2

Pass a quick test

Pass a 30’- 60’ test.

3

Record a short video

Introduce yourself on video to fast-track your application process.

4

Meet our team

Once you pass the video review, grab a spot on our calendar for a technical interview.

5

Get an offer

Welcome to AgileEngine!

FAQ

Have any questions?

What is the work format and schedule?

We are a remote-first company, so all our positions are remote. Schedules are flexible, but the main requirement is to have an overlap with your client’s schedule to ensure smooth collaboration. Specific details depend on the project and are discussed during the interview process.

What level of English is required?

We look for Upper-Intermediate (B2) proficiency or higher. Since you will be collaborating with international teams and global clients (including Fortune 500 companies), English is a part of your daily work.

Does AgileEngine provide work equipment?

It depends on your location. We provide equipment in Ukraine, Poland, Argentina, Colombia, Mexico, Brazil, Guatemala, Portugal, Spain, and India. In the USA, equipment is usually provided by the client; otherwise, you will be expected to use your own setup.

What opportunities for professional growth do you offer?

We support continuous growth through personalized development paths tailored to each expert. Also, you can expect:

  • An annual learning and development budget
  • Internal workshops, tech talks, and mentorship programs
  • Opportunities to switch projects or grow into new roles over time

What does a typical team look like, and what tools do you use?

Teams vary by project, but you’ll usually work with a mix of experts across different fields, along with a delivery or project manager who supports collaboration and onboarding.

For day-to-day work, teams commonly use tools like Jira and Google Workspace, along with communication platforms such as Google Chat. Depending on the client, you may also work with Slack, Confluence, Notion, or similar tools.

Need help?

Want more details? See full FAQ

If something doesn’t work or you have questions regarding your application process, drop us a line.

    Scroll to Top