# Business Systems Analyst, GTM Systems — LangChain

- Location: San Francisco, CA
- Posted: Oct 14, 2026
- Status: open (checked Nov 20, 2026)
- Apply (employer's site): https://jobs.ashbyhq.com/langchain/886be84d-b56a-4260-a8dc-87992640293d
- Employer record: https://visajobs.io/company/langchain.md

## Sponsorship history
- Tier: Employer history only
- Occupation (SOC): Computer Systems Analysts (15-1211)
- Employer's certified LCAs for this occupation in CA, FY2024–FY2026: 0
- …in the whole US: 0
- With this exact title: 0
- Median DOL prevailing wage, level I / II: $97k / $122k

## Description
About Us
At LangChain, our mission is to enable every company to own its intelligence. We believe agents will transform how companies operate, and we're building the foundation to make that future possible. Our open-source harnesses and LangSmith platform give developers and enterprises the infrastructure to run, improve, and govern agents at scale.
We've raised $460M to date, with our most recent funding round valuing the company at $3B, backed by leading investors including Sequoia, Benchmark, IVP, and CapitalG. As we continue to expand our platform and tackle some of the hardest challenges in agent engineering, every team member has the opportunity to make a meaningful impact and help shape both our technology and the future of the industry.
More than 7,000 organizations rely on LangSmith, from fast-growing startups to Fortune 500 enterprises, including NVIDIA, Bridgewater, LinkedIn, Workday, and Rippling. We're just getting started on making high-performing agents easier to build and manage at scale.
About the Team:
You'll join our GTM Systems team, which owns the systems LangChain's go-to-market actually runs on — Salesforce above all: 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.
We design and ship internal product for the GTM organization. AI agents do a growing share of the building: they draft design docs, open changes, and run Salesforce deployments, while humans hold the approval gates. Build capacity — engineers plus the agent bench — sits on this team, and you'll help decide what it works on next.
About the Role:
You'll own the requirements, prioritization, and quality bar for LangChain's Salesforce-centered GTM systems, turning ambiguous revenue-team needs into shipped process and systems changes that scale.
This is not a ticket queue role. You'll be accountable for a small number of high-leverage GTM systems programs at a time: defining the problem, aligning stakeholders, specifying the solution, and ensuring what ships changes how the revenue org operates.
You'll work across Sales, Marketing, Partnerships, Support, and Finance in a fast-changing environment where priorities move quickly and influence matters more than reporting lines. The core challenge is operating with authority but not control: aligning teams around tradeoffs as the business changes underneath the plan.
You won't be expected to write production code. You will be expected to write clear enough specifications that engineers and AI coding agents can build from them, and to review the output with enough Salesforce and systems judgment to decide whether it is correct.
Location: San Francisco Bay Area — in office 4 days a week. The people whose processes you're redesigning are in this building, and so are the engineers who build LangGraph.
What You'll Own:
Carry multi-quarter programs
Own the Salesforce sales process from lead to close — routing, qualification, territory assignment, and stage progression — driving each initiative from discovery through UAT, change management, and adoption.
Be the person stakeholders come to before they file a request, especially when the system was never designed for what the business now needs.
Own the intake and prioritization model for hundreds of quarterly GTM systems requests, ensuring the team works on the highest-leverage business problems rather than the loudest tickets.
Own what gets specified and what ships
Run discovery and turn ambiguous asks into BRDs, process flows, data models, and acceptance criteria — with a clear problem statement and ROI justification, precise enough to execute without a second conversation.
Hold the quality gate: you write the specification, engineers and coding agents write the code, and nothing reaches production without your sign-off.
Run vendor evaluations when the right answer is buy, integrate, or replace rather than build.
Protect revenue data integrity
Trace anomalies in revenue fields — Net ARR, initial pipeline, lead source — back to the automation, trigger, or integration that wrote them.
Own the reconciliation seam between Salesforce, usage-based billing, and cloud-marketplace transactions.
Identify which design decisions are load-bearing and which are cosmetic, and catch the downstream failure modes before they reach production.
What Success Looks Like:
In your first 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.
Create a prioritization model for hundreds of GTM systems requests per quarter, with clear tradeoffs and business rationale.
Ship a Salesforce change that improves pipeline hygiene, quote-to-cash accuracy, provisioning reliability, or cloud marketplace reconciliation.
Establish a specification and UAT standard that engineers and AI agents can reliably build against.
Build enough trust with Sales, Marketing, Partnerships, Support, and Finance that stakeholders bring you the problem before they prescribe the solution.
What You'll Need to Be Successful:
Systems and domain depth
Domain and tenure — 6–8 years in business systems, sales systems, revenue systems, or GTM systems, with Salesforce as your primary platform throughout.
Sales process depth — you've partnered with Sales Ops on the things reps feel every day: territory and account coverage, lead qualification and routing, stage gates, and pipeline and forecast hygiene.
Sales systems / RevOps depth — experience across quote-to-cash, CPQ, territory and lead routing, forecasting, or adjacent revenue processes.
Technical fluency — you can read a data model, a Flow, and enough Apex to design against what's really there, even though you are not expected to write production code.
Program leadership
Program ownership — you've been the single accountable owner, at the working level negotiating the commitments yourself, of a program that spann

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
