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.
You’ll own the systems that carry our software from commit to production: GitLab CI for build, Octopus Deploy for release, across .NET, Python, and Svelte. That’s today’s starting point, not the destination. The mandate here is transformation — we need to accelerate delivery meaningfully, how far that goes is genuinely open, and you’ll have a strong hand in deciding.
What You'll Do:
Own and re-architect our CI/CD pipeline end to end, across three language ecosystems.
Find where engineering time actually goes — through conversation and through data — and fix what costs the most.
Build internal tooling that engineers adopt because it’s better, not because it’s mandated.
Attack flaky tests, slow feedback loops, and the seams between systems where delivery quietly stalls.
Instrument 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.
Carry on-call for what you build. We support what we ship.
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.
Pipelines serving multiple language ecosystems at once, several dependency caches, several test runners, one coherent release process.
Fluency in how software delivery is measured: You know the DORA 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.
An ownership mindset. You’ve carried a pager for systems you built, and it shaped how you build them.
The ability to change how engineers work through mentorship — through better tools, clear writing, and earned credibility.
Hands-on, non-superficial use of AI-assisted development tooling.
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
Similar Jobs
.png){kind=logo}
.png)
What you need to know about the San Francisco Tech Scene
Key Facts About San Francisco Tech
- Number of Tech Workers: 365,500; 13.9% of overall workforce (2024 CompTIA survey)
- Major Tech Employers: Google, Apple, Salesforce, Meta
- Key Industries: Artificial intelligence, cloud computing, fintech, consumer technology, software
- Funding Landscape: $50.5 billion in venture capital funding in 2024 (Pitchbook)
- Notable Investors: Sequoia Capital, Andreessen Horowitz, Bessemer Venture Partners, Greylock Partners, Khosla Ventures, Kleiner Perkins
- Research Centers and Universities: Stanford University; University of California, Berkeley; University of San Francisco; Santa Clara University; Ames Research Center; Center for AI Safety; California Institute for Regenerative Medicine
