Responsibilities
- Build and evolve the platform capabilities that product engineers use to get code from commit to production
- Improve CI/CD pipelines, build systems, release workflows, deployment automation, quality gates, observability, and developer productivity metrics
- Consolidate delivery patterns across Go, Erlang, Elixir, JavaScript/TypeScript, and other stacks where it makes sense
- Improve the speed and reliability of feedback loops, including PR checks, builds, tests, release pipelines, and deployment signals
- Simplify release systems so engineers can resolve most delivery issues without needing a platform engineer in the loop
- Embed quality and safety into the default delivery path instead of relying on manual process
- Define clear contracts for platform capabilities, covering expected inputs, guarantees provided, how they're measured, and how other platform engineers can extend them
- Partner with product teams to identify where delivery is slow, confusing, risky, or painful, and fix the underlying system rather than the symptom
- Participate in operational ownership of the systems the team runs, including debugging failures, improving runbooks, reducing toil, and helping make on-call sustainable
Requirements
- Strong software engineering fundamentals, with the ability to write and review good code, debug complex systems, and reason about trade-offs
- Hands-on experience with CI/CD, release tooling, developer platforms, infrastructure platforms, internal tooling, or similar systems
- Ability to work across different technology stacks and learn unfamiliar ecosystems without needing perfect context upfront
- Experience with containerised or cloud-native systems such as Docker, Kubernetes, GitOps, ArgoCD, Terraform, or Helm
- A practical platform mindset, with focus on adoption, reliability, simplicity, observability, and real impact for engineers
- Good operational instincts, including an understanding of failure modes, rollback paths, incident response, and monitoring
- Clear communication skills, with the ability to explain technical trade-offs to cross-functional teams without relying on jargon
Nice to Have
- Experience with Bazel, monorepos, remote caching, hermetic builds, or large-scale build systems
- Experience with Erlang, Elixir, BEAM operations, rebar3, Mix releases, or high-availability runtime environments
- Experience with JavaScript/TypeScript build and release workflows, frontend deployment pipelines, or developer-facing platform UIs
- Familiarity with GitHub Actions, Argo Workflows, GitLab CI, Jenkins, or Buildkite
- Familiarity with SonarQube, static analysis, coverage tooling, test infrastructure, or flaky-test management
- Knowledge of DORA, SPACE, CI performance metrics, or engineering effectiveness dashboards
- Experience with progressive delivery, canary releases, blue/green deployments, feature flags, or automated rollback
