Senior DevOps Engineer

Why this role now

The foundations exist, and the opportunities are clear. Over the next 18 to 24 months, you will help chart the direction, design the practices, and build the automation that moves both platforms toward stronger, market-standard engineering.

We are looking for people who can take ownership of entire problem areas, exercise independent judgment, and turn direction into working systems. This is not a role built around executing a predefined task list.

What we use today

The current environment spans cloud and on-prem infrastructure, Kubernetes, delivery automation, security controls, and the supporting data plane

• Infrastructure: AWS, Terraform, Linux, Ansible
• Runtime and delivery.: Kubernetes, Helm, Istio, GitHub, Jenkins, GitOps
• Artifacts and quality: Harbor, Nexus, SonarQube, Checkmarx, Trivy
• Observability: Prometheus, Grafana, FluentBit, OpenSearch,
• Services and data: SQL Databases, Caches, Queues, API gateways, Service Meshes,
• Automation: Python, Bash, Makefiles
• LLMs: ChatGPT, Codex, APM

What we want to achieve in the next 12 months

The goal is not to add more tools. It is to turn the existing platform into a consistent operating model that works across many environments.

• One Button Deployments. Move toward true one-action workflows that produce results across complex environments
• A paved road for delivery. Standardize environments, pipeline patterns, templates, local-development tooling, and release processes around clear developer workflows.
• Build Better DevEx with IDP. Strengthen self-service and robust automation to free DevOps time for more proactive work.
• Security by default. Make secrets handling, RBAC, hardening, scanning, and compliance part of delivery rather than separate cleanup work.
• Useful observability. Connect operational signals to reliability, performance, and business impact, with clear ownership and response paths.
• Reduced technical debt. Remove one-off paths, undocumented exceptions and replace parts of our internal stack with new market standards.

What we plan to use to get there

• Infrastructure as Code: Terraform on AWS, ClusterAPI
• Kubernetes delivery: Helm and ArgoCD
• Delivery automation: GitHub, Tekton, Backstage,
• Platform networking: AWS networking, Istio service mesh patterns, WAFs, Firewalls, Zero Trust Architecture.
• Operational feedback: Metrics, logs, traces, and dashboards built around actionable service and product signals.

Specific tools may change. The standard does not: solutions must be repeatable, testable, maintainable, and usable by the teams that depend on them