> Markdown version of [/jobs/ext/4099082-platform-engineer](https://www.wearedevelopers.com/jobs/ext/4099082-platform-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Platform Engineer

- **Company:** YachtCloud
- **Location:** Rotterdam, Netherlands
- **Experience:** Experienced
- **Salary:** €2,700 - €5,000
- **Contract:** Permanent contract
- **Skills:** Amazon Web Services, Bash Shell, Computer Networks, Linux, Domain Name System (DNS), Python (Programming Language), Routing, Prometheus, Software Engineering, Scripting, Grafana, Kubernetes Helm Charts, Kubernetes, Docker, Microservices
- **Published:** October 29, 2026
- **Apply:** https://www.indeed.com/viewjob?jk=675ec54ea8a13757

## About the Role

We need someone who treats Kubernetes as plumbing rather than an identity. If you care more about whether a service actually recovers after a reboot than about chasing the latest CNCF buzzword, this will suit you well.

· Production Mileage: At least 3 years working with container workloads on Kubernetes in real environments. You know what broke, why it broke, and how you fixed it.

· Packaging & Delivery: Daily comfort with Helm or Kustomize, tied into a working GitOps workflow.

· Linux Fundamentals: You are comfortable working directly in a shell. You understand container runtimes (containerd/Docker), Linux networking (DNS, routing, packet flow), and lightweight distributions like k3s.

· Practical Scripting: You reach for Bash, Python, or Go when you need to automate routine maintenance or glue systems together.

· Clear Communication: Comfortable talking trade-offs with both developers and hardware-oriented field engineers. Fluent English is required; Dutch is handy to have.

## Description

You work shoulder-to-shoulder with our software engineering and our systems team. Your job is to make sure our microservices run predictably, deploy without drama, and don't fall over when a vessel loses external connectivity.

What you will own day-to-day:

· Cluster Ops: Stand up, configure, and maintain Kubernetes environments across managed cloud (AWS) and bare-metal edge setups running k3s aboard vessels.

· Service Packaging: Sit down with developers to containerize services the right way-reasonable CPU/memory bounds, sensible health probes, multi-stage Docker builds, and zero hidden assumptions about local persistent disks.

· GitOps & Releases: Build and look after the deployment flow using GitOps tooling (ArgoCD or Flux) alongside Helm charts or Kustomize setups so pushes are deterministic and easily rolled back.

· Monitoring & Health: Hook up Prometheus, Grafana, and OpenTelemetry so we can spot resource leaks and broken services quickly-even on systems that don't have constant outbound telemetry.

· Basic Security Hygiene: Apply sensible RBAC defaults, lock down pod capabilities, configure network isolation policies, and keep credentials out of plain text.