Skip to content
LangChain

Monetization Operations & Systems Lead

San Francisco, CAOnsite · United States
Staff · FullTime · Revenue Operations
POSTED 15 OCTVERIFIED 18H AGO
Apply Ask
Role
31 days opentrue age
Closes in ~4d at the median (35d)
Posted 15 Oct · n=17
Pay
$220k–$280kno pay posted
$175k$280k
Market p25–p75
$175k–$250k
LangChain p25–p75
$220k–$280kn=5
SF Bay Area · n=947 · 365d to 15 Nov
CompanyLangChain →
103open roles
Opened · 30d
+12
Closed · 30d
−5
Signal
● Steady+7 net
14d of snapshots · 30d window
Market
23,310open · Staff Other
Opened · 7d
+3,05113% of open
All other
622,837open
All tracked boards · live 16 Nov · n=23,310
Visa
12H-1B LCAs · FY26
Median wage
$170k
LCAs FY26 · n=12 · to 2026-05-18
AWSGCPAzure

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 role

The ways customers buy from us are multiplying as fast as the business is growing. Enterprise order forms. Private offers through AWS, GCP, and Azure. A self-serve business running on usage-based pricing, with commits, drawdowns, and true-ups behind it. Each one is a distinct path from signature to cash, and each one runs today on some mix of manual steps and automation that grew up with the business.

This role owns what comes next. You'll run order operations end to end - booking, provisioning, invoicing, amendments, and renewals - on a stack we picked deliberately and recently: Salesforce, Metronome for metering and billing, Rillet for ERP. The stack is modern, but the processes on top of it were built to keep up with growth, not designed to scale. Your job is to decide what each one should become: keep it, rebuild it, automate it, or retire it.

Our bias is to invest in systems rather than in a growing queue of manual work, so you'll be setting the automation roadmap at the same time you're operating the function - deciding what a person should touch, what a workflow should handle, and what should never have been a step in the first place. Getting that right is what lets order volume grow by an order of magnitude without ops growing with it.

This is a senior individual contributor role. You'll own order operations, working closely with Deal Strategy and Operations, GTM Systems, Finance and Accounting, and Enterprise Engineering. Those teams are your partners and much of your build capacity. Bringing them onto one shared order-to-cash roadmap is a core part of the job, and the reason we're hiring someone senior to do it.

What you'll do

Own the order-to-cash path end to end: order form intake from Deal Desk, booking in Salesforce, plan and entitlement setup in Metronome, invoicing and revenue recognition through Rillet, and the amendments, true-ups, and renewals that follow

Build out cloud marketplace operations across AWS, GCP, and Azure: private offer setup, usage reporting to each marketplace, and reconciling marketplace disbursements back to what we billed. Every new channel launches against defined readiness criteria, so marketplace deals run on the same clean path as direct ones

Own self-serve billing operations: usage metering, plan changes, dunning, credits, rebills, refunds, and the escalations behind them

Own billing and usage completeness at month-end close. Every order, credit, and metered event is reconciled between Metronome and Rillet before revenue is recognized, not after

Partner with Deal Strategy and Product as our pricing evolves. Bring the billing view into pricing and deal-structure decisions early, so new models and non-standard terms can be billed accurately and automated, not handled by hand

Set the automation roadmap. Instrument the path, put a number on every place a human touches an order, and decide what gets automated, what gets designed away, and what stays manual on purpose

Treat every billing error as a defect: find the root cause and fix the class of problem, not just the one invoice

Source · LangChainFirst seen 2 Nov1 editsOriginal ↗