Devops Engineer

About the role:

We run our product on self-managed cloud infrastructure. Services are containerized and orchestrated through a lightweight self-hosted deployment platform on top of Docker no managed Kubernetes, no heavy cloud abstraction layer.

You would own this stack end to end: keeping it stable, making deploys boring, and building the monitoring and recovery story that a fully managed platform would otherwise hand us.

This suits someone who likes owning real infrastructure rather than configuring someone else's control plane.

What you'll own:

• Cloud infrastructure across providers: compute, networking, firewalls, DNS, TLS, storage and volumes
• The container layer: service definitions, resource limits, healthchecks, zero-downtime deploys, rollbacks
• Reverse proxy and ingress, routing, certificate automation, rate limiting
• CI/CD from commit to production, including image builds and registry management
• Observability: metrics, logs, traces, dashboards and alerts that page someone only when it matters
• Backups and disaster recovery, including tested restores of databases and persistent volumes a backup nobody has restored is not a backup
• Secrets management and environment configuration across environments
• Security hardening: OS patching, access policy, least-privilege, container image hygiene, CVE triage
• Capacity planning and cloud cost control
• Incident response, postmortems, and the runbooks that keep the next incident shorter

What we're looking for

• 3+ years running production Linux systems, comfortable without a managed platform underneath you
• Hands-on experience with at least one major cloud (AWS, GCP, Azure, DigitalOcean, Hetzner, OVH or similar) and the ability to work across others
• Strong Docker fundamentals: images, layers, networking, volumes, Compose, resource constraints, debugging a container that won't start
• Production experience with a reverse proxy (Traefik, nginx or Caddy) including TLS and automated certificate renewal
• CI/CD experience (GitHub Actions, GitLab CI or similar) with real build and deploy pipelines, not just lint jobs
• Monitoring and logging in practice: Prometheus/Grafana, Loki/ELK, OpenTelemetry or equivalents, plus the judgement to know what's worth alerting on
• Database operations: backups, point-in-time recovery, upgrades, connection pooling, basic query troubleshooting
• Scripting in Bash and Python or Go
• Infrastructure as code (Terraform, Ansible or Pulumi) and a bias toward reproducible setups over hand-tuned servers
• Networking literacy: DNS, TCP/IP, HTTP, private networking, VPN, firewall rules

Nice to have

• Self-hosted PaaS experience (Dokploy, Coolify, CapRover or similar)
• Docker Swarm, or Kubernetes experience alongside an honest view of when it's overkill
• Multi-cloud or migration experience, including moving workloads between providers
• Familiarity with our application stack, so you can debug with the developers rather than around them
• Experience in an on-call rotation