Role Summary:
Every engineer pays a tax on slow builds, flaky tests, manual release steps, and tooling they have to work around. That tax compounds, and it’s paid by every team, every day, and it never shows up on a roadmap. This role exists to pay it down, so that everyone building software for legal teams can ship faster.
Today the largest known cost is the path from commit to production: GitLab CI for build, Octopus Deploy for release, across .NET, Python, and Svelte. That’s where you’ll start, and it isn’t where the job ends. The same mandate covers developer platform work, internal tooling, and purpose-built solutions for one team’s specific problem. What stays fixed is the measure: how much faster we ship, and how much friction you took out. You’ll have a strong hand in choosing the means. This is a senior individual contributor role, and your leverage comes from what you build and who you persuade.
What You'll Do:
- Own and re-architect the path from commit to production, end to end, across three language ecosystems. It’s the largest single cost today and the first thing you’ll take on.
- Build internal tooling that engineers adopt because it’s better, not because it’s mandated.
- Build the platform layer where it pays for itself: self-service environments, paved paths, and shared infrastructure that teams should stop solving separately. Build one-off solutions where a single team’s problem deserves a purpose-built answer.
- Expand our delivery metrics and use them to drive decisions and report progress.
- Improve local development setup and onboarding, and bring AI-assisted development into our workflow deliberately.
What You'll Need:
- Deep hands-on CI/CD ownership: you’ve designed and rebuilt pipelines, not just consumed them.
- Real software engineering ability. This isn’t a configuration role; you’ll write code your peers respect.
- Product sense for internal tools, and the ability to change how engineers work without the authority to make them. You treat engineers as users, you know the difference between what they ask for and what they need, and you earn adoption through better tools, clear writing, and credibility from having shipped.
- Range across more than one language ecosystem at once: several dependency caches, several test runners, one coherent release process. We care that you’ve handled the variety, not that you’ve handled ours.
- Fluency in how software delivery is measured: You know the metrics well enough to instrument them, read them honestly, and use them to choose what to work on. We make decisions on data, not whim.
- Infrastructure-as-code and containerization in practice.
Nice To Have
-
GitLab CI at scale (runner fleets, caching strategies, reusable templates) or Octopus Deploy.
-
Build systems for .NET/MSBuild, Python packaging, or modern JavaScript build tooling.
-
Experience with monorepo tooling, pipeline observability, or security/compliance automation.
-
Prior background working as a product/feature software engineer