Growth Operations Lead

Own the GTM data foundation. You'll maintain our full TAM inside Lightfield — 20,000+ venture-backed companies enriched with funding data, segmented by ICP tier, refreshed automatically — and keep the account, contact, and opportunity data clean enough that agents and humans can trust it.

Build the attribution and reporting layer. You'll own the pipelines and dashboards that tell us where pipeline actually comes from — source attribution on every opportunity, inbound vs. outbound tagging, campaign-to-spend mapping, and marketing dashboards leadership runs the business on. Our Performance Marketing Lead defines what we measure; you make it true in the data.

Ship revenue-driving automations. You'll design and run the always-on plays that turn signals into pipeline: website visitor de-anonymization into multi-channel sequences, demo and paywall drop-off recovery, closed-lost re-engagement, funding-signal listeners, and referral loops. You'll describe the process; Lightfield's agents will run it; you'll own that it works.

Own routing and the marketing-sales handoff. Lead scoring, segment-based routing, target list generation for AEs, and the SLAs that keep speed-to-lead fast as volume scales.

Integrate the stack. You'll connect Lightfield to the tools around it — ad platforms, enrichment, gifting, outbound infrastructure, billing — and own that data flows reliably in both directions.

Run our agent fleet. You'll stand up, monitor, and continuously improve the automations our operating model depends on — and when one breaks quietly at the worst moment, you'll be the person who notices and fixes it.

You're AI-native. You build workflows by describing them, use AI to write your analyses and your automations, and get more done alone than most ops teams of five.

You've run RevOps or growth ops at a fast-growing B2B company. You've owned a CRM data model end to end, and you have scars from lead routing, attribution debates, and enrichment vendors.

You think in systems, not tickets. Given twenty requests, you find the three underlying problems. You'd rather build the automation than do the task twice.

You're technically fearless without being an engineer. APIs, webhooks, and data pipelines don't scare you. You can debug why a sync failed by reading the logs, and you know when to pull in engineering versus fix it yourself.

You have a point of view on data quality. You know that agents are only as good as the records they reason over, and you treat CRM hygiene as a product, not a chore.

You have a track record of success at a fast-paced early-stage company. You're comfortable with a less-structured work environment and shipping daily.