See how candidates think and approach the work this role demands, before the phone screen. We'll build a video challenge from this posting, and you can edit or share it before it goes live.
A former consumer-scale AI startup (Tome) is building its own CRM and hiring a RevOps leader to design the revenue machine around it, suggesting the company is betting that AI-native customer data can replace traditional sales software and that the people who run go-to-market should help shape the product itself.
Lightfield is reimagining CRM as a world model of a business. By learning from emails, meetings, and customer conversations, we’re building a living understanding of how a company works—so AI can help teams anticipate what comes next, make better decisions, and take action.
More than 5,000 companies have used the product since its November launch. We’ve raised more than $70M from Andreessen Horowitz, Coatue, Maverick Ventures, and Greylock to attack the biggest software category in the world. We previously built Tome, which reached more than 25 million users, and our team brings experience from Llama, Instagram, Google, and Salesforce.
We're looking for a Head of Revenue Operations to build the revenue infrastructure that will power Lightfield's growth. This role goes beyond traditional RevOps. You'll combine revenue strategy, business architecture, and operational excellence with GTM engineering, automation, and AI-native workflows. You'll also help shape the product we're building. Lightfield is our CRM, and you'll be a critical partner to Engineering, representing the RevOps persona and helping define what modern revenue operations should look like. This is a leadership role for someone who thinks strategically, loves building, and is excited to be hands-on at an early-stage company.
Own revenue strategy and operations: Lead forecasting, planning, territory design, capacity modeling, pipeline management, compensation operations, and GTM performance.
Build our GTM infrastructure: Design the systems, workflows, automations, and data architecture that connect Sales, Marketing, and Customer Success.
Drive GTM engineering: Leverage AI, automation, and emerging tools to build more intelligent, efficient, and scalable revenue processes.
Be a hands-on builder: Own our internal Lightfield implementation, build dashboards, configure workflows, and solve operational problems directly.
Shape our product: Partner with Product and Engineering to translate RevOps challenges into product capabilities, using our own GTM organization as a proving ground.
Be an external thought partner: Join strategic customer conversations with RevOps and GTM executives, contribute to thought leadership, and help establish Lightfield's credibility with revenue leaders.
8+ years in Revenue Operations, GTM Strategy, or Revenue Systems, ideally at high-growth B2B SaaS companies.
Deep expertise in revenue planning, forecasting, GTM architecture, analytics, and operations.
Strong technical aptitude and hands-on experience building CRM workflows, automations, integrations, and reporting.
Experience leveraging AI, automation, or GTM engineering to improve revenue productivity.
Executive presence and the ability to engage credibly with senior RevOps leaders and CROs.
A builder's mindset, strong product instincts, and excitement about reimagining how revenue teams operate.
Competitive salary
Meaningful early equity
Health insurance (medical, dental, vision)
3 weeks of PTO
11 paid company holidays + we enjoy a winter holiday break
3 months of paid family leave
Wednesdays work from home
Regular team dinners, events, offsites, and retreats
401k plan
Other perks include: commuter and lunch stipend
Answer a McCoy challenge. Companies hiring in operations see your response and reach out when they want to talk.
About 15 minutes to prepare and 5 minutes to record. Unlimited retakes and a teleprompter help you answer. No AI training, and you can delete your response anytime.
This isn't an application to Tome.
tome:49122ae5-60de-4015-ad02-96eec9d4337aLightfieldThis posting hasn't been probed by our closure verifier yet. Stream C runs on a rolling schedule against postings approaching the close-decision threshold.
See how we measure for definitions, or our corrections log for known issues. Found something wrong? Flag a correction.