Senior DevOps Engineer - Belgrade or Warsaw, hybrid

Build the platform that turns repeatable delivery into the default.

We are hiring two senior/staff DevOps engineers for two separate teams supporting our Distributed Fleet Management platforms: Evo and Advantage X.

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.

Location

Belgrade or Warsaw, hybrid

Our job is to make product delivery reliable, repeatable, and easier for engineering teams. In practice, we:

· Own the platform. Operate and evolve the infrastructure and delivery foundations.

· Enable developers. Provide clear paths for environments, builds, releases, local development, and troubleshooting so teams can ship without avoidable friction.

· Automate infrastructure. Treat infrastructure changes as software: versioned, reviewed, tested, and reproducible.

· Keep delivery safe. Embed access control, secrets management, hardening, scanning, and compliance checks into normal engineering workflows.

· Operate for outcomes. Use observability to understand reliability, performance, and business impact rather than producing dashboards without decisions behind them.

· Make architecture explicit. Define problems, surface trade-offs, document decisions, and challenge complexity that does not serve the product.

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

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.

4. 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.

We are looking for a senior engineer ready to operate with staff-level impact: strong judgment, practical depth, ownership of outcomes, and close collaboration with the developers who use the platform.

· High agency. You take ownership, move work forward, and challenge assumptions when they do not serve the product or business outcome.

· Automation-first thinking. You know the difference between a script and a system that can be operated, changed, and trusted.

· Engineering discipline. You treat infrastructure and automation as software: versioned, reviewed, tested, and documented.

· System design judgment. You can explain trade-offs between simplicity and capability, immediate delivery and future cost, and local optimization and platform-wide impact.

· Networking: Network automation, AWS networking, service mesh, connectivity, and systematic troubleshooting.

· Terraform and AWS: Reusable infrastructure design, state and lifecycle decisions, testing, security, and safe change at scale.

· Linux: Operating-system troubleshooting, practical automation, and strong command-line fluency.

· Kubernetes: Production clusters, storage, networking, RBAC, zero-trust approaches, resource management, high availability, troubleshooting, Helm, Argo CD, and Istio.

· Security automation: Secrets management, access control, hardening, scanning, and continuous compliance controls.

· Internal Developer Platforms: Backstage Platform architecture, developer self-service, paved roads, reusable capabilities, governance, adoption, and clear product boundaries.

· Microservices system design: Service boundaries, communication patterns, resilience, scalability, observability, data ownership, failure handling, and operational tradeoffs.

You will have two interviews with practitioners and your future manager. The discussion will focus on:

· how you reason about system design, automation, and operational trade-offs;

· your understanding of the tools and concepts you use, beyond executing pre-built commands or pipelines;

· your ideas, professional interests, communication, and working style.

There are no LeetCode exercises or whiteboard coding sessions.