> Markdown version of [/jobs/ext/4094415-staff-engineer-platform](https://www.wearedevelopers.com/jobs/ext/4094415-staff-engineer-platform). 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).

---

# Staff Engineer, Platform

- **Company:** Flexport
- **Location:** Amsterdam, Netherlands (Remote available)
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Continuous Integration, Software Debugging, Software Design Documents, Middleware, Github, Gradle, Identity and Access Management, Machine Learning, OpenID, Software Engineering, Datadog, Backend, Kubernetes, Data Analytics, Npm(Software), Graphql, Front End Software Development, Terraform, Artifactory
- **Published:** October 7, 2026
- **Apply:** https://www.adzuna.nl/details/5921035812

## About the Role

* 10+ years of software engineering experience, with significant time spent building developer platforms, internal tooling, or core infrastructure that other engineers depend on.
 * Deep full-stack instincts: you're equally comfortable in a backend service, a frontend build pipeline, a Kubernetes manifest, and a CI configuration.
 * Strong product instincts applied to internal users: you treat engineers as customers, identify what's actually worth building, and measure whether it worked.
 * Expertise and hands on experience with at least one of each: a CI/CD system (Github Actions pref), a container orchestrator (Kubernetes pref.), build tooling preferably for more than one language, backend-for-frontend (Graphql pref.), service-to-service communication (gRPC preferred), Metrics and artifact storage.
 * An appetite to take a shovel to that brown field: you thrive on fixing what's broken and building bridges to what's next. You don't just throw migrations over the wall, you either execute them yourself or make sure they feel effortless.
 * An independent mindset: you thrive in ambiguity, find the highest-leverage problems yourself, and don't wait to be told what to do.
 * Excellent communication: you can run a developer interview, write a clear design doc, and align stakeholders across teams to land platform-wide changes.
 * A generally helpful attitude. Everyone should know you within no-time as the person who gets stuff unblocked, points them in the right direction and makes their work easier. The 90's can keep their BOFH.
 * A drive for impact: you are not satisfying until every engineer is productive and confident thanks to your team.

 * Experience in data-driven DevX development using metrics such as DORA.
 * Experience with AWS.
 * Experience in Identity and Access Management (IAM) at scale such as JWTs, OIDC and fine-grained authorization.
 * Experience with Terraform.

 * We come to the office 3 times a week to hang out, whiteboard, and ship together.
 * We have the latest hardware and software, including frontier AI models on day one.
 * We're agile, but not dogmatic. Teams decide how they work best.

## Description

* Making the best paved paths and self-serve tooling possible that makes the right thing the easy thing, protected by guardrails but not locked gates.
 * Creating and supporting developers with CI/CD pipelines (Buildkit, Github Actions), build tooling (Gradle, Bazel, npm/pnpm/bun, Go and Cargo) and artifact repositories (Artifactory, ECR, github).
 * Owning and improving the backend and frontend developer experience.
 * Acting as the steward of our GraphQL and gRPC ecosystem and make sure our middleware, federation and schema sharing, CLIs, codegen and servers and clients work smooth as butter.
 * Evolving and integrating our IAM solutions and primitives so that everything is easy and secure by default.
 * Making sure engineers can easily use and understand our container orchestration (Kubernetes, ECS) and observability stack (Openmetrics, Datadog) that engineers rely on to run, understand and debug their services.
 * Doing user research with developers: shadowing engineers, running interviews, and tracking DevX metrics so that what you build is grounded on data and not assumptions.
 * Crossing organizational boundaries to align with product teams and ship changes that impact the whole engineering org.