Responsibilities

About the Role

This isn't only maintenance work. You'll own the platform and infrastructure strategy for IntelligenEVO's cloud-based EGM management solution serving thousands of devices across air-gapped systems.

Location: Warsaw preferred, few office visits/month. Full-remote possible if you have a strong remote culture.

What You’ll Do

• Standardize deployments to true one‑button workflows (repeatable across many environments).
• Support developers by designing smooth SDLC paths: environments, CI/CD pipelines, templates, local‑dev tooling, and clear processes that unblock delivery.
• Drive Infrastructure as Code (Terraform on AWS), with tested, reviewed, and versioned changes.
• Own SDLC toolchains: Github, CI/CD (GitHub Actions/Jenkins), artifact registries (Harbor/Nexus), scanning tools (SonarQube/Trivy), deployment orchestrators (ArgoCD/Helm).
• Shape networking and service mesh patterns (VPCs, connectivity for air‑gapped systems, Istio).
• Bake in security from day one: secrets management, RBAC, hardening, compliance automation.
• Set up observability that matters (reliability, performance, business impact > vanity metrics).
• Partner with engineering to define release strategies (Helm, ArgoCD, canary/blue‑green).
• Lead through system design: define problems, make trade‑offs explicit, and document why.

Qualifications

Nice to Have few of those (Practical Experience):

• Ansible, Python, Makefiles, Bash,
• Prometheus, Grafana, Fluentbit, Opensearch, ADOT
• GitHub Administration
• Jenkins, Github Actions
• Supporting JVM/TypeScript SDLC.
• PostgreSQL, Redis, Ignite
• API gateways
• NGINX, Haproxy
• RabbitMQ, SQS

Sonarqube, Helm, Harbor, Nexus

Keys to Success

Mindset (Non‑Negotiables)

• Automation‑first: You design systems that run themselves & you know the difference between "I wrote a script" and "well-designed automation."
• Git discipline: Treat any code like software: versioned, reviewed, tested
• Shipping mindset: You can be described as high agency: you own outcomes, not tasks nor revel in busy work. You will also challenge assumptions when they don't serve business outcomes.
• System design thinking: “Why” is as important as “What” & “How.” and you can articulate decisions on trade-offs: complexity vs. maintainability, immediate vs. future cost, simplicity vs. capability
• Love the craft: Current job might suck, but you still love building infrastructure, fast, stable, clean, and systems - and elevating DevOps culture.
• DevOps mindset: You break silos, collaborate deeply with developers, and treat platform engineering as a product that serves the whole engineering org.