DevOps Architect

A Day in The Life of Our DevOps Architect:

As a DevOps Architect, you’ll lead the design, implementation, and evolution of our infrastructure and deployment architecture at scale. Your day-to-day will involve a mix of hands-on engineering, long-term strategic planning, and technical leadership.

• You will be a member of a cross-functional team of up to thirty people, including other DevOps engineers, and will act as an architect and trusted advisor for all things DevOps, infrastructure, and platform engineering.
• Collaborate closely with other architects and engineering leaders to define scalable, secure, and observable infrastructure patterns that support our A365 product at global scale.
• Participate in roadmap planning and ongoing project management, ensuring technical initiatives align with broader strategic goals.
• Build clear and trusted relationships with development teams, improving the developer experience by removing friction and unblocking technical barriers.
• Lead the evolution of our internal DevOps platform, shaping its architecture, capabilities, and adoption to meet the growing needs of our engineering teams and business.
• Evaluate, design, and implement cloud-native patterns using AWS, Kubernetes and other Cloud Native tools for high availability, resilience, self-healing, and efficient operations.
• Drive architectural decisions across CI/CD, cloud infrastructure, monitoring, and compliance.
• Spearhead the evolution of Infrastructure as Code standards and tools (e.g., Terraform), ensuring consistency and reusability across teams and environments.
• Mentor and coach engineers on design principles, automation patterns, and operational excellence.
• Champion continuous improvement in automation, system performance, cost optimization, security posture, engineering standards, and deployment workflows across our cloud environments.
• Help build and scale a world-class DevOps organization by participating in hiring and recruitment efforts.

Who You Are and What You’ll Need for This Position:

You bring a deep understanding of modern DevOps and infrastructure architecture and are motivated by the challenge of building reliable, scalable systems used globally. You understand not only how to build robust platforms, but how to guide teams in doing so consistently and securely.

• 6+ years of experience in DevOps, Platform Engineering, Site Reliability Engineering, or Infrastructure roles.
• Bachelor’s degree in computer science or related field
• Proven experience designing and operating production systems in cloud environments, using AWS or another major cloud provider (deep familiarity with EC2, ECS, EKS, RDS, Lambda, VPC, ALB/NLB, S3, Route53, OpenSearch or equivalent technologies in other cloud providers).
• Expert-level knowledge of Kubernetes internals, ecosystem tools (e.g., Helm, ArgoCD), and best practices for multi-region, production-grade clusters.
• Strong Infrastructure as Code experience using Terraform.
• Experience with CI/CD platforms (e.g., Github Actions, GitLab CI, Jenkins, or similar), including self-hosted CI/CD systems.
• Strong software engineering fundamentals and the ability to write automation and tooling in Go, Python, or Bash.
• Experience leading architectural decisions for Kubernetes-based computer platforms.
• Comfortable with event-driven and microservices-based architecture, service discovery, and distributed system design.
• Proven experience of building developer platforms for mid-size and enterprise customers.
• Strong background in monitoring and observability (NewRelic, Datadog, Prometheus/Grafana/Loki/Tempo, or similar APM/logging/metrics tools).
• Track record of mentoring engineers and influencing technical direction at team and org level.
• Familiarity with security tooling and policy-as-code is a plus.
• Familiarity with other cloud providers is a plus.
• Familiarity with Data Analytics tooling and architecture is a plus (e.g. Databricks, Airflow, Kinesis/Firehose).
• Good communication skills and the ability to bridge the gap between technical and non-technical stakeholders.