Jobs / engineering

Staff Platform Engineer

💩 No bullshit: Big egos suck. Be open, honest and transparent. Share your mistakes openly and learn from them. Don't just talk about problems, solve them.
🎯 Grow &amp; win: Be highly curious, adaptable &amp; proactive. Embrace discomfort and change. Keep an open mindset and learn from others. You invest in our growth, so we invest in yours.
🎠 Have fun: Work hard, laugh harder. Not everything has to be serious. Be yourself, especially if you're the good kind of crazy. Sendcloud is an adventure, not a corporate maze, enjoy the ride.

SendCloud · Eindhoven

Salary shownIND sponsor

About the role

📍Eindhoven HQ (min. 1 day/week in office) | 🗓️ 40hrs per week

7+ years of hands-on engineering experience, with at least 3 years operating at senior or staff level in a platform, infrastructure, or SRE function.
Deep AWS expertise: EKS, VPC/networking, IAM, RDS/Aurora, ElastiCache, S3, CloudFront, WAF, KMS, and Lambda — you understand the stack Sendcloud runs on.
Production-grade Kubernetes: Helm, Karpenter, Envoy Gateway, KEDA, Kyverno, workload patterns, RBAC, and cluster operations at scale.
Infrastructure as Code mastery: Terraform modules, composition, and state management, with extensive experience designing modules and applying best practices at scale.
CI/CD and progressive delivery: GitLab CI, Argo CD, Argo Rollouts (canary, blue-green), pipeline design, and change failure rate reduction.
Observability as a discipline: Datadog (APM, dashboards, SLOs/SLIs, scorecards, log configuration), DORA metrics, and the ability to define what healthy looks like for a platform service.
Security thinking embedded in daily work: IAM hygiene, zero-trust principles, secrets management, JIT access, OAuth2/OIDC, audit logging, and compliance readiness (SOC2, GDPR).
Proven track record of owning and delivering complex, cross-team technical initiatives from problem framing to production — not just contributing to them.
Strong written and verbal English: you can write a compelling ADR, present trade-offs to a non-technical stakeholder, and give direct technical feedback in a code review.