You and the process

With a person
Anna, in-house recruiter
9 years hiring engineers
30 minutes with a real recruiter
They read your CV with you, on a call, and say where the offers are being lost.
Didn’t find what you were looking for? Tell us what to build
LangChain

Business Systems Analyst, GTM Systems

  • Office
  • 6+ years

Salary

$180,000 - 200,000/ year

AI summary

For members

The whole posting in a few lines. Sign up to read it here and on every role you open.

Sign Up to Read

Description

The company builds open-source agent harnesses and a platform that help developers and enterprises run, improve and govern agents at scale.

The company has raised $460M and was most recently valued at $3B. Investors include Sequoia, Benchmark, IVP and CapitalG.

More than 7,000 organizations use the platform, from startups to Fortune 500 enterprises such as NVIDIA, Bridgewater, LinkedIn, Workday and Rippling.

You would join the GTM Systems team, which runs the systems the company's go-to-market depends on, mainly Salesforce: the account and contact model, territory and routing, the sales process from first touch to closed-won, and the quote-to-cash and provisioning stack behind it.

The team builds internal products for the GTM organization. AI agents do much of the building, drafting design docs, opening changes and running Salesforce deployments, while people approve each gate. Engineers and agents both sit on this team, and you will help set its priorities.

You will not write production code.

Responsibilities

  • Own requirements, priorities and quality standards for the company's Salesforce-centered GTM systems, turning vague revenue-team requests into shipped process and system changes that scale.
  • Run a small number of high-impact GTM programs at a time, from defining the problem and aligning stakeholders through to specifying the fix and making sure what ships changes how revenue works.
  • Work across Sales, Marketing, Partnerships, Support and Finance, where priorities shift quickly and influence counts for more than reporting lines. Align teams on tradeoffs as the business changes.
  • Own the Salesforce sales process from lead to close: routing, qualification, territory assignment and stage progression. Take each initiative from discovery through UAT, change management and adoption.
  • Be the person stakeholders contact before they file a request, especially when the system was not built for what the business now needs.
  • Own the intake and prioritization model for hundreds of quarterly GTM requests, so the team works on the highest-leverage problems rather than the loudest ones.
  • Run discovery and write BRDs, process flows, data models and acceptance criteria, with a clear problem statement and ROI case, detailed enough to build without another meeting.
  • Sign off on everything before it reaches production. You write the specification, and engineers and coding agents write the code.
  • Lead vendor evaluations when buying, integrating or replacing a tool is better than building.
  • Trace anomalies in revenue fields such as Net ARR, initial pipeline and lead source back to the automation, trigger or integration that wrote them.
  • Own the reconciliation between Salesforce, usage-based billing and cloud marketplace transactions.
  • Separate load-bearing design decisions from cosmetic ones, and catch downstream failures before release.
  • Within 6-12 months, you might redesign the lead-to-opportunity process so routing, qualification and stage progression are measurable, enforceable and adopted by the field.
  • Within 6-12 months, you might build a prioritization model for hundreds of GTM requests a quarter, with clear tradeoffs and business rationale.
  • Within 6-12 months, you might ship a Salesforce change that improves pipeline hygiene, quote-to-cash accuracy, provisioning reliability or marketplace reconciliation.
  • Within 6-12 months, you might set a specification and UAT standard that engineers and AI agents can reliably build against.
  • Within 6-12 months, you might earn enough trust with Sales, Marketing, Partnerships, Support and Finance that they bring you the problem before prescribing a solution.

Requirements

  • Have 6-8 years in business, sales, revenue or GTM systems, with Salesforce as your primary platform throughout.
  • Have partnered with Sales Ops on territory and account coverage, lead qualification and routing, stage gates, and pipeline and forecast hygiene.
  • Have experience across quote-to-cash, CPQ, territory and lead routing, forecasting or similar revenue processes.
  • Read a data model, a Flow and enough Apex to design against what the system actually contains.
  • Have been the single accountable owner of a program that spanned four or more functions and changed how a revenue organization works day to day, negotiating commitments yourself at the working level.
  • Have delivered a program into a core system on a release process you did not control, where another team's change could break your release.
  • Have re-scoped a program mid-flight because the business changed, a sponsor moved, or the original scope no longer matched reality.
  • Have declined a request with executive backing and kept the relationship, and have held the line on pricing discipline, legal constraints or architecture, arriving with an alternative.
  • Write for the reader in front of you: a clear page for a VP, a precise spec for an engineer.
  • Find friction and start the project yourself rather than waiting for a ticket.
  • Give an AI agent the same brief you would give a new engineer, and check its work the same way.
  • Know which architecture calls are load-bearing and which are cosmetic, such as why a usage event belongs on its own object rather than a field on Account, and how renaming one picklist can break the provisioning saga before anyone deploys.
  • Strong signals are not screens: none is required, but any one makes you useful faster.
  • Strong signal: you have owned a core Salesforce object domain such as Account, Contact, Lead or Opportunity through a full redesign.
  • Strong signal: you have traced a Salesforce field into a usage record and then into a provisioning step, and seen what broke downstream when it moved.
  • Strong signal: you have worked with cloud marketplace operations such as AWS or GCP private offers, co-sell, entitlement mapping and metering, and know the failure modes when they break.
  • Strong signal: you have worked with usage-based billing systems such as Metronome or Orb, or similar, and with CRM-to-billing identity reconciliation.
  • Strong signal: you have experience with the company's agent frameworks, or you are keen to learn them from the people who build them.

Conditions

Compensation includes base salary, variable pay for relevant roles, meaningful equity, benefits and perks.

The annual base salary range is $180-200k USD.

The band reflects the range of scope being hired for. The offer depends on what the interviews show about your impact, craft, leadership and communication. You will hear early where you stand and discuss pay before the offer stage.

Based in the San Francisco Bay Area, in office 4 days a week, alongside the people whose processes you will redesign and the engineers who build the agent framework.

Team members in the EU, UK and APAC receive locally competitive benefits aligned with regional norms and regulations.

Benefits

  • Medical, dental and vision coverage, flexible vacation, a 401(k) plan, and meals on in-office days in the US, among other benefits.

Where you’d work

From the office, 4 or more days a week in the office

The office

About the company

LangChain

Office in San Francisco, United States

Also hiring in Amsterdam, Netherlands, London, United Kingdom, New York, United States and 1 more place

6 of their 22 open roles are remote

Your chances

Worth a look before you spend an evening tailoring a CV for it.

  • 22 checks run
  • 2 red flags

Still hiring?

14 checks

1 red flag

How crowded?

8 checks

1 red flag

Fits Me

How well does this role fit you?

Answer a few questions or drop your CV, and every role gets a fit score with the reasons, this one first.

  • Your field
  • Level
  • Stack
  • Work model
  • Salary floor
  • Must-haves
Details11 facts · Role, Location, Compensation, Employment
Tech stack
  • AWS
  • LangChain
Type
Full-time
Equity
Equity offered
Region
United States
Pay period
Annual
Show 6 more factsShow less

Role

Category
Product & Project
Experience
8+ years
Tech stack
  • AWS
  • LangChain

Location

Work model
Office
Region
United States
Office
  • San Francisco, United States
Days in the office
4 or more days

Compensation

Salary
$180,000 - 200,000 / year
Pay period
Annual
Equity
Equity offered

Employment

Type
Full-time

Something wrong with this vacancy?

Similar vacancies

Share this vacancy

What's wrong with it?

The employer never sees who reported.

Reason