We care more about how you think and what you've built than which specific tools you've used. Here's what success looks like in this role
You're a thoughtful software engineer who also loves infrastructure. You write clean, well-designed code and lead by example in caring about the experience of the people using what you build
You've worked on CI/CD systems and have real experience building and leading durable solutions to the hard problems — slow builds, flaky tests, painful merges
You've built and led developer tooling that other engineers genuinely wanted to use: self-serve frameworks, CLI tools, build systems, environment setup, or debugging tools
You're comfortable in Python and/or TypeScript — our monorepo leans on both
You have 7+ years in software engineering, with meaningful time spent building and leading developer infrastructure or tooling initiatives
Automation is your default. You build solutions proactively — doing something manually twice feels like a problem worth solving
You think from the perspective of the engineers using your work, and lead with empathy. Developer experience isn't a buzzword to you — it's the whole job
We'd love to hear about experience in any of these areas — but we don't expect any one person to have all of them
Monorepo tooling and build systems (e.g. Bazel, Pants, Monorepo, Nx, or similar approaches)
Cloud-based development environments (e.g. Coder, Codespaces, devcontainers)
CI platform depth — going beyond workflow files into managing runners, optimizing costs, and building custom tooling
Containerized builds and local/CI parity (e.g. Docker, Dagger)
Deploy pipeline patterns: canary deployments, feature flags, automated rollbacks, GitOps
AI coding tools — not just using them, but leading the configuration, customization, or building of tooling around them
Security engineering in developer workflows: dependency scanning, secrets management, supply chain controls
GCP experience