> Markdown version of [/jobs/ext/4625833-staff-software-engineer-gtm-systems](https://www.wearedevelopers.com/jobs/ext/4625833-staff-software-engineer-gtm-systems). 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 Software Engineer, GTM Systems

- **Company:** Anthropic Limited
- **Location:** San Francisco, CA, United States
- **Salary:** $320,000
- **Contract:** Permanent contract
- **Skills:** Code Review, Continuous Integration, Salesforce.Com, Delivery Pipeline, AI Coding Agents, Deployment Automation, Software Version Control
- **Published:** November 7, 2026
- **Apply:** https://www.juju.com/job/28_25196_df183d8b2a71b8f1d01ce026ec1368e6

## About the Role

Have worked on business-critical enterprise platforms where financial correctness and auditability mattered

Have experience with Salesforce or comparable enterprise platforms, including their metadata and deployment models

Have built tooling or agents on top of an enterprise system of record

Have operated in a company under audit or compliance constraints, Minimum education: Bachelor's degree or an equivalent combination of education, training, and/or experience

Required field of study:A field relevant to the role as demonstrated through coursework, training, or professional experience

Minimum years of experience: Years of experience required will correlate with the internal job level requirements for the position

Location-based hybrid policy: Currently, we expect all staff to be in one of our offices at least 25% of the time. However, some roles may require more time in our offices.

## Description

GTM Systems builds and runs the platform that Sales and contracting operate on. These are production systems that process real transactions and produce the data the rest of the company depends on, and the team has grown into a scope where the engineering practices need to grow with it. The platform-developer model got us here. The next stage is a team that operates as software engineers on top of it.

We are hiring a technical lead to build that next stage. You will design and stand up the engineering motions the team runs on, from pull requests and CI/CD through automated UAT, and you will set the technical bar by working alongside the team rather than legislating from the side. Anthropic is also an unusual place to do this work: our own frontier models are part of your toolkit, the team already uses them daily, and a real part of this role is turning that individual usage into a coordinated engineering practice., Lead architecture reviews for GTM systems that process lead-to-cash transactions and generate the data points the organization runs on, including changes originating in other teams that land on our platform

Architect and mature the engineering pipeline the team develops against: pull request workflow, CI/CD, automated UAT, and the deploy path from source control to production

Establish shared AI-assisted development standards for the team, converting existing individual usage into consistent practice that holds up under review

Work with engineering teams outside GTM on shared architectural problems and common tooling, where the right answer is a platform decision rather than a local one

Build and shape the agentic tooling running on top of our platform, and set the pattern other engineers follow when they build the next one

Trace the dependency chain from upstream data and downstream quoting and provisioning systems, and make sure design decisions account for what they break

Partner with the platform developers on the team as engineering practice deepens, expanding what the team can safely ship

Have strong software engineering fundamentals: version control discipline, testing, code review, deployment automation, and a bias toward simple designs

Have built the delivery pipeline for a team, not just worked within one, and can describe the sequencing choices you made

Have led a team through a step change in engineering practice as its scope grew, including what you did when adoption slowed

Work fluently with AI coding tools and agentic development workflows, and have views on how a team should standardize around them

Can run a technical discussion across teams that do not report to you and leave it with a decision rather than a follow-up meeting

Reason about systems you do not own well enough to predict how your changes affect them

Prefer influence through demonstrated work over positional authority